MeeGo wiki - User contributions [en]

File:Ux-daemon.jpg

2011-05-20T06:05:52Z

Tatlahte: TDriver visualizer dump of the meego ux

TDriver visualizer dump of the meego ux

Quality/QA-tools/TDriver/Getting Started

2011-01-12T07:06:12Z

Tatlahte: /* Building Qt components */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

For Ubuntu:
<pre>
sudo apt-get install qttas testability-driver-host visualizer # This can take several minutes
</pre>

Fedora:
<pre>
yum install qttas testability-driver-host testability-driver-visualizer
</pre>

Start a new shell and you should have all the required environmental parameters set.

== Other platforms ==

TDriver components can be installed on most Qt and Ruby supported platforms. The ruby components can be found from rubygems.org. You will need the following packages, or their equivalents installed:
<pre>
rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

Then install the gems:
<pre>
sudo gem install testability-driver testability-driver-qt-sut-plugin
</pre>

=== Building Qt components ===

Build requirements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev
</pre>

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
</pre>

Build requirements for Fedora:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
Build requiremens for Ubuntu
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
</pre>
Fedora
<pre>
sudo yum install git qt4-qmake gcc-c++
</pre>

Compile and install
<pre>
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber # This will take a few minutes and require gherkin-2.3.2
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

Note: If you used the "testability-driver-host" package to install TDriver, the ip address is set automatically to the "sut_qt_maemo" device.

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2011-01-12T07:03:58Z

Tatlahte: /* Building Qt components */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

For Ubuntu:
<pre>
sudo apt-get install qttas testability-driver-host visualizer # This can take several minutes
</pre>

Fedora:
<pre>
yum install qttas testability-driver-host testability-driver-visualizer
</pre>

Start a new shell and you should have all the required environmental parameters set.

== Other platforms ==

TDriver components can be installed on most Qt and Ruby supported platforms. The ruby components can be found from rubygems.org. You will need the following packages, or their equivalents installed:
<pre>
rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

Then install the gems:
<pre>
sudo gem install testability-driver testability-driver-qt-sut-plugin
</pre>

=== Building Qt components ===

Build requirements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqt4-webkit
</pre>

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
</pre>

Build requirements for Fedora:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
Build requiremens for Ubuntu
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
</pre>
Fedora
<pre>
sudo yum install git qt4-qmake gcc-c++
</pre>

Compile and install
<pre>
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber # This will take a few minutes and require gherkin-2.3.2
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

Note: If you used the "testability-driver-host" package to install TDriver, the ip address is set automatically to the "sut_qt_maemo" device.

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2011-01-05T11:41:47Z

Tatlahte: /* Connecting to your MeeGo device */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

For Ubuntu:
<pre>
sudo apt-get install qttas testability-driver-host visualizer # This can take several minutes
</pre>

Fedora:
<pre>
yum install qttas testability-driver-host testability-driver-visualizer
</pre>

Start a new shell and you should have all the required environmental parameters set.

== Other platforms ==

TDriver components can be installed on most Qt and Ruby supported platforms. The ruby components can be found from rubygems.org. You will need the following packages, or their equivalents installed:
<pre>
rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

Then install the gems:
<pre>
sudo gem install testability-driver testability-driver-qt-sut-plugin
</pre>

=== Building Qt components ===

Build requirements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libwebkit4-dev
</pre>

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
</pre>

Build requirements for Fedora:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
Build requiremens for Ubuntu
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
</pre>
Fedora
<pre>
sudo yum install git qt4-qmake gcc-c++
</pre>

Compile and install
<pre>
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber # This will take a few minutes and require gherkin-2.3.2
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

Note: If you used the "testability-driver-host" package to install TDriver, the ip address is set automatically to the "sut_qt_maemo" device.

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2011-01-05T11:40:25Z

Tatlahte: /* Installing required packages from repositories */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

For Ubuntu:
<pre>
sudo apt-get install qttas testability-driver-host visualizer # This can take several minutes
</pre>

Fedora:
<pre>
yum install qttas testability-driver-host testability-driver-visualizer
</pre>

Start a new shell and you should have all the required environmental parameters set.

== Other platforms ==

TDriver components can be installed on most Qt and Ruby supported platforms. The ruby components can be found from rubygems.org. You will need the following packages, or their equivalents installed:
<pre>
rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

Then install the gems:
<pre>
sudo gem install testability-driver testability-driver-qt-sut-plugin
</pre>

=== Building Qt components ===

Build requirements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libwebkit4-dev
</pre>

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
</pre>

Build requirements for Fedora:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
Build requiremens for Ubuntu
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
</pre>
Fedora
<pre>
sudo yum install git qt4-qmake gcc-c++
</pre>

Compile and install
<pre>
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber # This will take a few minutes and require gherkin-2.3.2
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2011-01-05T11:40:15Z

Tatlahte:

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

For Ubuntu:
<pre>
sudo apt-get install qttas testability-driver-host visualizer # This can take several minutes
</pre>

Fedora:
<pre>
yum install qttas testability-driver-host testability-driver-visualizer
</pre>

Start a new shell and you should have all the required environmental parameters set.

== Other platforms ==

TDriver components can be installed on most Qt and Ruby supported platforms. The ruby components can be found from rubygems.org. You will need the following packages, or their equivalents installed:
<pre>
rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

Then install the gems:
<pre>
sudo gem install testability-driver testability-driver-qt-sut-plugin
</pre>

=== Building Qt components ===

Build requirements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libwebkit4-dev
</pre>

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
</pre>

Build requirements for Fedora:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
Build requiremens for Ubuntu
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
</pre>
Fedora
<pre>
sudo yum install git qt4-qmake gcc-c++
</pre>

Compile and install
<pre>
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber # This will take a few minutes and require gherkin-2.3.2
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2011-01-05T11:37:52Z

Tatlahte:

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

<pre>
sudo apt-get install qttas testability-driver-host visualizer
</pre>

Start a new shell and you should have all the required environmental parameters set.

=== Fedora 13 ===

<pre>
yum install qttas testability-driver-host testability-driver-visualizer
</pre>

Start a new shell and you should have all the required environmental parameters set.

== Other platforms ==

TDriver components can be installed on most Qt and Ruby supported platforms. The ruby components can be found from rubygems.org. You will need the following packages, or their equivalents installed:
<pre>
rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

Then install the gems:
<pre>
sudo gem install testability-driver testability-driver-qt-sut-plugin
</pre>

=== Building Qt components ===

Build requirements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libwebkit4-dev
</pre>

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
</pre>

Build requirements for Fedora:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
Build requiremens for Ubuntu
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
</pre>
Fedora
<pre>
sudo yum install git qt4-qmake gcc-c++
</pre>

Compile and install
<pre>
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber # This will take a few minutes and require gherkin-2.3.2
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-16T10:17:21Z

Tatlahte: /* Ubuntu 10.10 */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.04 ===

Build requriements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libwebkit4-dev
</pre>

=== Ubuntu 10.10 ===

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 / 10.10 ===
To install visualizer and qttas server:
<pre>
sudo apt-get install visualizer qttas
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-16T10:17:01Z

Tatlahte: /* Ubuntu 10.04 */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.04 ===

Build requriements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libwebkit4-dev
</pre>

=== Ubuntu 10.10 ===

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev, x11proto-xext-dev, libxtst-dev, libqtwebkit-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 / 10.10 ===
To install visualizer and qttas server:
<pre>
sudo apt-get install visualizer qttas
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-16T10:16:37Z

Tatlahte: /* Compiling TDriver from git */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.04 ===

Build requriements for ubuntu 10.04:
<pre>
sudo apt-get install libqt4-dev, x11proto-xext-dev, libxtst-dev, libwebkit4-dev
</pre>

=== Ubuntu 10.10 ===

Build requirements for Ubuntu 10.10:
<pre>
sudo apt-get install libqt4-dev, x11proto-xext-dev, libxtst-dev, libqtwebkit-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 / 10.10 ===
To install visualizer and qttas server:
<pre>
sudo apt-get install visualizer qttas
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-16T09:27:56Z

