Contents |
This page describes the installation of the Testability Driver (TDriver) on your host machine.
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 How to set up repositories for QA-tools guide.
TDriver requires Rubygems and xml libraries:
sudo apt-get install ruby rubygems ruby1.8-dev libxslt-dev libxml2-dev
We are ready to install TDriver packages, so skip to Installing TDriver.
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 here).
Compiling ruby (skip this step if you downloaded the packages)
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
Install the ruby packges that were created:
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
Next we need rubygems:
rpmbuild --rebuild rubygems-*src.rpm sudo yum localinstall --nogpgcheck rpmbuild/*/*/rubygems-1.3.7*.noarch.rpm
Install other requirements, required to build native dependencies for ruby gems:
sudo yum install libxslt-devel libxml2-devel
We are ready to install TDriver packages, so skip to Installing TDriver.
You will need to compile the Qt components. Skip to compilation .
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 and Fedora 14 build requirements.
Build requriements for ubuntu 10.04:
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libwebkit4-dev
Build requirements for Ubuntu 10.10:
sudo apt-get install libqt4-dev x11proto-xext-dev libxtst-dev libqtwebkit-dev
Build requirements:
sudo yum install libxtst-devel libqtwebkit-devel qt4-qmake gcc-c++ libqt4-devel
Build requirements for Ruby components:
sudo yum install libxslt-devel libxml2-devel
Compile and install qttas-server:
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
Visualizer:
git clone http://git.gitorious.org/tdriver/visualizer.git cd visualizer qmake -r make sudo make install
Install the Testabiity Driver qt plugin. This will install everything required.
sudo gem install testability-driver-qt-sut-plugin # This will take a few minutes
Try that it works
export RUBYOPT="rubygems" # This should go to your login file e.g. .bashrc ruby -e "require 'tdriver'"
The command above prints out nothing, the ruby components are installed successfully.
To install visualizer and qttas server:
sudo apt-get install visualizer qttas
sudo yum install --nogpgcheck testability-driver-visualizer qttas-server
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:
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
For ubuntu 10.04
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
Now we are ready to start the qttas-server and the calculator
qttasserver & calculator -testability &
You should see a simple calculator application. Next, let's start the visualizer.
tdriver_visualizer & # If you compiled visualizer from source, it will be under /opt/tdriver_visualizer
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.
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!
We are ready to run an automated test. We will need [Cucumber], so let's install it:
sudo gem install cucumber
We still need to edit the tdriver parameters. Add the following line to /etc/tdriver/tdriver_parameters.xml inside <parameters> tag:
<parameter name="default_sut" value="sut_qt"/>
We can use the tests repository we got the calculator from as an example. From there, we will run one test:
# cd <wherever you cloned the tdriver/tests repository> cd test/ cucumber features/qt_widget_tap.feature:8 # Run one scenario from one feature
Something like this should be displayed on the console:
~/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$
Everything should be up and running now. You are ready for test development!
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.
You need a working network connection to the device. For the N900, see the 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:
<sut id="sut_qt" template="qt"> <parameter name="qttas_server_ip" value="192.168.2.15" /> <!-- other parameters.... --> </sut>
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.