Tatlahte: /* Ubuntu 10.04 / 10.10 */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 / 10.10 ===
To install visualizer and qttas server:
<pre>
sudo apt-get install visualizer qttas
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-16T09:27:33Z

Tatlahte: /* Ubuntu 10.04 / 10.010 */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 / 10.10 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-16T09:27:22Z

Tatlahte: /* Ubuntu 10.04 */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 / 10.010 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-16T09:21:46Z

Tatlahte: /* Ubuntu 10.04 */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttasserver &
calculator -testability &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-12-14T07:58:14Z

Tatlahte: /* Compilation */

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://git.gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://git.gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

'''For ubuntu 10.04'''
<pre>
sudo apt-get install git-core qt4-qmake qt4-dev-tools build-essential
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We still need to edit the tdriver parameters. Add the following line to <tt>/etc/tdriver/tdriver_parameters.xml</tt> inside
<tt><parameters></tt> tag:
<pre>
<parameter name="default_sut" value="sut_qt"/>
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver

2010-12-08T07:16:13Z

Tatlahte: /* Installation on MeeGo Netbook */

=Testability Driver (TDriver)=

New to TDriver? [https://projects.forum.nokia.com/Testabilitydriver/wiki/introduction_to_tdriver Look for an introduction to TDriver] from Forum Nokia web site.

TDriver is a test automation driver enabling acceptance testing through the UI or using business logic directly. It is written in Ruby language and enables using any test framework written for Ruby.

For a sample test run, see [http://www.youtube.com/watch?v=UL0XmcPKAp8 TDriver in action]. The cucumber tests in the example can be found from [http://gitorious.org/tdriver/tests/trees/master/examples/MeeGo/N900/cucumber/features here].

==Overview==

TDriver consists of the following modules:

* [[#Agent|Agent]]
* [[#Driver|Driver]]
* [[#Visualizer|Visualizer]]

===Agent===

TDriver has one agent for Qt based systems where Qt applications on any supported OS can be tested. The Qt agent is called qttasserver.

Agent (qttas-server) is the only component that needs to be installed to the SUT (system under test). It will handle communication with the testing framework and applications. When Qt application starts it will load a testability plugin into the application process. The plugin will register the application into qttasserver. Once the application is registered to qttasserver, it can be controlled and queried from the testing framework.

MeeGo touch applications will automatically load the testability plugin. If your application is a standard Qt application, use the "-testability" argument:

<pre>
myapp -testability
</pre>

That will cause the testability plugin to be loaded automatically.

===Driver===

Driver is the component that will provide the glue between test harness and SUT. You can install driver inside SUT or you can also use another host for driver that will connect to sut over tcp/ip.

TDriver is a ruby class libary which is packaged as a Ruby gem. Package 'rubygem-testability-driver' provides the core functionality and 'rubygem-testability-driver-qt-sut-plugin' provides the qt specific support.

===Visualizer===

Visualizer is a helper tool that provides access to UI components of the application. It will help testers to know what objects are contained and what is possible to do with them. You will see a SUT screenshot and an object tree containing all visible object. For Qt applications the objects are fetched from the object tree of the application registered to qttasserver. Visualizer also contains documentation and a small editor to help in scripting and debugging.

==Installation==

On a typical test automation setup, tests are executed on the host. See the [[Quality/QA-tools/TDriver/Getting Started|Getting Started Guide]] for host based installation. If you are going to install TDriver on MeeGo netbook, see the [[#Installation on MeeGo Netbook|Installation on MeeGo Netbook]] section.

===Adding Agent On The Target Device===

On host based testing, the only required package for the image is the qttas-server. Add this package to your ks. file if you want it into your image.

On a preexisting image, you can add it by
<pre>
sudo zypper install qttas-server
</pre>

This will install the agent. Once you reboot the agent should start automatically.

If you do not reboot the device, you can start the agent manually by:
<pre>
qttasserver &
</pre>

''' Note - qttasserver should always be run with the same user as the applications, e.g. meego '''

===Adding Everything On The Image===

You can also run the entire testability driver on the device. Currently packages are only in devel:quality. Add the devel:quality repository into the ks. file:
<pre>
repo --name=devel-quality-testing --baseurl=http://download.meego.com/live/devel:/quality/testing/
</pre>
And add the meta package:
<pre>
testability-driver
</pre>

Package rubygem-cucumber is also available if you have [http://cukes.info Cucumber] tests.

===Installation on MeeGo Netbook===

You need to enable devel:quality repo as not all components in Trunk:Testing
<pre>
sudo zypper ar http://download.meego.com/live/devel:/quality/testing/ devel:quality.repo
sudo zypper update
</pre>

To install all required packages install the testability-driver and visualizer packages. But lets install the tests package so we can easily test the installation:
<pre>
sudo zypper install testability-driver-tests testability-driver-visualizer
</pre>

You can test the installation using irb:

<pre> [matti@matti-desktop tmp]$ irb
irb(main):001:0> require 'tdriver'
=> true
irb(main):002:0> </pre>

To test the visualizer, make sure qttasserver is running and start testapp:

<pre>
qttasserver &
testapp &
</pre>

Now make sure you have RUBYOPT set and start visualizer:
<pre>
export RUBYOPT=rubygems
tdriver_visualizer &
</pre>

Now you should see the visualizer application. Select sut_qt from device menu and select File -> Refresh. You should now see screenshot of testapp and object tree which contains all visible objects from the application.

You can also try to run our unit tests to see that automated tests work:
<pre>
ruby /usr/share/testability-driver-tests/tc_testapp.rb
</pre>

And the script will use the app 'testapp' to test basic things like launching and closing app, tapping, dragging, flick etc.

== Enabling Logs On The Agent ==

In order to debug you can enable logs on the device. Just create a folder and give appropriate write access so that qttasserver and applications can write in there:

mkdir -p /logs/testability
sudo chmod a+w /logs/testability

Now if you restart qttasserver you will see a log file qttasserver.log being created. For each application loading testability plugin there will be also a file <application_name>.log

Quality/QA-tools/TDriver/Getting Started

2010-11-25T12:31:59Z

Tatlahte:

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===

<pre>
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
</pre>

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-25T12:31:15Z

Tatlahte:

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-25T12:30:58Z

Tatlahte:

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04/10.10, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 / 10.10 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver

2010-11-25T12:16:22Z

Tatlahte:

=Testability Driver (TDriver)=

TDriver is a test automation driver enabling acceptance testing through the UI or using business logic directly. It is written in Ruby language and enables using any test framework written for Ruby.

For a sample test run, see [http://www.youtube.com/watch?v=UL0XmcPKAp8 TDriver in action]. The cucumber tests in the example can be found from [http://gitorious.org/tdriver/tests/trees/master/examples/MeeGo/N900/cucumber/features here].

==Overview==

TDriver consists of the following modules:

* [[#Agent|Agent]]
* [[#Driver|Driver]]
* [[#Visualizer|Visualizer]]

===Agent===

TDriver has one agent for Qt based systems where Qt applications on any supported OS can be tested. The Qt agent is called qttasserver.

Agent (qttas-server) is the only component that needs to be installed to the SUT (system under test). It will handle communication with the testing framework and applications. When Qt application starts it will load a testability plugin into the application process. The plugin will register the application into qttasserver. Once the application is registered to qttasserver, it can be controlled and queried from the testing framework.

MeeGo touch applications will automatically load the testability plugin. If your application is a standard Qt application, use the "-testability" argument:

<pre>
myapp -testability
</pre>

That will cause the testability plugin to be loaded automatically.

===Driver===

Driver is the component that will provide the glue between test harness and SUT. You can install driver inside SUT or you can also use another host for driver that will connect to sut over tcp/ip.

TDriver is a ruby class libary which is packaged as a Ruby gem. Package 'rubygem-testability-driver' provides the core functionality and 'rubygem-testability-driver-qt-sut-plugin' provides the qt specific support.

===Visualizer===

Visualizer is a helper tool that provides access to UI components of the application. It will help testers to know what objects are contained and what is possible to do with them. You will see a SUT screenshot and an object tree containing all visible object. For Qt applications the objects are fetched from the object tree of the application registered to qttasserver. Visualizer also contains documentation and a small editor to help in scripting and debugging.

==Installation==

On a typical test automation setup, tests are executed on the host. See the [[Quality/QA-tools/TDriver/Getting Started|Getting Started Guide]] for host based installation. If you are going to install TDriver on MeeGo netbook, see the [[#Installation on MeeGo Netbook|Installation on MeeGo Netbook]] section.

===Adding Agent On The Target Device===

On host based testing, the only required package for the image is the qttas-server. Add this package to your ks. file if you want it into your image.

On a preexisting image, you can add it by
<pre>
sudo zypper install qttas-server
</pre>

This will install the agent. Once you reboot the agent should start automatically.

If you do not reboot the device, you can start the agent manually by:
<pre>
qttasserver &
</pre>

''' Note - qttasserver should always be run with the same user as the applications, e.g. meego '''

===Adding Everything On The Image===

You can also run the entire testability driver on the device. Currently packages are only in devel:quality. Add the devel:quality repository into the ks. file:
<pre>
repo --name=devel-quality-testing --baseurl=http://download.meego.com/live/devel:/quality/testing/
</pre>
And add the meta package:
<pre>
testability-driver
</pre>

Package rubygem-cucumber is also available if you have [http://cukes.info Cucumber] tests.

===Installation on MeeGo Netbook===

You need to enable devel:quality repo as not all components in Trunk:Testing
<pre>
sudo zypper ar http://download.meego.com/live/devel:/quality/testing/devel:quality.repo
sudo zypper update
</pre>

To install all required packages install the testability-driver and visualizer packages. But lets install the tests package so we can easily test the installation:
<pre>
sudo zypper install testability-driver-tests testability-driver-visualizer
</pre>

You can test the installation using irb:

<pre> [matti@matti-desktop tmp]$ irb
irb(main):001:0> require 'tdriver'
=> true
irb(main):002:0> </pre>

To test the visualizer, make sure qttasserver is running and start testapp:

<pre>
qttasserver &
testapp &
</pre>

Now make sure you have RUBYOPT set and start visualizer:
<pre>
export RUBYOPT=rubygems
tdriver_visualizer &
</pre>

Now you should see the visualizer application. Select sut_qt from device menu and select File -> Refresh. You should now see screenshot of testapp and object tree which contains all visible objects from the application.

You can also try to run our unit tests to see that automated tests work:
<pre>
ruby /usr/share/testability-driver-tests/tc_testapp.rb
</pre>

And the script will use the app 'testapp' to test basic things like launching and closing app, tapping, dragging, flick etc.

== Enabling Logs On The Agent ==

In order to debug you can enable logs on the device. Just create a folder and give appropriate write access so that qttasserver and applications can write in there:

mkdir -p /logs/testability
sudo chmod a+w /logs/testability

Now if you restart qttasserver you will see a log file qttasserver.log being created. For each application loading testability plugin there will be also a file <application_name>.log

Quality/QA-tools/How to set up repositories

2010-11-25T09:34:24Z

Tatlahte:

= How To Set Up Repositories =

QA tools are located at Tools:Testing repository. Before installing the actual tools, you need to set up the repository. The supported operating systems are MeeGo Netbook UX, Ubuntu 10.04 (and newer) and Fedora 13.

== MeeGo Netbook 1.1 ==

1. Download [http://wiki.meego.com/images/Devel-quality.repo repository file] and copy it to right place
sudo cp /home/$USER/Downloads/Devel-quality.repo /etc/yum.repos.d/

2. Inform zypper about new repository

sudo zypper addrepo /etc/yum.repos.d/Devel-quality.repo
sudo zypper update

== Ubuntu 10.04 ==

1. Add the following to your sources.list (/etc/apt/sources.list)

deb <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/ /</nowiki>

2. Add the repository key

wget <nowiki>http://download.meego.com/live/Tools:/Testing/xUbuntu_10.04/Release.key</nowiki>
sudo apt-key add Release.key
rm Release.key

3. Update your PC's package information

sudo apt-get update

== Ubuntu 10.10 ==

Instructions above, but replace 10.04 with 10.10

== Fedora 13 ==

1. Fedora 13 repository:

<nowiki>http://download.meego.com/live/Tools:/Testing/Fedora13/Tools:Testing.repo</nowiki>

2. Copy the repository file to /etc/yum.repos.d/

Quality/QA-tools/TDriver/Getting Started

2010-11-25T08:01:52Z

Tatlahte:

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

=== Testing Your Application ===

If your application is a Meegotouch application, the qttas plugin will be loaded automatically. If it is a standard Qt application, pass "-testability" as a command line parameter.

=== Connecting to your MeeGo device ===

You need a working network connection to the device. For the N900, see the [[ARM/N900/Tips and Tricks/N900 USB Networking|N900 Networkig Guide]]. TDriver works over TCP/IP, so any device in the network can be tested.

As an example, connection to the N900 we add the N900 ip address into /etc/tdriver/tdriver_parameters.xml:
<pre>
<sut id="sut_qt" template="qt">
<parameter name="qttas_server_ip" value="192.168.2.15" />

</sut>
</pre>

On the device, make sure the package "qttas-server" is installed and "qttasserver" is running as user. If you just installed the package, you will need to restart the applications to make them load the qttas plugin. On the N900, the qttasserver should start automatically and all supported applications should be available.

If you refresh the visualizer, you should see the application content that is running on the N900. Note - If you edit the configuration file, the visualizer must be restarted.

== What's Next ==

=== TODO ===

* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-25T07:30:41Z

Tatlahte:

= Testability Driver Getting Started Guide =

This page describes the installation of the Testability Driver (TDriver) on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

== What's Next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver

2010-11-25T07:28:50Z

Tatlahte:

== Testability Driver (TDriver) ==

TDriver is a test automation driver enabling acceptance testing through the UI or using business logic directly. It is written in Ruby language and enables using any test framework written for Ruby.

See [http://www.youtube.com/watch?v=UL0XmcPKAp8 TDriver in action].

The cucumber tests in the example can be found from [http://gitorious.org/tdriver/tests/trees/master/examples/MeeGo/N900/cucumber/features here].

== Overview ==

TDriver contains few modules:

* agent
* driver
* visualizer

=== Agent ===

TDriver has one agent for Qt based systems where Qt applications on any supported OS can be tested. The Qt agent is called qttasserver.

Agent (qttas-server) is the only component that needs to be installed to the SUT (system under test). It will handle communication with the testing framework and applications. When Qt application starts it will load a testability plugin into the process. The plugin will register the application into qttasserver. Once the application is registered to qttasserver it can be controlled and queried from the testing framework.

If the application does not explicitly load the testability plugin, it can be started with -testability argument:

<pre>
myapp -testability
</pre>

That will cause the testability plugin to be loaded automatically.

=== Driver ===

Driver is the component that will provide the glue between test harness and SUT. You can install driver inside SUT or you can also use another host for driver that will connect to sut over tcp/ip.

TDriver is a ruby class libary which is packaged as a Ruby gem. Package 'rubygem-testability-driver' provides the core functionality and 'rubygem-testability-driver-qt-sut-plugin' provides the qt specific support.

=== Visualizer ===

Visualizer is a helper tool that provides access to UI components of the application. It will help testers to know what objects are contained and what is possible to do with them. You will see a SUT screenshot and an object tree containing all visible object. For Qt applications the objects are fetched from the object tree of the application registered to qttasserver. Visualizer also contains documentation and a small editor to help in scripting and debugging.

== Installation ==

See the [[Quality/QA-tools/TDriver/Getting Started|Getting Started Guide]] for host installation.

== Adding Packages Directly Into image ==

Currently packages are only in devel:quality. Add the devel:quality repository into the ks. file:
<pre>
repo --name=devel-quality-testing --baseurl=http://download.meego.com/live/devel:/quality/testing/
</pre>
And add the meta package:
<pre>
testability-driver
</pre>
And if installing on netbook, if you want the visualizer:
<pre>
testability-driver-visualizer
</pre>

rubygem-cucumber is also available if you have [http://cukes.info Cucumber] tests.

=== Installation From Repos ===

Note! Repo locations will change as soon as the official location is decided.

First you will need to disable core repo and enable Trunk:Testing as they have some conflicting versions

sudo zypper rr core
sudo zypper ar http://download.meego.com/live/Trunk:/Testing/standard/Trunk:Testing.repo

Then you need to enable devel:quality repo as not all components are yet in Trunk:Testing

sudo zypper ar http://download.meego.com/live/devel:/quality/testing/devel:quality.repo

Note! The repo above contains development versions of quality tools. In the future this repo should not be used but while proper end locations are decided it is ok to use this repo. If you experience any problems with this repo please remove it with rr command

sudo zypper rr devel_quality

=== Installing Agent To The Target SUT ===

sudo zypper install qttas-server

This will install the agent. Once you reboot the first time the agent should start automatically. (TODO: This will be changed to lazy load later)

You can start the agent manually by typing:

qttasserver &

=== Installing Environment ===

sudo zypper install testability-driver

This will install the ruby gem for handling qt SUTs and all the dependencies like for example ruby interpreter it self.

=== Testing The Installation ===

TDriver requires rubygems. Make sure you have rubygems defined in rubyopt:

<pre>
export RUBYOPT=rubygems
</pre>
This will tell ruby to use gem packages.

You can test the installation using irb easily:

<pre> [matti@matti-desktop tmp]$ irb
irb(main):001:0> require 'tdriver'
=> true
irb(main):002:0> </pre>

You can also install our testapps and tests and try to run those

sudo zypper install testability-driver-tests

And once installed you can launch the test script:

ruby /usr/share/testability-driver-tests/tc_testapp.rb

And the script will use app 'testapp' and test basic things like launching and closing app, tapping, dragging, flick etc.

=== Installing Visualizer ===

You can install visualizer with a command

sudo zypper install testability-driver-visualizer

You can test visualizer by first making sure qttasserver is running and starting testapp (tdriver-testapp installed in the previous section)

qttasserver &
testapp &

Now make sure you have RUBYOPT set and sut_qt installed and start visualizer

export RUBYOPT=rubygems
sudo zypper install rubygem-testability-driver-qt-sut-plugin
tdriver_visualizer &

Now you should see the visualizer app loading. Select sut_qt from device menu and select file -> refresh. You should now see screenshot of testapp and object tree which contains all visible objects from the application.

== Enabling Logs On The Agent ==

In order to debug you can enable logs on the device. Just create a folder and give appropriate write access so that qttasserver and applications can write in there:

mkdir -p /logs/testability
sudo chmod a+w /logs/testability

Now if you restart qttasserver you will see a log file qttasserver.log being created. For each application loading testability plugin there will be also a file <application_name>.log

=== Known Issues ===

Builds require Qt 4.7. So these rpms will not work on base Fedora installations.

Quality/QA-tools/TDriver

2010-11-25T07:28:11Z

Tatlahte:

Quality/QA-tools/TDriver/Getting Started

2010-11-24T15:15:57Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example "1" button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

We are ready to run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

We can use the tests repository we got the calculator from as an example. From there, we will run one test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
~/tests/test$
</pre>

Everything should be up and running now. You are ready for test development!

== What's Next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T15:11:20Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

Finally, let's run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

Run a test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
</pre>

Everything should be up and running now. You are ready for test development!

== What's Next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T15:10:52Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine.

== Installing required packages from repositories ==

We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

Finally, let's run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

Run a test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
</pre>

Everything should be up and running now. You are ready for test development!

== What's Next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T15:10:04Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine. We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed. We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Let's get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake command is qmake-qt4
make
sudo make install
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

Finally, let's run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

Run a test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
</pre>

Everything should be up and running now. You are ready for test development!

== What's Next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T15:07:44Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine. We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed.

We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

Finally, let's run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

Run a test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
</pre>

Everything should be up and running now. You are ready for test development!

== What's Next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T15:05:53Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine. We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

We are ready to install TDriver packages, so skip to [[#Installing TDriver|Installing TDriver]].

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compiling TDriver from git ==

TDriver components can be installed on most Qt and Ruby supported platforms. On other Linux distributions, search for the equivalent packages that are described in [[#Ubuntu 10.10|Ubuntu 10.10]] and [[#Fedora 14|Fedora 14]] build requirements.

=== Ubuntu 10.10 ===

Install build requirements:
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Compilation ===

Compile and install qttas-server:
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Visualizer:
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should now be installed.

We need an application to test it with, so let's get one. Let's use a classic calculator application that is used in TDriver tests.

Get it from git and compile it:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== Running Automated Tests ==

Finally, let's run an automated test. We will need [[http://cukes.info Cucumber]], so let's install it:
<pre>
sudo gem install cucumber
</pre>

Run a test:
<pre>
# cd <wherever you cloned the tdriver/tests repository>
cd test/
cucumber features/qt_widget_tap.feature:8
</pre>

Something like this should be displayed on the console:
<pre>
~/tests/test$ cucumber features/qt_widget_tap.feature:8
@qt_linux @qt_windows @qt_symbian @qt_meego
Feature: MobyBehaviour::QT::Widget#tap
As a test script writer
I want to use tap method to simulate user tapping or clicking an object,
so that I can test the MobyBehaviour::QT::Widget behaviour

Scenario: Tap a QWidget button # features/qt_widget_tap.feature:8
Given I launch application "calculator" # features/step_definitions/feature_common.rb:65
When I execute "@app.Button(:name => 'oneButton').tap" # features/step_definitions/feature_common.rb:165
Then The calculator display says "1" # features/step_definitions/feature_common.rb:235

1 scenario (1 passed)
3 steps (3 passed)
0m1.598s
</pre>

== What's Next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Making your application load the testability plug-in
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T14:32:37Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine. We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev visualizer
</pre>

Skip to [[#Installing TDriver]].

=== Ubuntu 10.10 ===

To install build requirements
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

Skip to [[#Installing TDriver]].

=== Fedora 14 ===

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

You will need to compile the Qt components. Skip to [[#Compilation|compilation]] .

== Compling TDriver from source repositories ==

=== Compilation ===

Compile and install qttas-server
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Compile and install visualizer
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should be now installed.

We need an application to test it with, so download one. Let's a classic calculator application.

Compilation:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== What's next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Running cucumber tests
* Making your application load the testability plugin
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T14:29:01Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine. We provide repositories for Fedora 13 and Ubuntu 10.04, and more will be added as soon as it's possible from OBS. For other platforms and versions you will need to compile the Qt components from source.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev visualizer
</pre>

=== Ubuntu 10.10 ===

Before the repository is available, you will need to compile the Qt components from see [[#Compilation|below]] .

To install build requirements
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Fedora 14 ===

Before the repository is available, you will need to compile the Qt components from see [[#Compilation|below]] .

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

== Compling TDriver from source repositories ==

=== Compilation ===

Compile and install qttas-server
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Compile and install visualizer
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should be now installed.

We need an application to test it with, so download one. Let's a classic calculator application.

Compilation:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== What's next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Running cucumber tests
* Making your application load the testability plugin
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T14:14:49Z

Tatlahte:

= Testability Driver (TDriver) Getting Started Guide =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions (Ubuntu 10.10 and Fedora 13) will be available as soon as they are available in obs. Before this is available, you will need to compile qttas and visualizer from source. Ruby components require rubygems, which should be available in newer releases.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev visualizer
</pre>

=== Ubuntu 10.10 ===

Before the repository is available, you will need to compile the Qt components from see [[#Compiling TDriver from source|below]] .

To install build requirements
<pre>
sudo apt-get install libxtst-dev libqtwebkit-dev qt4-qmake g++ libqt4-dev
</pre>

Requirements for Ruby components:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this step if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

=== Fedora 14 ===

Before the repository is available, you will need to compile the Qt components from see [[#Compiling TDriver from source|below]] .

Build requirements:
<pre>
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
</pre>

Build requirements for Ruby components:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

== Compiling TDriver from source ==

=== Compilation ===

Compile and install qttas-server
<pre>
git clone http://gitorious.org/tdriver/agent_qt.git # Note that this our development master. See the list of available tags if you want to checkout a released version.
cd agent_qt
qmake -r CONFIG+=no_mobility
make
sudo make install
</pre>

Compile and install visualizer
<pre>
git clone http://gitorious.org/tdriver/visualizer.git
cd visualizer
qmake -r
make
sudo make install
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'"
</pre>

The command above prints out nothing, the ruby components are installed successfully.

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should be now installed.

We need an application to test it with, so download one. Let's a classic calculator application.

Compilation:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Now we are ready to start the qttas-server and the calculator
<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== What's next ==

TODO
* Contacting to MeeGo device
* Tutorial for test creation
* Running cucumber tests
* Making your application load the testability plugin
* Making your application testable

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T13:38:34Z

Tatlahte:

= Testability Driver (TDriver) setup tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev visualizer
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'" # Should print nothing
</pre>

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should be now installed.

We need an application to test it with, so download one. Let's a classic calculator application.

Compilation:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Start the qttas-server and the calculator

<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer &
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, the visualizer will highlight the object that is currently under the cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== What's next ==

TODO
- Contacting to MeeGo device
- Tutorial for test creation
- ??

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T13:37:36Z

Tatlahte:

= Testability Driver (TDriver) setup tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev visualizer
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'" # Should print nothing
</pre>

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should be now installed.

We need an application to test it with, so download one. Let's a classic calculator application.

Compilation:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Start the qttas-server and the calculator

<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer &
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you hover your mouse above the picture, it the visualizer will highlight the object tree will display the object under cursor.

[[File:Visualizer.png|800px|Visualizer window (click to enlarge)]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== What's next ==

TODO
- Contacting to MeeGo device
- Tutorial for test creation
- ??

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T13:36:14Z

Tatlahte:

= Testability Driver (TDriver) setup tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

== Installing required packages from repositories ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''Note - you cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev visualizer
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download the packages from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
sudo yum install rpmdevtools #
rpmdev-setuptree
sudo yum install yum-utils fedora-release-rawhide gcc
yumdownloader --enablerepo=rawhide --source ruby rubygems
sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
rpmbuild --rebuild ruby-*src.rpm # Compilation will take a few minutes
</pre>

Install the ruby packges that were created:
<pre>
cd ~
sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
rpmbuild --rebuild rubygems-*src.rpm
sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
sudo yum install libxslt-devel libxml2-devel
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
</pre>

Try that it works
<pre>
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
ruby -e "require 'tdriver'" # Should print nothing
</pre>

=== Ubuntu 10.04 ===
To install visualizer:
<pre>
sudo apt-get install visualizer qttas-server
</pre>

=== Fedora 13 ===
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server

== Testing the installation ==

Everything should be now installed.

We need an application to test it with, so download one. Let's a classic calculator application.

Compilation:
<pre>
sudo yum install git qt4-qmake gcc-c++
git clone http://git.gitorious.org/tdriver/tests.git
cd tests/calculator
qmake # in Fedora qmake-qt4
make
</pre>

Start the qttas-server and the calculator

<pre>
qttas-server &
./calculator &
</pre>

You should see a simple calculator application. Next, let's start the visualizer.

<pre>
tdriver_visualizer &
</pre>

In the visualizer, select File->Refresh. You should see a picture of the calculator application. If you your mouse above the picture, it the object tree will display the object under cursor.

[[File:Visualizer.png|800px|Visualizer window]]

Right click on an element, for example one button, and select "send tap to SUT". The calculator should receive a click to the "1" button. If so, congratulations you have a working TDriver environment!

== What's next ==

TODO
- Contacting to MeeGo device
- Tutorial for test creation
- ??

=== Links ===

* [https://projects.forum.nokia.com/Testabilitydriver/wiki/ TDriver wiki]
* [https://projects.forum.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/ API Documentation]
* [http://gitorious.org/tdriver/ Gitorious project]

File:Visualizer.png

2010-11-24T13:12:45Z

Tatlahte: Screenshot of the visualizer with calculator application on it.

Screenshot of the visualizer with calculator application on it.

Quality/QA-tools/TDriver/Getting Started

2010-11-24T13:10:06Z

Tatlahte:

Quality/QA-tools/TDriver/Tutorial

2010-11-24T13:09:35Z

Tatlahte: moved Quality/QA-tools/TDriver/Tutorial to Quality/QA-tools/TDriver/Getting Started: Making name correlate with content

#REDIRECT [[Quality/QA-tools/TDriver/Getting Started]]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T13:09:35Z

Tatlahte: moved Quality/QA-tools/TDriver/Tutorial to Quality/QA-tools/TDriver/Getting Started: Making name correlate with content

= Testability Driver (TDriver) tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

== Installing required packages ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories for QA-tools] guide.

=== Ubuntu 10.04 ===

'''You cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

TDriver requires Rubygems and xml libraries:
<pre>
$ sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download it from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
# sudo yum install rpmdevtools #
# rpmdev-setuptree
# sudo yum install yum-utils fedora-release-rawhide gcc
# yumdownloader --enablerepo=rawhide --source ruby rubygems
# sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
# rpmbuild --rebuild ruby-*src.rpm # Will take a while
</pre>

Install the ruby packges that were created:
<pre>
# cd ~
# sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

Next we need rubygems:

<pre>
# rpmbuild --rebuild rubygems-*src.rpm
# sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
</pre>

Install other requirements, required to build native dependencies for ruby gems:
<pre>
# sudo yum install libxslt-devel libxml2-devel
</pre>

=== Fedora 14 ===

Install ruby gems and xml libraries:
<pre>
# sudo yum install rubygems libxslt-devel libxml2-dev ruby-devel
</pre>

== Installing TDriver ==

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
# sudo gem install testability-driver-qt-sut-plugin
</pre>

Try that it works
<pre>
# export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
# ruby -e "require 'tdriver'" # Should print nothing
</pre>

Quality/QA-tools/TDriver/Getting Started

2010-11-24T11:53:35Z

Tatlahte:

Quality/QA-tools/TDriver/Getting Started

2010-11-24T11:39:02Z

Tatlahte:

= Testability Driver (TDriver) tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

'''You cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

== Installing required packages ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories] guide.

=== Ubuntu 10.04 ===

TDriver requires Rubygems and xml libraries:
<pre>
$ sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download it from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
# sudo yum install rpmdevtools #
# rpmdev-setuptree
# sudo yum install yum-utils fedora-release-rawhide gcc
# yumdownloader --enablerepo=rawhide --source ruby rubygems
# sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
# rpmbuild --rebuild ruby-*src.rpm # Will take a while
</pre>

Install the ruby packges that were created:
<pre>
# cd ~
# sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.rpm \
rpmbuild/*/*/noarch/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/noarch/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

# sudo yum install rubygems xslt-devel xml2-devel

=== Fedora 14 ===

# sudo yum install rubygems

=== Installing TDriver ===

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
# sudo gem install testability-driver-qt-sut-plugin
</pre>

Try that it works
<pre>
# export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
# ruby -e "require 'tdriver'" # Should print nothing
</pre>

Quality/QA-tools/TDriver/Getting Started

2010-11-24T11:37:20Z

Tatlahte:

= Testability Driver (TDriver) tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

'''You cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

== Installing required packages ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories] guide.

=== Ubuntu 10.04 ===

TDriver requires Rubygems and xml libraries:
<pre>
$ sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download it from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
# sudo yum install rpmdevtools #
# rpmdev-setuptree
# sudo yum install yum-utils fedora-release-rawhide gcc
# yumdownloader --enablerepo=rawhide --source ruby rubygems
# sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
# rpmbuild --rebuild ruby-*src.rpm # Will take a while
</pre>

Install the ruby packges that were created:
<pre>
# cd ~
# sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.*.i686.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302*.i686.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302*.i686.rpm \
rpmbuild/*/*/noarch/ruby-irb-1.8.7.302*.noarch.rpm \
rpmbuild/*/*/noarch/ruby-rdoc-1.8.7.302*.noarch.rpm
</pre>

# sudo yum install rubygems xslt-devel xml2-devel

=== Fedora 14 ===

# sudo yum install rubygems

=== Installing TDriver ===

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
# sudo gem install testability-driver-qt-sut-plugin
</pre>

Try that it works
<pre>
# export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
# ruby -e "require 'tdriver'" # Should print nothing
</pre>

Quality/QA-tools/TDriver/Getting Started

2010-11-24T11:34:41Z

Tatlahte:

= Testability Driver (TDriver) tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

'''You cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

== Installing required packages ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories] guide.

=== Ubuntu 10.04 ===

TDriver requires Rubygems and xml libraries:
<pre>
$ sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download it from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
# sudo yum install rpmdevtools #
# rpmdev-setuptree
# sudo yum install yum-utils fedora-release-rawhide gcc
# yumdownloader --enablerepo=rawhide --source ruby rubygems
# sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
# rpmbuild --rebuild ruby-*src.rpm # Will take a while
</pre>

Install the ruby packges that were created:
<pre>
# cd ~
# sudo yum localinstall --nogpgcheck \
rpmbuild/*/*/ruby-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/*/ruby-libs-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/*/ruby-devel-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/*/noarch/ruby-irb-1.8.7.302-1.fc13.noarch.rpm \
rpmbuild/*/*/noarch/ruby-rdoc-1.8.7.302-1.fc13.noarch.rpm
</pre>

# sudo yum install rubygems xslt-devel xml2-devel

=== Fedora 14 ===

# sudo yum install rubygems

=== Installing TDriver ===

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
# sudo gem install testability-driver-qt-sut-plugin
</pre>

Try that it works
<pre>
# export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
# ruby -e "require 'tdriver'" # Should print nothing
</pre>

Quality/QA-tools/TDriver/Testability Driver Tutorial

2010-11-24T11:32:46Z

Tatlahte: moved Quality/QA-tools/TDriver/Testability Driver Tutorial to Quality/QA-tools/TDriver/Tutorial

#REDIRECT [[Quality/QA-tools/TDriver/Tutorial]]

Quality/QA-tools/TDriver/Getting Started

2010-11-24T11:32:46Z

Tatlahte: moved Quality/QA-tools/TDriver/Testability Driver Tutorial to Quality/QA-tools/TDriver/Tutorial

= Testability Driver (TDriver) tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

'''You cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

== Installing required packages ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories] guide.

=== Ubuntu 10.04 ===

TDriver requires Rubygems and xml libraries:
<pre>
$ sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download it from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
# sudo yum install rpmdevtools #
# rpmdev-setuptree
# sudo yum install yum-utils fedora-release-rawhide gcc
# yumdownloader --enablerepo=rawhide --source ruby rubygems
# sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
# rpmbuild --rebuild ruby-*src.rpm # Will take a while
</pre>

Install the ruby packges that were created:
<pre>
# cd ~
# sudo yum localinstall --nogpgcheck \
rpmbuild/*/ruby-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/ruby-libs-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/ruby-devel-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/noarch/ruby-irb-1.8.7.302-1.fc13.noarch.rpm \
rpmbuild/*/noarch/ruby-rdoc-1.8.7.302-1.fc13.noarch.rpm
</pre>

# sudo yum install rubygems xslt-devel xml2-devel

=== Fedora 14 ===

# sudo yum install rubygems

=== Installing TDriver ===

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
# sudo gem install testability-driver-qt-sut-plugin
</pre>

Try that it works
<pre>
# export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
# ruby -e "require 'tdriver'" # Should print nothing
</pre>

Quality/QA-tools/TDriver/Getting Started

2010-11-24T11:31:36Z

Tatlahte: Created page with "= Testability Driver (TDriver) tutorial = This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu…"

= Testability Driver (TDriver) tutorial =

This page describes the installation of the Testability Driver on your host machine. Currently supported hosts are Fedora 13 and Ubuntu 10.04. Repositories for newer versions will be available as soon as they are available in obs.

'''You cannot use the Ubuntu 10.04 repository in 10.10. The version is compiled agains Qt 4.6, which is not compatible'''

== Installing required packages ==

First wee need to enable the Testing:Tools repository. See the [http://wiki.meego.com/Quality/QA-tools/How_to_set_up_repositories How to set up repositories] guide.

=== Ubuntu 10.04 ===

TDriver requires Rubygems and xml libraries:
<pre>
$ sudo apt-get install rubygems ruby1.8-dev libxslt-dev libxml2-dev
</pre>

=== Fedora 13 ===

Unfortunately Fedora 13 does not have the required Ruby 1.8.7, so we need to compile and install it first. (If you do not want to compile it yourself, you can download it from [https://github.com/leamas/diaspora/downloads here]).

Compiling ruby (skip this if you downloaded the packages)

<pre>
# sudo yum install rpmdevtools #
# rpmdev-setuptree
# sudo yum install yum-utils fedora-release-rawhide gcc
# yumdownloader --enablerepo=rawhide --source ruby rubygems
# sudo yum install $( rpm -qRp ruby-*src.rpm | grep -v rpmlib) gcc-g++
# rpmbuild --rebuild ruby-*src.rpm # Will take a while
</pre>

Install the ruby packges that were created:
<pre>
# cd ~
# sudo yum localinstall --nogpgcheck \
rpmbuild/*/ruby-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/ruby-libs-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/ruby-devel-1.8.7.302-1.fc13.i686.rpm \
rpmbuild/*/noarch/ruby-irb-1.8.7.302-1.fc13.noarch.rpm \
rpmbuild/*/noarch/ruby-rdoc-1.8.7.302-1.fc13.noarch.rpm
</pre>

# sudo yum install rubygems xslt-devel xml2-devel

=== Fedora 14 ===

# sudo yum install rubygems

=== Installing TDriver ===

Install the Testabiity Driver qt plugin. This will install everything required.
<pre>
# sudo gem install testability-driver-qt-sut-plugin
</pre>

Try that it works
<pre>
# export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc
# ruby -e "require 'tdriver'" # Should print nothing
</pre>

TDriver

2010-11-12T06:30:43Z

Tatlahte: Redirected page to Quality/QA-tools/TDriver

#REDIRECT [[Quality/QA-tools/TDriver]]

Quality/QA-tools/TDriver

2010-11-12T06:30:04Z

Tatlahte:

== Testability Driver (TDriver) ==

TDriver is a test automation driver enabling acceptance testing through the UI or using business logic directly. It is written in Ruby language and enables using any test framework written for Ruby.

See [http://www.youtube.com/watch?v=UL0XmcPKAp8 TDriver in action].

The cucumber tests in the example can be found from [http://gitorious.org/tdriver/tests/trees/master/examples/MeeGo/N900/cucumber/features here].

=== Current status ===

On build 1.0.90.4.20100928.1 TDriver is tested to work N900 and on netbook.

== Overview ==

TDriver contains few modules:

* agent
* driver
* visualizer

=== Agent ===

TDriver has one agent for Qt based systems where Qt applications on any supported OS can be tested. The Qt agent is called qttasserver.

Agent is the only component that needs to be installed to the SUT. It will handle communication with the testing framework and applications. When Qt application starts it will load a testability plugin into the process. The plugin will register the application into qttasserver. Once the application is registered to qttasserver it can be controlled and queried from the testing framework.

If the application does not explicitly load the testability plugin, it can be started with -testability argument:

myapp -testability

That will cause the testability plugin to be loaded automatically.

=== Driver ===

Driver is the component that will provide the glue between test harness and SUT. You can install driver inside SUT or you can also use another host for driver that will connect to sut over tcp/ip.

TDriver is a ruby class libary which is packaged as a Ruby gem. Package 'rubygem-testability-driver' provides the core functionality and 'rubygem-testability-driver-qt-sut-plugin' provides the qt specific support.

=== Visualizer ===

Visualizer is a helper tool that provides access to UI components of the application. It will help testers to know what objects are contained and what is possible to do with them. You will see a SUT screenshot and an object tree containing all visible object. For Qt applications the objects are fetched from the object tree of the application registered to qttasserver. Visualizer also contains documentation and a small editor to help in scripting and debugging.

== Installation on MeeGo ==

== Adding Packages Directly Into image ==

Currently packages are only in devel:quality. Add the devel:quality repository into the ks. file:
<pre>
repo --name=devel-quality-testing --baseurl=http://download.meego.com/live/devel:/quality/testing/
</pre>
And add the meta package:
<pre>
testability-driver
</pre>
And if installing on netbook, if you want the visualizer:
<pre>
testability-driver-visualizer
</pre>

rubygem-cucumber is also available if you have [http://cukes.info Cucumber] tests.

=== Installation From Repos ===

Note! Repo locations will change as soon as the official location is decided.

First you will need to disable core repo and enable Trunk:Testing as they have some conflicting versions

sudo zypper rr core
sudo zypper ar http://download.meego.com/live/Trunk:/Testing/standard/Trunk:Testing.repo

Then you need to enable devel:quality repo as not all components are yet in Trunk:Testing

sudo zypper ar http://download.meego.com/live/devel:/quality/testing/devel:quality.repo

Note! The repo above contains development versions of quality tools. In the future this repo should not be used but while proper end locations are decided it is ok to use this repo. If you experience any problems with this repo please remove it with rr command

sudo zypper rr devel_quality

=== Installing Agent To The Target SUT ===

sudo zypper install qttas-server

This will install the agent. Once you reboot the first time the agent should start automatically. (TODO: This will be changed to lazy load later)

You can start the agent manually by typing:

qttasserver &

=== Installing Environment ===

sudo zypper install testability-driver

This will install the ruby gem for handling qt SUTs and all the dependencies like for example ruby interpreter it self.

=== Testing The Installation ===

TDriver requires rubygems. Make sure you have rubygems defined in rubyopt:

<pre>
export RUBYOPT=rubygems
</pre>
This will tell ruby to use gem packages.

You can test the installation using irb easily:

<pre> [matti@matti-desktop tmp]$ irb
irb(main):001:0> require 'tdriver'
=> true
irb(main):002:0> </pre>

You can also install our testapps and tests and try to run those

sudo zypper install testability-driver-tests

And once installed you can launch the test script:

ruby /usr/share/testability-driver-tests/tc_testapp.rb

And the script will use app 'testapp' and test basic things like launching and closing app, tapping, dragging, flick etc.

=== Installing Visualizer ===

You can install visualizer with a command

sudo zypper install testability-driver-visualizer

You can test visualizer by first making sure qttasserver is running and starting testapp (tdriver-testapp installed in the previous section)

qttasserver &
testapp &

Now make sure you have RUBYOPT set and sut_qt installed and start visualizer

export RUBYOPT=rubygems
sudo zypper install rubygem-testability-driver-qt-sut-plugin
tdriver_visualizer &

Now you should see the visualizer app loading. Select sut_qt from device menu and select file -> refresh. You should now see screenshot of testapp and object tree which contains all visible objects from the application.

== Enabling Logs On The Agent ==

In order to debug you can enable logs on the device. Just create a folder and give appropriate write access so that qttasserver and applications can write in there:

mkdir -p /logs/testability
sudo chmod a+w /logs/testability

Now if you restart qttasserver you will see a log file qttasserver.log being created. For each application loading testability plugin there will be also a file <application_name>.log

=== Known Issues ===

Builds require Qt 4.7. So these rpms will not work on base Fedora installations.

MeeGo Conference 2010/Flight Information

2010-11-11T14:05:40Z

Tatlahte: /* Wednesday 17 */

== Flight Information ==

''Wouldn't it make sense to split the table for arrivals and departures and then sort each table by date and time as with the [http://wiki.maemo.org/Maemo_Summit_2009/Travel Maemo Summit 2009 travel wiki page]?''

Please move your entry from below to the new tables here. Keep the entries sorted by time and date.

===Arrivals===

====Friday 12====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 12:00
| [[user:Nightrose | Lydia Pintscher]]
| Airport (DUB)
| from FRA
|
|-
| 12:45
| [[user:pycage | Martin Grimme]]
| Airport (DUB)
| from MUC
|
|}

====Saturday 13====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 08:55
| [[user:timsamoff | Tim Samoff]]
| Airport (DUB)
| from JFK
|
|-
| 09:00
| [[user:dawnfoster | Dawn Foster]]
| Airport (DUB)
| from ORD
|
|-
| 09:20
| [[user:texrat | Randall Arnold ]] ([http://meego.com/users/texrat texrat])
| Airport (DUB)
| United 3261 from EWR
|
|-
| 09:40
| Timo Rongas ([http://meego.com/users/ronksu ronksu])
| Airport (DUB)
| from CPH
|
|-
| 09:40
| Tatu Lahtela ([http://meego.com/users/tatlahte tatlahte])
| Airport (DUB)
| from CPH
|
|-
| 10:30
| David Greaves ([http://meego.com/users/lbt lbt])
| Airport (DUB)
| from LHR
|
|-
| 12:05
| Dan Leinir Turthra Jensen ([http://meego.com/users/leinir leinir])
| Aurport (DUB)
| EI0235 from LGW
|
|-
| 13:25
| Andrew Flegg ([http://meego.com/users/jaffa Jaffa])
| Airport (DUB)
| EI0267 from BHX
|
|-
| 14:05
| Josep Roura ([http://meego.com/users/netoak netoak])
| Airport (DUB)
| FR7039 from GRO
|
|-
| 16:40
| Henri Bergius ([http://meego.com/users/bergie bergie])
| Airport (DUB)
| AF5014 from CDG
|
|-
| 16:40
| Susanna Huhtanen ([http://maemo.org/profile/view/ihmis-suski/ ihmis-suski])
| Airport (DUB)
| AF5014 from CDG
|
|-
| 17:20
| Attila Csipa ([http://meego.com/users/achipa achipa])
| Airport (DUB)
| LH980 from FRA
|
|-
| 17:35
| [[user:thp|thp]]
| Airport (DUB)
| from LHR
|
|-
| 18:50
| Leonardo da Mata ([http://meego.com/users/barroca barroca])
| Airport (DUB)
| JJ 7922 from LHR
|
|-
| 14:25
| [[user:sivan|sivang]]
| Airport (DUB)
| From LHR
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

====Sunday 14====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 8:50
| Ryan Abel ([http://meego.com/users/generalantilles GeneralAntilles])
| Airport (DUB)
| US Air 722 from PHL
|
|-
| 08:50
| Stephen Gadsby ([http://meego.com/users/sjgadsby sjgadsby])
| Airport (DUB)
| US Air 722 from PHL
|
|-
| 08:55
| Gary Birkett ([http://meego.com/users/lcuk lcuk])
| Airport (DUB)
| FR553 from MAN
|
|-
| 08:55
| Mike Jipping ([http://meego.com/users/frethop frethop])
| Airport (DUB)
| DL164 from JFK
|
|-
| 09:00
| Reggie Suplido ([http://meego.com/users/reggie reggie])
| Airport (DUB)
| EI124 from ORD (Chicago, IL)
|
|-
| 09:20
| Aniello Del Sorbo ([http://meego.com/users/anidel anidel])
| Airport (DUB)
| Flight 126 (Continental) from EWR (Newark, NJ)
|
|-
| 09:40
| Arek Stopczynski ([http://meego.com/users/hopbeat hopbeat])
| Airport (DUB)
| SK537 from CPH
|
|-
| 09:40
| Brendan Le Foll ([http://meego.com/users/arfoll arfoll])
| Airport (DUB)
| 6394 from BCN
|
|-
| 10:10
| Valério Valério ([http://meego.com/users/vdvsx VDVsx])
| Airport (DUB)
| KL3153 from AMS
|
|-
| 12:20
| Daniele Maio ([http://meego.com/users/b0unc3 b0unc3])
| Airport (DUB)
| FR 9427 from BGY
|
|-
| 12:40
| Andrew Olmsted ([http://meego.com/users/fiferboy fiferboy])
| Airport (DUB)
| AC848/BMI123 from YYZ/LHR
|
|-
| 13.35
| Kathy Smith ([http://meego.com/users/revdkathy RevdKathy])
| Airport (DUB)
| SZ593 from NQY
|
|-
| 13.55
| Andrew Zhilin ([http://meego.com/users/wazd wazd])
| Airport (DUB)
| AF5006 from CDG
|
|-
| 14.10
| Carsten Munk ([http://meego.com/users/stskeeps Stskeeps])
| Airport (DUB)
| EI0363 from WAW
|
|-
| 16:40
| timeless
| Airport (DUB)
| AF1099/AF5014
|
|-
| 17:20
| Eero af Heurlin ([http://meego.com/users/rambo rambo])
| Airport (DUB)
| LH 980
|
|-
| 17:20
| Lauri Manner
| Airport (DUB)
| LH 980
|
|-
| 17:25
| Andre Klapper ([http://meego.com/users/andre andre])
| Airport (DUB)
| EI0645 from PRG
|
|-
| 21:55
| Piotr Pokora ([http://meego.com/users/piotras piotras])
| Airport (DUB)
| FR1979
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

====Monday 15====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 06:50
| Sanjeev Visvanatha ([http://meego.com/users/eipi eipi])
| Airport (DUB)
| Flight CO22 from EWR
|
|-
| 07:55
| Lucas Maneos ([http://meego.com/users/lm lm])
| Airport (DUB)
| Flight BD0121 from LHR
|
|-
| 08:55
| Mart Roosmaa ([http://meego.com/users/roosmaa roosmaa])
| Airport (DUB)
| Flight FR553 from MAN
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

===Departures===

====Wednesday 17====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 09:00
| Sanjeev Visvanatha ([http://meego.com/users/eipi eipi])
| Airport (DUB)
| CO23 to EWR (Newark, NJ)
|
|-
| 09:00
| Aniello Del Sorbo ([http://meego.com/users/ anidel])
| Airport (DUB)
| to EWR (Newark, NJ)
|
|-
| 13:45
| Kathy Smith ([http://meego.com/users/revdkathy RevdKathy])
| Airport (DUB)
| to NQY (Newquay, Cornwall)
|
|-
| 16:00
| Piotr Pokora ([http://meego.com/users/piotras piotras])
| Airport (DUB)
| FR1978
|
|-
| 16:30
| [[user:thp|thp]]
| Airport (DUB)
| to VIE
|
|-
| 18:10
| Mart Roosmaa ([http://meego.com/users/roosmaa roosmaa])
| Airport (DUB)
| to MAN
|
|-
| 18:40
| Andrew Flegg ([http://meego.com/users/jaffa Jaffa])
| Airport (DUB)
| EI0276 to BHX
|
|-
| 18:45
| Eero af Heurlin ([http://meego.com/users/rambo rambo])
| Airport (DUB)
| SK 2538
|
|-
| 18:45
| Tatu Lahtela ([http://meego.com/users/tatlahte tatlahte])
| Airport (DUB)
| SK 2538
|
|-
| 18:45
| Lauri Manner
| Airport (DUB)
| SK 2538
|
|-
| 20:00
| Adam Reviczky ([[user:Reviczky|reviczky]])
| Airport (DUB)
| FR118 to LGW
|
|-
| 21:05
| Lucas Maneos ([http://meego.com/users/lm lm])
| Airport (DUB)
| BD0132 to LHR
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

====Thursday 18====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 06:00
| Valério Valério ([http://meego.com/users/vdvsx VDVsx])
| Airport (DUB)
| KL3152 to AMS
|
|-
| 06:35
| Daniele Maio ([http://meego.com/users/b0unc3 b0unc3])
| Airport (DUB)
| FR 9426 to BGY
|
|-
| 07:00
| Lydia Pintscher ([http://meego.com/users/Nightrose Nightrose])
| Airport (DUB)
| to FRA
|
|-
| 07:20
| Carsten Munk ([http://meego.com/users/stskeeps Stskeeps])
| Airport (DUB)
| EI0362 to WAW
|
|-
| 09:10
| Henri Bergius ([http://meego.com/users/bergie bergie])
| Airport (DUB)
| AF5001 to CDG
|
|-
| 09:10
| Susanna Huhtanen ([http://maemo.org/profile/view/ihmis-suski/ ihmis-suski])
| Airport (DUB)
| AF5001 to CDG
|
|-
| 10:20
| Josep Roura ([http://meego.com/users/netoak NetOak])
| Airport (DUB)
| FR7038 to GRO
|
|-
| 10:45
| [http://meego.com/users/dawnfoster Dawn Foster]
| Airport (DUB)
| to JFK
|
|-
| 10:45
| Mike Jipping [http://meego.com/users/frethop frethop]
| Airport (DUB)
| DL165 to JFK
|
|-
| 11:05
| Reggie Suplido ([http://meego.com/users/reggie reggie])
| Airport (DUB)
| SK538 to CPH
|
|-
| 11:05
| Ryan Abel ([http://meego.com/users/generalantilles GeneralAntilles])
| Airport (DUB)
| US Air 723 to PHL
|
|-
| 11:05
| Stephen Gadsby ([http://meego.com/users/sjgadsby sjgadsby])
| Airport (DUB)
| US Air 723 to PHL
|
|-
| 11:40
| Andre Klapper ([http://meego.com/users/andre andre])
| Airport (DUB)
| IE0644 to PRG
|
|-
| 11:55
| Andrew Zhilin ([http://meego.com/users/wazd wazd])
| Airport (DUB)
| AF5005 to CDG
|
|-
| 13:00
| Randall Arnold (texrat)
| Airport (DUB)
| United 4925 to ORD
|
|-
| 13:55
| Brendan Le Foll ([http://meego.com/users/arfoll arfoll])
| Airport (DUB)
| 6395
|
|-
| 14:50
| timeless
| Airport (DUB)
| AF5009/AF1798
|
|-
| 15:00
| Andrew Olmsted ([http://meego.com/users/fiferboy fiferboy])
| Airport (DUB)
| EI3296 to CWL
| Staying extra days after conference
|-
| 16:00
| Martin Grimme ([http://meego.com/users/pycage pycage])
| Airport (DUB)
| EI356 to MUC
|
|-
| 18:10
| Gary Birkett ([http://meego.com/users/lcuk lcuk])
| Airport (DUB)
| FR556 to MAN
|
|-
| 18:45
| Arek Stopczynski ([http://meego.com/users/hopbeat hopbeat])
| Airport (DUB)
| SK2538 to CPH
|
|-
| 20:30
| Dan Leinir Turthra Jensen ([http://meego.com/users/leinir leinir])
| Airport (DUB)
| EI0248 to LGW
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number to airport
| ...
|}

====Friday 19 ====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 13:15
| David Greaves ([http://meego.com/users/lbt lbt])
| Airport (DUB)
| to LHR
|
|-
|}

====Saturday 20====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 10:45
| [[user:timsamoff | Tim Samoff]]
| Airport (DUB)
| to JFK
| My wife arrives on the 17th and we're staying through Saturday.
|}

==Old list (please don't add anything here - move to the tables above)==

{| border="1"
! Participant name
! Arrival flight info
! Departure flight info
! Comments
|-
| Andrea Grandi ([http://meego.com/users/andreagrandi andreagrandi])
| Flight 9907 Depart PSA at 07:00 and arrive DUB at 08:45 - Sat, 13/November/2010
| Dublin BA British Airways 5964 at 13:15, Wed 17th Nov --> London BA British Airways 602 at 16:45 --> Pisa at 19:55
|
|}