MeeGo wiki - User contributions [en]

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-05-09T08:45:24Z

Esmietti: /* conductor configuration */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

There is a flasher plug-in example in the OTS source code under the example folder.

See example video from youtube: http://www.youtube.com/watch?v=exmJ6T-fjlM

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the '''network-manager''' and remove all usb* settings from the '''/etc/network/interfaces'''.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses. '''You cannot use 192.168.2.15 address for testing! That is used for setting up the devices!'''

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

Test that conductors are configured correctly and flashing is working:
sudo su
export OTS_WORKER_NUMBER=1
conductor -u http://url/to/image.bin -v

You should see something like:
...
INFO using config file /etc/conductor_1.conf
...
INFO Loaded flasher 'meego-ai-flasher-n900'
...
INFO Host IP 192.168.3.14;Device IP 192.168.3.15
...

Quality/QA-tools/OTS/UserDocumentation/Installation rpm

2011-05-04T09:19:37Z

Esmietti: /* How to install N900 automation tools to OTS worker */

= OTS 0.8.x installation RPM =

These instructions have been tested with Fedora 13. Execute commands as root.

In MeeGo netbook, at least following packages needs to be installed manually:
python-amqp, python-django, minixsv, rabbitmq-server

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing source to /etc/yum.repos.d/
cd /etc/yum.repos.d/
yum install wget nano
wget http://download.meego.com/live/Tools:/Testing/Fedora13/Tools:Testing.repo

* Update the repositories
yum check-update

'''Build packages from source (optional)'''
* Install git core
yum install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
yum rpm-build python-setuptools

* Build packages
mv ots python-ots-0.8.x
tar czf python-ots-0.8.x.tar.gz python-ots-0.8.x
rpmbuild -tb python-ots-0.8.x.tar.gz

== OTS server installation ==

* Install dependencies
yum install Django python-amqplib python-configobj rabbitmq-server test-definition
easy_install minixsv
yum install python-setuptools

* Install OTS server components
yum install python-ots-common python-ots-results python-ots-server
or if you are using own built packages
rpm -i ...

* Add rabbitmq to start on boot
chkconfig --add rabbitmq-server
chkconfig rabbitmq-server on

* Start rabbitmq server
/etc/init.d/rabbitmq-server start

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins

See plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* Start OTS server
ots_server

== OTS worker installation ==

* Install dependencies
yum install python-amqplib testrunner-lite

* Install OTS worker packages
yum install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Start OTS worker (as root)
ots_worker

NOTE: if worker failed to start up with error like "socket.error: [Errno 113] No route to host", check that ots-worker is able to connect to ots-server

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
yum install python-ots-tools

* Trigger a test run
ots_trigger -s localhost:8080 -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Install dependencies
yum install meego-ai-flaster eat-host

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2.tar.gz
Compile the flasher

* Configure conductor to use rpm and fetch /var/log/messages
sudo nano /etc/conductor.conf

* Test manually that everything is OK, this is executed in the worker
sudo conductor -u <image url>
* Start OTS worker
sudo ots_worker

Quality/QA-tools/OTS/UserDocumentation/Installation rpm

2011-05-04T09:18:47Z

Esmietti: /* OTS worker installation */

= OTS 0.8.x installation RPM =

These instructions have been tested with Fedora 13. Execute commands as root.

In MeeGo netbook, at least following packages needs to be installed manually:
python-amqp, python-django, minixsv, rabbitmq-server

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing source to /etc/yum.repos.d/
cd /etc/yum.repos.d/
yum install wget nano
wget http://download.meego.com/live/Tools:/Testing/Fedora13/Tools:Testing.repo

* Update the repositories
yum check-update

'''Build packages from source (optional)'''
* Install git core
yum install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
yum rpm-build python-setuptools

* Build packages
mv ots python-ots-0.8.x
tar czf python-ots-0.8.x.tar.gz python-ots-0.8.x
rpmbuild -tb python-ots-0.8.x.tar.gz

== OTS server installation ==

* Install dependencies
yum install Django python-amqplib python-configobj rabbitmq-server test-definition
easy_install minixsv
yum install python-setuptools

* Install OTS server components
yum install python-ots-common python-ots-results python-ots-server
or if you are using own built packages
rpm -i ...

* Add rabbitmq to start on boot
chkconfig --add rabbitmq-server
chkconfig rabbitmq-server on

* Start rabbitmq server
/etc/init.d/rabbitmq-server start

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins

See plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* Start OTS server
ots_server

== OTS worker installation ==

* Install dependencies
yum install python-amqplib testrunner-lite

* Install OTS worker packages
yum install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Start OTS worker (as root)
ots_worker

NOTE: if worker failed to start up with error like "socket.error: [Errno 113] No route to host", check that ots-worker is able to connect to ots-server

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
yum install python-ots-tools

* Trigger a test run
ots_trigger -s localhost:8080 -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Install dependencies
yum install meego-ai-flaster eat-host

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2.tar.gz
Compile the flasher

* Configure conductor to use rpm and fetch /var/log/messages
sudo nano /etc/conductor.conf

* If you want run ots_worker as user, copy SSH keys to the user and make udev rule for n900
install-eat-key.sh
sudo nano /etc/udev/rules.d/meego-n900.rules
SUBSYSTEMS=="usb", ATTR{idVendor}=="0421", ATTR{idProduct}=="0105", GROUP="<group>", MODE="0664"

* Create a power_cycle.sh script for turning N900 on/off. This requires external accessory, like [[Quality/QA-tools/hat-control|HAT]]
sudo nano /usr/bin/power_cycle.sh

#!/bin/bash

hat_drv &
hat_ctrl -pwr1=off
hat_ctrl -usb1data=off
hat_ctrl -usb1pwr=off
sleep 2;
hat_ctrl -usb1pwr=on
hat_ctrl -usb1data=on
hat_ctrl -pwr1=on
killall hat_drv

* Test manually that everything is OK, this is executed in the worker
conductor -u <image url>
* Start OTS worker
ots_worker

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-05-04T09:17:15Z

Esmietti: /* Introduction */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

There is a flasher plug-in example in the OTS source code under the example folder.

See example video from youtube: http://www.youtube.com/watch?v=exmJ6T-fjlM

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the '''network-manager''' and remove all usb* settings from the '''/etc/network/interfaces'''.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

Test that conductors are configured correctly and flashing is working:
sudo su
export OTS_WORKER_NUMBER=1
conductor -u http://url/to/image.bin -v

You should see something like:
...
INFO using config file /etc/conductor_1.conf
...
INFO Loaded flasher 'meego-ai-flasher-n900'
...
INFO Host IP 192.168.3.14;Device IP 192.168.3.15
...

Quality/QA-tools/OTS/UserDocumentation/Installation

2011-05-04T09:15:07Z

Esmietti: /* OTS tools */

= OTS 0.8.x installation Ubuntu =

If using 0.1.x version, see [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration from 0.1.x to 0.8.x]] document.

== Used hardware ==

:1 x Server (Ubuntu 10.10)
:1 x Client (Ubuntu 10.10)
::1 x HAT controller
:: 1 x Power cable
:: 1 x Power supply
:: 2 x USB A-B cable
:: 1 x USB A-microB cable
:: 1 x N900

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing apt source to /etc/apt/sources.list
sudo nano /etc/apt/sources.list
deb http://download.meego.com/live/Tools:/Testing/xUbuntu_10.10/ /
Notice that if you are using Ubuntu 10.04, change the path.

* Add repository keys
gpg --keyserver subkeys.pgp.net --recv-keys 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

* Update the repositories
sudo apt-get update

'''Build packages from source (optional)'''
* Install git core
sudo apt-get install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
sudo apt-get install dpkg-dev debhelper python-setuptools

* Build packages
cd ots
dpkg-buildpackage -rfakeroot

== OTS server installation ==

* Install dependencies
sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition

* Install OTS server components
sudo apt-get install python-ots-common python-ots-results python-ots-server
Or if you are using own built packages
sudo dpkg -i ...

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins
[[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger plug-in]] (recommended)
[[Quality/QA-tools/OTS/Plugins/Email|Email plug-in]] (recommended)

See more plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* If logger plug-in is installed
Change permissions to logging directory
sudo chown www-data:www-data /var/log/ots

Now the OTS server can be used via apache (django_xmlrpc).

* If logger plug-in is not installed
Change user permissions to logging directory
sudo chown <user>:<group> /var/log/ots

* Start rabbitmq-server
/etc/init.d/rabbitmq-server start

ots_server

== OTS worker installation ==

* Install dependencies
sudo apt-get install python-amqplib testrunner-lite

* Install OTS worker packages
sudo apt-get install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Start OTS worker
sudo ots_worker

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
sudo apt-get install python-ots-tools

* Trigger a test run
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

== How to install N900 automation tools to OTS worker ==

* Remove network-manager, because it breaks the USB connection. See more information from autotest-guide.

* Install dependencies
sudo apt-get install meego-ai-flasher eat-host-ubuntu

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb
sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb

* Start HAT driver
sudo hat_drv &

* Test manually that everything is OK, this is executed in the worker
sudo conductor -u <image url>

* Start OTS worker
sudo ots_worker

Quality/QA-tools/OTS/UserDocumentation/Installation

2011-05-04T09:14:40Z

Esmietti: /* OTS worker installation */

= OTS 0.8.x installation Ubuntu =

If using 0.1.x version, see [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration from 0.1.x to 0.8.x]] document.

== Used hardware ==

:1 x Server (Ubuntu 10.10)
:1 x Client (Ubuntu 10.10)
::1 x HAT controller
:: 1 x Power cable
:: 1 x Power supply
:: 2 x USB A-B cable
:: 1 x USB A-microB cable
:: 1 x N900

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing apt source to /etc/apt/sources.list
sudo nano /etc/apt/sources.list
deb http://download.meego.com/live/Tools:/Testing/xUbuntu_10.10/ /
Notice that if you are using Ubuntu 10.04, change the path.

* Add repository keys
gpg --keyserver subkeys.pgp.net --recv-keys 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

* Update the repositories
sudo apt-get update

'''Build packages from source (optional)'''
* Install git core
sudo apt-get install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
sudo apt-get install dpkg-dev debhelper python-setuptools

* Build packages
cd ots
dpkg-buildpackage -rfakeroot

== OTS server installation ==

* Install dependencies
sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition

* Install OTS server components
sudo apt-get install python-ots-common python-ots-results python-ots-server
Or if you are using own built packages
sudo dpkg -i ...

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins
[[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger plug-in]] (recommended)
[[Quality/QA-tools/OTS/Plugins/Email|Email plug-in]] (recommended)

See more plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* If logger plug-in is installed
Change permissions to logging directory
sudo chown www-data:www-data /var/log/ots

Now the OTS server can be used via apache (django_xmlrpc).

* If logger plug-in is not installed
Change user permissions to logging directory
sudo chown <user>:<group> /var/log/ots

* Start rabbitmq-server
/etc/init.d/rabbitmq-server start

ots_server

== OTS worker installation ==

* Install dependencies
sudo apt-get install python-amqplib testrunner-lite

* Install OTS worker packages
sudo apt-get install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Start OTS worker
sudo ots_worker

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
sudo apt-get install python-ots-tools

* Trigger a test run
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Remove network-manager, because it breaks the USB connection. See more information from autotest-guide.

* Install dependencies
sudo apt-get install meego-ai-flasher eat-host-ubuntu

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb
sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb

* Start HAT driver
sudo hat_drv &

* Test manually that everything is OK, this is executed in the worker
sudo conductor -u <image url>

* Start OTS worker
sudo ots_worker

Quality/QA-tools/OTS/UserDocumentation/Installation

2011-05-04T09:14:00Z

Esmietti: /* How to install N900 automation tools to OTS worker */

= OTS 0.8.x installation Ubuntu =

If using 0.1.x version, see [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration from 0.1.x to 0.8.x]] document.

== Used hardware ==

:1 x Server (Ubuntu 10.10)
:1 x Client (Ubuntu 10.10)
::1 x HAT controller
:: 1 x Power cable
:: 1 x Power supply
:: 2 x USB A-B cable
:: 1 x USB A-microB cable
:: 1 x N900

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing apt source to /etc/apt/sources.list
sudo nano /etc/apt/sources.list
deb http://download.meego.com/live/Tools:/Testing/xUbuntu_10.10/ /
Notice that if you are using Ubuntu 10.04, change the path.

* Add repository keys
gpg --keyserver subkeys.pgp.net --recv-keys 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

* Update the repositories
sudo apt-get update

'''Build packages from source (optional)'''
* Install git core
sudo apt-get install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
sudo apt-get install dpkg-dev debhelper python-setuptools

* Build packages
cd ots
dpkg-buildpackage -rfakeroot

== OTS server installation ==

* Install dependencies
sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition

* Install OTS server components
sudo apt-get install python-ots-common python-ots-results python-ots-server
Or if you are using own built packages
sudo dpkg -i ...

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins
[[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger plug-in]] (recommended)
[[Quality/QA-tools/OTS/Plugins/Email|Email plug-in]] (recommended)

See more plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* If logger plug-in is installed
Change permissions to logging directory
sudo chown www-data:www-data /var/log/ots

Now the OTS server can be used via apache (django_xmlrpc).

* If logger plug-in is not installed
Change user permissions to logging directory
sudo chown <user>:<group> /var/log/ots

* Start rabbitmq-server
/etc/init.d/rabbitmq-server start

ots_server

== OTS worker installation ==

* Install dependencies
sudo apt-get install python-amqplib testrunner-lite

* Install OTS worker packages
sudo apt-get install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Change permissions to OTS worker log
sudo chown <user>:<group> /var/log/ots.log

* Start OTS worker
ots_worker

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
sudo apt-get install python-ots-tools

* Trigger a test run
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Remove network-manager, because it breaks the USB connection. See more information from autotest-guide.

* Install dependencies
sudo apt-get install meego-ai-flasher eat-host-ubuntu

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb
sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb

* Start HAT driver
sudo hat_drv &

* Test manually that everything is OK, this is executed in the worker
sudo conductor -u <image url>

* Start OTS worker
sudo ots_worker

Quality/QA-tools/OTS/UserDocumentation/Upgrading

2011-05-04T09:12:03Z

Esmietti: /* 0.8.3 - 0.8.4 */

= Upgrading OTS =

== 0.8.3 - 0.8.4 ==
* Backup all configuration files before updating
* Multiple device support added, even if you use '''only one device''' check following:
** Changes to /etc/conductor.conf
** Update meego-ai-flasher (>= 0.1.4) and [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] packages!
** Even if you use only one device, remove usb0 configurations from /etc/network/interfaces
** [[Quality/QA-tools/OTS/UserDocumentation/Multiple_device| See this instructions!]]
* Changes to QAReports configuration file /etc/ots_plugins_qareports.conf
** Added proxy and attachment upload settings

== 0.8.2 - 0.8.3 ==
* Changes in ots_plugin_qareports.conf
** Add new parameters
* Only new features
** Test plan based execution
** Chroot support
** See [[Quality/QA-tools/OTS/UserDocumentation/Usage|how to]] use these features

== 0.8.1 - 0.8.2 ==
* New django package added, effects to all plug-ins
** See [[Quality/QA-tools/OTS/Plugins/Django|Django instructions]].
** See [[Quality/QA-tools/OTS/DeveloperDocs/Plugins|plug-ins instructions]].

== 0.8.0 - 0.8.1 ==
* Plug-in namespace changed, effects to Logger and QA-Reports plug-ins
** For logger update web page content, see step 8 from [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger documentation]].
** For QA-Reports, configuration file name has changed. Move /etc/ots_qareports_plugin.conf to /etc/ots_plugin_qareports.conf

== 0.1.x - 0.8.0 ==

See [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration document]].

Quality/QA-tools/OTS/UserDocumentation/Upgrading

2011-05-03T08:20:58Z

Esmietti: /* 0.8.3 - 0.8.4 */

= Upgrading OTS =

== 0.8.3 - 0.8.4 ==
* Backup all configuration files before updating
* Multiple device support added, even if you use '''only one device''' update your configuration files!
** Changes to /etc/conductor.conf
** Update meego-ai-flasher (>= 0.1.4) and [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] packages!
** [[Quality/QA-tools/OTS/UserDocumentation/Multiple_device| See this instructions!]]
* Changes to QAReports configuration file /etc/ots_plugins_qareports.conf
** Added proxy and attachment upload settings

== 0.8.2 - 0.8.3 ==
* Changes in ots_plugin_qareports.conf
** Add new parameters
* Only new features
** Test plan based execution
** Chroot support
** See [[Quality/QA-tools/OTS/UserDocumentation/Usage|how to]] use these features

== 0.8.1 - 0.8.2 ==
* New django package added, effects to all plug-ins
** See [[Quality/QA-tools/OTS/Plugins/Django|Django instructions]].
** See [[Quality/QA-tools/OTS/DeveloperDocs/Plugins|plug-ins instructions]].

== 0.8.0 - 0.8.1 ==
* Plug-in namespace changed, effects to Logger and QA-Reports plug-ins
** For logger update web page content, see step 8 from [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger documentation]].
** For QA-Reports, configuration file name has changed. Move /etc/ots_qareports_plugin.conf to /etc/ots_plugin_qareports.conf

== 0.1.x - 0.8.0 ==

See [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration document]].

Quality/QA-tools/OTS/UserDocumentation/Upgrading

2011-04-29T07:00:19Z

Esmietti: /* Upgrading OTS */

= Upgrading OTS =

== 0.8.3 - 0.8.4 ==
* Backup all configuration files before updating
* Multiple device support added, even if you use '''only one device''' update your configuration files!
** Changes to /etc/conductor.conf
** Update meego-ai-flasher and meego-ai packages!
** [[Quality/QA-tools/OTS/UserDocumentation/Multiple_device| See this instructions!]]
* Changes to QAReports configuration file /etc/ots_plugins_qareports.conf
** Added proxy and attachment upload settings

== 0.8.2 - 0.8.3 ==
* Changes in ots_plugin_qareports.conf
** Add new parameters
* Only new features
** Test plan based execution
** Chroot support
** See [[Quality/QA-tools/OTS/UserDocumentation/Usage|how to]] use these features

== 0.8.1 - 0.8.2 ==
* New django package added, effects to all plug-ins
** See [[Quality/QA-tools/OTS/Plugins/Django|Django instructions]].
** See [[Quality/QA-tools/OTS/DeveloperDocs/Plugins|plug-ins instructions]].

== 0.8.0 - 0.8.1 ==
* Plug-in namespace changed, effects to Logger and QA-Reports plug-ins
** For logger update web page content, see step 8 from [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger documentation]].
** For QA-Reports, configuration file name has changed. Move /etc/ots_qareports_plugin.conf to /etc/ots_plugin_qareports.conf

== 0.1.x - 0.8.0 ==

See [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration document]].

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-15T06:34:16Z

Esmietti: /* Introduction */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

There is a flasher plug-in example in the OTS source code under the example folder.

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the '''network-manager''' and remove all usb* settings from the '''/etc/network/interfaces'''.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

Test that conductors are configured correctly and flashing is working:
sudo su
export OTS_WORKER_NUMBER=1
conductor -u http://url/to/image.bin -v

You should see something like:
...
INFO using config file /etc/conductor_1.conf
...
INFO Loaded flasher 'meego-ai-flasher-n900'
...
INFO Host IP 192.168.3.14;Device IP 192.168.3.15
...

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:41:50Z

Esmietti: /* Multiple device support */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the '''network-manager''' and remove all usb* settings from the '''/etc/network/interfaces'''.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

Test that conductors are configured correctly and flashing is working:
sudo su
export OTS_WORKER_NUMBER=1
conductor -u http://url/to/image.bin -v

You should see something like:
...
INFO using config file /etc/conductor_1.conf
...
INFO Loaded flasher 'meego-ai-flasher-n900'
...
INFO Host IP 192.168.3.14;Device IP 192.168.3.15
...

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:22:32Z

Esmietti: /* conductor configuration */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the '''network-manager''' and remove all usb* settings from the '''/etc/network/interfaces'''.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

Test that conductors are configured correctly and flashing is working:
sudo su
export OTS_WORKER_NUMBER=1
conductor -u http://url/to/image.bin -v

You should see something like:
...
INFO using config file /etc/conductor_1.conf
...
INFO Loaded flasher 'meego-ai-flasher-n900'
...
INFO Host IP 192.168.3.14;Device IP 192.168.3.15
...

== Testing ==

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:15:54Z

Esmietti: /* conductor configuration */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the '''network-manager''' and remove all usb* settings from the '''/etc/network/interfaces'''.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

Test that conductors are configured correctly and flashing is working:
sudo su
export OTS_WORKER_NUMBER=1
conductor -u http://url/to/image.bin -v

You should see something like:
...
INFO using config file /etc/conductor_1.conf
...
INFO Loaded flasher 'meego-ai-flasher-n900'
...

== Testing ==

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:08:51Z

Esmietti: /* Setup and configuration */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the '''network-manager''' and remove all usb* settings from the '''/etc/network/interfaces'''.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

== Testing ==

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:08:30Z

Esmietti: /* Setup and configuration */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

Remove the network-manager and remove all usb* settings from the /etc/network/interfaces.

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

== Testing ==

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:07:53Z

Esmietti: /* conductor configuration */

= Multiple device support =

== Introduction ==

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

'''Note!''' For MeeGo N900, you need the latest [http://meego-qa-tools.digia.com/meego-ai/meego-ai-optimized.tar.gz meego-ai] and [https://meego.gitorious.org/meego-quality-assurance/meego-ai-flasher meego-ai-flasher]!

== Setup and configuration ==

This guideline assumes that you have HAT switchbox and two N900 devices.

Install OTS worker normally, [[Quality/QA-tools/OTS/UserDocumentation|check installation guidelines]].

=== Wiring ===

[[File:20110414_002.jpg]]

You need one HAT, two N900 devices and lots of cables:
* 3 x USB A-B cables from the PC to HAT
* 1 x Power cable to HAT
* 2 x Power cable from HAT to JIGs
* 2 x USB A-microB cables from HAT to JIGs

=== ots-worker configuration ===

Basically you need to start two ots-worker programs in one PC.

If both devices are using the same OTS server and queue, then you can use the default /etc/ots.ini file. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2

If you want to dedicated the other device to some other server or queue, create a copy from the default ots.ini file and make your changes to that. Start workers as '''root''' in different shells or screen windows:
ots_worker -n 1
ots_worker -n 2 -c /your/new/ots.ini

Both workers should be able to connect to OTS server normally, check that they have different worker id:
ots.worker.worker - INFO - Starting the worker 1...

=== conductor configuration ===

You need always own conductor.conf per device. Copy the default conductor.conf to first device:
sudo cp /etc/conductor.conf /etc/conductor_1.conf

And for second device:
sudo cp /etc/conductor.conf /etc/conductor_2.conf

The most important thing in those configuration files is to define the default flasher and IP addresses.

Recommended IPs for devices:
* conductor_1.conf, host: 192.168.3.14, device: 192.168.3.15
* conductor_2.conf, host: 192.168.4.14, device: 192.168.4.15

== Testing ==

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:04:25Z

Esmietti: /* Multiple device support */

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T12:02:26Z

Esmietti: /* Multiple device support */

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T11:56:02Z

Esmietti:

File:20110414 002.jpg

2011-04-14T11:55:03Z

Esmietti: Multiple devices connected to HAT

Multiple devices connected to HAT

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T11:54:09Z

Esmietti: /* Setup and configuration */

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T11:11:29Z

Esmietti: /* Introduction */

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T11:10:56Z

Esmietti: /* Multiple device support */

Quality/QA-tools/OTS/UserDocumentation/Multiple device

2011-04-14T07:36:00Z

Esmietti: Created page with "= Multiple device support = This feature has been added to 0.8.4 version. Multiple device support means that one OTS worker can handle multiple devices simultaneously and execu..."

= Multiple device support =

This feature has been added to 0.8.4 version.

Multiple device support means that one OTS worker can handle multiple devices simultaneously and execute tests parallel. One worker can include multiple ots-worker instances and they work individually. Only limitation is amount of the switchbox ports (if using USB devices), this limitation in HAT switchbox is 2.

== Setup ==

== Testing ==

Quality/QA-tools/OTS/UserDocumentation

2011-04-14T06:53:25Z

Esmietti: /* Usage */

== OTS User Documentation ==

This page contains user documentation for OTS.

=== Installation ===

'''Version 0.8.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Installation| 0.8.x Installation instructions Ubuntu]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm| 0.8.x Installation instructions RPM]]

'''Plug-ins'''

[[Quality/QA-tools/OTS/Plugins| 0.8.x Plug-ins installation instructions]]

'''Version 0.1.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| Migration from version 0.1.x to 0.8.x]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation/Old/Version_0.1| 0.1.x Installation instructions]]

'''Upgrading'''

* [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]

'''Troubleshooting'''

* [[Quality/QA-tools/OTS/Troubleshooting | Troubleshooting]]

=== Usage ===

* [[Quality/QA-tools/OTS/UserDocumentation/Usage|How to trigger a test run]]
** How to use conductor
** How to use ots_trigger
** Test plan based execution
** Running tests in chroot environment
** What are distribution models

==== Flashing ====

These HowTos show how to flash step by step [[Quality/QA-tools/OTS/Manual_flashing_of_n900 | manually]] and [[Quality/QA-tools/OTS/Automated_flashing_of_N900 | automatically]]

HowTo setup [[Quality/QA-tools/OTS/UserDocumentation/Multiple_device|Multiple device support]].

=== Related Documentation ===

* [[Quality/QA-tools/OTS/Glossary]]
* [[Quality/QA-tools/Testrunner-lite]]
* [[Quality/QA-tools/Autotest-guide]]

Quality/QA-tools/OTS/UserDocumentation/Upgrading

2011-04-13T05:47:25Z

Esmietti: /* 0.8.2 - 0.8.3 */

= Upgrading OTS =

== 0.8.2 - 0.8.3 ==
* Changes in ots_plugin_qareports.conf
** Add new parameters
* Only new features
** Test plan based execution
** Chroot support
** See [[Quality/QA-tools/OTS/UserDocumentation/Usage|how to]] use these features

== 0.8.1 - 0.8.2 ==
* New django package added, effects to all plug-ins
** See [[Quality/QA-tools/OTS/Plugins/Django|Django instructions]].
** See [[Quality/QA-tools/OTS/DeveloperDocs/Plugins|plug-ins instructions]].

== 0.8.0 - 0.8.1 ==
* Plug-in namespace changed, effects to Logger and QA-Reports plug-ins
** For logger update web page content, see step 8 from [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger documentation]].
** For QA-Reports, configuration file name has changed. Move /etc/ots_qareports_plugin.conf to /etc/ots_plugin_qareports.conf

== 0.1.x - 0.8.0 ==

See [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration document]].

Quality/QA-tools/OTS/Plugins/Django

2011-04-04T05:24:05Z

Esmietti: /* Enable/disable Django applications */

= Django environment setup =

== Introduction ==

Django is used for handling database communication and displaying WebUI.

== Basic installation ==

These instructions are made for Ubuntu, but should work in the same principals with other distributions. <br />
Installation is made to OTS server.

1. Install django
sudo apt-get install python-django
In Fedora:
sudo yum install Django
2. Download the latest django xml-rpc plugin
https://launchpad.net/django-xmlrpc
3. Install django plug-in
tar xzf django_xmlrpc-0.1.tar.gz
sudo mv django_xmlrpc /usr/local/lib/python2.6/dist-packages/
In Fedora (as root):
mv django_xmlrpc /usr/lib/python2.6/site-packages/
chcon -R -t httpd_user_content_t /usr/lib/python2.6/site-packages/django_xmlrpc
chcon -R -t httpd_user_content_t /opt/ots
setsebool -P httpd_unified 1
setsebool -P httpd_tmp_exec 1

== Enable/disable Django applications ==

In '''0.8.3''' release, this is not necessary anymore. Plug-ins are loaded automatically.

1. Edit Django settings
sudo nano /usr/local/lib/python2.6/dist-packages/ots/django/settings.py
In Fedora:
sudo nano /usr/lib/python2.6/site-packages/ots/django/settings.py
2. Comment/uncomment OTS components in 'INSTALLED_APPS' section
# OTS components:
'ots.plugin.logger',
'ots.plugin.monitor',
'ots.plugin.history'

== Create/update databases ==

1. Create database
sudo python /usr/local/lib/python2.6/dist-packages/ots/django/manage.py syncdb --settings=settings
In Fedora:
sudo python /usr/lib/python2.6/site-packages/ots/django/manage.py syncdb --settings=settings

2. Set permissions to database file
sudo chown www-data:www-data /opt/ots
sudo chown www-data:www-data /opt/ots/ots.sqlite
In Fedora:
sudo chown apache:apache /opt/ots
sudo chown apache:apache /opt/ots/ots.sqlite

== Apache configuration ==

1. Install Apache2 and Apache2 modules
sudo apt-get install libapache2-mod-wsgi apache2-mpm-prefork
Fedora:
yum install httpd mod_wsgi
rm /etc/httpd/conf.d/welcome.conf

2. Apache2 configuration

'''Ubuntu 10.04'''

sudo apt-get install libapache2-mod-python

<pre>
<VirtualHost *:80>

AliasMatch /([^/]*\.css) /var/www/styles/$1

Alias /media/ /var/www/media/

<Location "/">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE ots.plugin.logger.django_ots.settings
PythonDebug On
</Location>

<Location "/media">
SetHandler None
</Location>

<LocationMatch "/styles">
SetHandler None
</LocationMatch>
</VirtualHost>
</pre>

'''Ubuntu 10.10'''
sudo nano /etc/apache2/sites-enabled/000-default

<pre>
<VirtualHost *:80>

AliasMatch /([^/]*\.css) /var/www/styles/$1

Alias /media/ /var/www/media/

<Directory /usr/local/wsgi/static>
Order deny,allow
Allow from all
</Directory>

WSGIScriptAlias / /var/www/ots.wsgi

<Directory /usr/local/wsgi/scripts>
Order allow,deny
Allow from all
</Directory>

</VirtualHost>
</pre>

'''Fedora'''
rm /etc/httpd/conf.d/welcome.conf
sudo nano /etc/httpd/conf.d/ots.conf

<pre>
<VirtualHost *:80>

AliasMatch /([^/]*\.css) /var/www/styles/$1

Alias /media/ /var/www/media/

<Directory /usr/local/wsgi/static>
Order deny,allow
Allow from all
</Directory>

WSGIScriptAlias / /var/www/ots.wsgi

<Directory /usr/local/wsgi/scripts>
Order allow,deny
Allow from all
</Directory>

</VirtualHost>
</pre>

3. Copy www files to /var/www/
sudo cp -r /usr/share/ots/django/* /var/www/
sudo cp -r /usr/share/ots/plugin/* /var/www/
4. Add WSGI settings '''"WSGIRestrictSignal Off"'''
sudo nano /etc/apache2/apache2.conf
Fedora:
sudo nano /etc/httpd/conf/httpd.conf
5. Restart apache
sudo service apache2 restart
Fedora:
chkconfig --add httpd
chkconfig httpd on
/etc/init.d/httpd start

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-04T05:21:04Z

Esmietti: /* Using ots_trigger */

= OTS Usage =

== Test execution ==

=== Using conductor ===

Conductor is the executer in the ots-worker. You can use conductor to test device flashing and for semi-automatic test executions.

To test flashing and basic test execution:
conductor --imageurl=http://192.168.1.1/image.tar.gz

The conductor flasher the image to the device and executes all available test packages.

To list all supported options:
conductor --help

=== Using ots_trigger ===

'''Note:''' Before starting to execute tests with ots_trigger, verify that your ots-worker is configured correctly. That can be done with conductor, see the topic above.

ots_trigger is tool for triggering a testrun to OTS server.

[[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools| How to install ots_trigger]].

Before you can trigger a testrun, you need to have all following:
* OTS server up-and-running [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* OTS worker with hardware configured [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* Image with eat-device package (enabled test automation environment to hardware) [http://wiki.meego.com/Quality/QA-tools/Autotest-guide]

And one of the following options:
* Test package installed to the device
* Test package installed to the ots-worker or
* Test plan [TODO LINK]

Okey, now we are ready to get dirty.

If we have test package(s) installed into the device and we want to execute all of them:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com

Let me explain the parameters.
* '''server''': Defines the address of the OTS server. If you are not using logger plug-in, the address is then 192.168.1.1:8080.
* '''build_id''': Free string to define the image build id.
* '''image''': Url path where the image is located. Yes, it must be on the http server.
* '''sw_product''': The default SW test execution options, you have defined the sw_product in /etc/ots_server.conf.
* '''email''': Who has requested the testrun and to whom to send notifications.

That was simple. Next you want to execute only one package, no problem, just define test package name to ots_trigger:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --testpackages=my-test-package1-tests

In to the '''testpackages''' option, you can define multiple packages like this:
--testpackages=my-test-package1-tests,my-test-package2-tests

If you want to add more people to receive email after the execution is done, just add more email addresses to --email option:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com,second.name@company.com

If you have test package installed to your ots-worker machine, that can be executed with --hostpackages:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --hostpackages=my-test-package1-tests

For optimizing the execution time, see distribution models section below.

To list all supported options:
ots_trigger --help

== Test plan based executions ==

Test plan based execution means that the user can create a test plan and give it directly to ots_trigger without making any test package. This brings benefits when executing different test against the same test image or release.

The user can create the test plan with [http://wiki.meego.com/Quality/QA-tools/Testplanner Testplanner].

And then give the test plan to ots_trigger with --deviceplan or --hostplan. Difference between these options are that 'deviceplan' is executed in the device and 'hostplan' in the ots-worker.
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --deviceplan=/path/to/my/test_plan.xml

== Distribution models ==

These are models how the OTS is distributing test executions to ots-workers. There are 2 build-in models and other ones are distribution model plug-ins.

Distribution model can be specified to ots_trigger with --distribution option.

=== Default ===

This is the default model, if nothing else has been specified.

Default model executes all test packages in a single task, so only one ots-worker will handle the test execution. Only exception to this model is test plan based executions, they are always executed as an own task and therefor distributed to multiple workers.

=== Perpackage ===

'''---distribution=perpackage'''

Perpackage is the second build-in distribution model.

This models creates always an own task for each test package and test plan, so multiple ots-worker can handle the testrun at the same time.

=== Optimized ===

'''---distribution=optimized'''

Optimized is a distribution plug-in and it is part of history plug-in.

History plug-in collects test package execution times to a database. When the user triggers a testrun, he/she can specify how long the execution should take and how many device can be used. The optimized model then tries to optimize the execution time to fit the user's requirements.

See how to use the optimized plug-in from the [[Quality/QA-tools/OTS/Plugins/History|plug-in subpage]].

Quality/QA-tools/OTS

2011-04-01T09:39:18Z

Esmietti: /* Releases */

= OTS Index =

Welcome to the Open Test System (OTS) Wiki Index.

== Introduction ==

OTS is the '''Open Test Service''' for testing software systems on evolving hardware architectures.

It was born out of the test framework incrementally developed for use on [http://maemo.org/ Maemo] project and is in use for 24/7 testing service by [http://www.nokia.com/ Nokia].

More detailed info can be found from [[Quality/QA-tools/OTS/About|about]] page.

== Releases ==

Current release [http://meego.gitorious.org/meego-quality-assurance/ots tag 0.8.3]. See [[Quality/QA-tools/OTS/UserDocumentation/Upgrading|upgrading]] instructions!

Next release [https://bugs.meego.com/show_bug.cgi?id=13356 0.8.4]

See OTS [[Quality/QA-tools/OTS/Roadmap| roadmap.]]

== Documentation ==

* [[Quality/QA-tools/OTS/UserDocumentation | User Documentation]]
** [[Quality/QA-tools/OTS/UserDocumentation/Installation | Installation Ubuntu]]
** [[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm | Installation RPM]]
** [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]
* [[Quality/QA-tools/OTS/DeveloperDocs | Developer Documentation]]
* [[Quality/QA-tools/OTS/AdminDocs | System Administration]]
* [[Quality/QA-tools/OTS/Glossary | Glossary]]

Quality/QA-tools/OTS

2011-04-01T09:38:58Z

Esmietti: /* Releases */

= OTS Index =

Welcome to the Open Test System (OTS) Wiki Index.

== Introduction ==

OTS is the '''Open Test Service''' for testing software systems on evolving hardware architectures.

It was born out of the test framework incrementally developed for use on [http://maemo.org/ Maemo] project and is in use for 24/7 testing service by [http://www.nokia.com/ Nokia].

More detailed info can be found from [[Quality/QA-tools/OTS/About|about]] page.

== Releases ==

Current release [http://meego.gitorious.org/meego-quality-assurance/ots tag 0.8.3]. See [[Quality/QA-tools/OTS/UserDocumentation/Upgrading|upgrading]] instructions!

Next release [https://bugs.meego.com/show_bug.cgi?id=13355 0.8.4]

See OTS [[Quality/QA-tools/OTS/Roadmap| roadmap.]]

== Documentation ==

* [[Quality/QA-tools/OTS/UserDocumentation | User Documentation]]
** [[Quality/QA-tools/OTS/UserDocumentation/Installation | Installation Ubuntu]]
** [[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm | Installation RPM]]
** [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]
* [[Quality/QA-tools/OTS/DeveloperDocs | Developer Documentation]]
* [[Quality/QA-tools/OTS/AdminDocs | System Administration]]
* [[Quality/QA-tools/OTS/Glossary | Glossary]]

Quality/QA-tools/OTS/UserDocumentation/Installation

2011-04-01T09:22:07Z

Esmietti: /* How to install N900 automation tools to OTS worker */

= OTS 0.8.x installation Ubuntu =

If using 0.1.x version, see [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration from 0.1.x to 0.8.x]] document.

== Used hardware ==

:1 x Server (Ubuntu 10.10)
:1 x Client (Ubuntu 10.10)
::1 x HAT controller
:: 1 x Power cable
:: 1 x Power supply
:: 2 x USB A-B cable
:: 1 x USB A-microB cable
:: 1 x N900

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing apt source to /etc/apt/sources.list
sudo nano /etc/apt/sources.list
deb http://download.meego.com/live/Tools:/Testing/xUbuntu_10.10/ /
Notice that if you are using Ubuntu 10.04, change the path.

* Add repository keys
gpg --keyserver subkeys.pgp.net --recv-keys 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

* Update the repositories
sudo apt-get update

'''Build packages from source (optional)'''
* Install git core
sudo apt-get install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
sudo apt-get install dpkg-dev debhelper python-setuptools

* Build packages
cd ots
dpkg-buildpackage -rfakeroot

== OTS server installation ==

* Install dependencies
sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition

* Install OTS server components
sudo apt-get install python-ots-common python-ots-results python-ots-server
Or if you are using own built packages
sudo dpkg -i ...

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins
[[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger plug-in]] (recommended)
[[Quality/QA-tools/OTS/Plugins/Email|Email plug-in]] (recommended)

See more plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* If logger plug-in is installed
Change permissions to logging directory
sudo chown www-data:www-data /var/log/ots

Now the OTS server can be used via apache (django_xmlrpc).

* If logger plug-in is not installed
Change user permissions to logging directory
sudo chown <user>:<group> /var/log/ots

* Start rabbitmq-server
/etc/init.d/rabbitmq-server start

ots_server

== OTS worker installation ==

* Install dependencies
sudo apt-get install python-amqplib testrunner-lite

* Install OTS worker packages
sudo apt-get install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Change permissions to OTS worker log
sudo chown <user>:<group> /var/log/ots.log

* Start OTS worker
ots_worker

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
sudo apt-get install python-ots-tools

* Trigger a test run
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Remove network-manager, because it breaks the USB connection. See more information from autotest-guide.

* Install dependencies
sudo apt-get install meego-ai-flasher eat-host-ubuntu

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb
sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb

* Configure conductor to use rpm and fetch /var/log/messages
sudo nano /etc/conductor.conf

* If you want run ots_worker as user, copy SSH keys to the user and make udev rule for n900
install-eat-key.sh
sudo nano /etc/udev/rules.d/meego-n900.rules
SUBSYSTEMS=="usb", ATTR{idVendor}=="0421", ATTR{idProduct}=="0105", GROUP="<group>", MODE="0664"

* Create a power_cycle.sh script for turning N900 on/off. This requires external accessory, like [[Quality/QA-tools/hat-control|HAT]]
sudo nano /usr/bin/power_cycle.sh

#!/bin/bash

hat_drv &
hat_ctrl -pwr1=off
hat_ctrl -usb1data=off
hat_ctrl -usb1pwr=off
sleep 2;
hat_ctrl -usb1pwr=on
hat_ctrl -usb1data=on
hat_ctrl -pwr1=on
killall hat_drv

* Test manually that everything is OK, this is executed in the worker
conductor -u <image url>
* Start OTS worker (if you use HAT, run ots_worker as sudo)
sudo ots_worker

Quality/QA-tools/OTS/UserDocumentation/Upgrading

2011-04-01T09:09:08Z

Esmietti: /* 0.8.2 - 0.8.3 */

= Upgrading OTS =

== 0.8.2 - 0.8.3 ==
* No major changes to configuration
* Only new features
** Test plan based execution
** Chroot support
** See [[Quality/QA-tools/OTS/UserDocumentation/Usage|how to]] use these features

== 0.8.1 - 0.8.2 ==
* New django package added, effects to all plug-ins
** See [[Quality/QA-tools/OTS/Plugins/Django|Django instructions]].
** See [[Quality/QA-tools/OTS/DeveloperDocs/Plugins|plug-ins instructions]].

== 0.8.0 - 0.8.1 ==
* Plug-in namespace changed, effects to Logger and QA-Reports plug-ins
** For logger update web page content, see step 8 from [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger documentation]].
** For QA-Reports, configuration file name has changed. Move /etc/ots_qareports_plugin.conf to /etc/ots_plugin_qareports.conf

== 0.1.x - 0.8.0 ==

See [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration document]].

Quality/QA-tools/OTS/UserDocumentation/Upgrading

2011-04-01T09:08:41Z

Esmietti: /* Upgrading OTS */

= Upgrading OTS =

== 0.8.2 - 0.8.3 ==
* No major changes to configuration
* Only new features
** Test plan based execution
** Chroot support
** See [[OTS/UserDocumentation/Usage|how to]] use these features

== 0.8.1 - 0.8.2 ==
* New django package added, effects to all plug-ins
** See [[Quality/QA-tools/OTS/Plugins/Django|Django instructions]].
** See [[Quality/QA-tools/OTS/DeveloperDocs/Plugins|plug-ins instructions]].

== 0.8.0 - 0.8.1 ==
* Plug-in namespace changed, effects to Logger and QA-Reports plug-ins
** For logger update web page content, see step 8 from [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger documentation]].
** For QA-Reports, configuration file name has changed. Move /etc/ots_qareports_plugin.conf to /etc/ots_plugin_qareports.conf

== 0.1.x - 0.8.0 ==

See [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration document]].

Quality/QA-tools/OTS/UserDocumentation

2011-04-01T09:03:54Z

Esmietti: /* Usage */

== OTS User Documentation ==

This page contains user documentation for OTS.

=== Installation ===

'''Version 0.8.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Installation| 0.8.x Installation instructions Ubuntu]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm| 0.8.x Installation instructions RPM]]

'''Plug-ins'''

[[Quality/QA-tools/OTS/Plugins| 0.8.x Plug-ins installation instructions]]

'''Version 0.1.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| Migration from version 0.1.x to 0.8.x]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation/Old/Version_0.1| 0.1.x Installation instructions]]

'''Upgrading'''

* [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]

'''Troubleshooting'''

* [[Quality/QA-tools/OTS/Troubleshooting | Troubleshooting]]

=== Usage ===

* [[Quality/QA-tools/OTS/UserDocumentation/Usage|How to trigger a test run]]
** How to use conductor
** How to use ots_trigger
** Test plan based execution
** Running tests in chroot environment
** What are distribution models

==== Flashing ====

These HowTos show how to flash step by step [[Quality/QA-tools/OTS/Manual_flashing_of_n900 | manually]] and [[Quality/QA-tools/OTS/Automated_flashing_of_N900 | automatically]]

=== Related Documentation ===

* [[Quality/QA-tools/OTS/Glossary]]
* [[Quality/QA-tools/Testrunner-lite]]
* [[Quality/QA-tools/Autotest-guide]]

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-01T09:02:18Z

Esmietti: /* OTS Usage */

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-01T08:53:55Z

Esmietti: /* Distribution models */

= OTS Usage =

== Test execution ==

=== Using conductor ===

Conductor is the executer in the ots-worker. You can use conductor to test device flashing and for semi-automatic test executions.

To test flashing and basic test execution:
conductor --imageurl=http://192.168.1.1/image.tar.gz

The conductor flasher the image to the device and executes all available test packages.

To list all supported options:
conductor --help

=== Using ots_trigger ===

'''Note:''' Before starting to execute tests with ots_trigger, verify that your ots-worker is configured correctly. That can be done with conductor, see the topic above.

ots_trigger is tool for triggering a testrun to OTS server.

[[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools| How to install ots_trigger]].

Before you can trigger a testrun, you need to have all following:
* OTS server up-and-running [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* OTS worker with hardware configured [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* Image with eat-device package (enabled test automation environment to hardware) [http://wiki.meego.com/Quality/QA-tools/Autotest-guide]

And one of the following options:
* Test package installed to the device
* Test package installed to the ots-worker or
* Test plan [TODO LINK]

Okey, now we are ready to get dirty.

If we have test package(s) installed into the device and we want to execute all of them:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com

Let me explain the parameters.
* '''server''': Defines the address of the OTS server. If you are not using logger plug-in, the address is then 192.168.1.1:8080.
* '''build_id''': Free string to define the image build id.
* '''image''': Url path where the image is located. Yes, it must be on the http server.
* '''sw_product''': The default SW test execution options, you have defined the sw_product in /etc/ots_server.conf.
* '''email''': Who has requested the testrun and to whom to send notifications.

That was simple. Next you want to execute only one package, no problem, just define test package name to ots_trigger:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --testpackages=my-test-package1-tests

In to the '''testpackages''' option, you can define multiple packages like this:
--testpackages=my-test-package1-tests,my-test-package2-tests

If you want to add more people to receive email after the execution is done, just add more email addresses to --email option:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com,second.name@company.com

If you have test package installed to your ots-worker machine, that can be executed with --hostpackages:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --hostpackages=my-test-package1-tests

For optimizing the execution time, see distribution models section below.

To list all supported options:
ots_trigger --help

== Distribution models ==

These are models how the OTS is distributing test executions to ots-workers. There are 2 build-in models and other ones are distribution model plug-ins.

Distribution model can be specified to ots_trigger with --distribution option.

=== Default ===

This is the default model, if nothing else has been specified.

Default model executes all test packages in a single task, so only one ots-worker will handle the test execution. Only exception to this model is test plan based executions, they are always executed as an own task and therefor distributed to multiple workers.

=== Perpackage ===

'''---distribution=perpackage'''

Perpackage is the second build-in distribution model.

This models creates always an own task for each test package and test plan, so multiple ots-worker can handle the testrun at the same time.

=== Optimized ===

'''---distribution=optimized'''

Optimized is a distribution plug-in and it is part of history plug-in.

History plug-in collects test package execution times to a database. When the user triggers a testrun, he/she can specify how long the execution should take and how many device can be used. The optimized model then tries to optimize the execution time to fit the user's requirements.

See how to use the optimized plug-in from the [[Quality/QA-tools/OTS/Plugins/History|plug-in subpage]].

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-01T08:39:20Z

Esmietti: /* OTS Usage */

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-01T07:29:29Z

Esmietti: /* Test execution */

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-01T07:26:13Z

Esmietti: /* Using ots_trigger */

= OTS Usage =

== Test execution ==

=== Using conductor ===

Conductor is the executer in the ots-worker. You can use conductor to test device flashing and for semi-automatic test executions.

To list all supported options:
conductor --help

=== Using ots_trigger ===

'''Note:''' Before starting to execute tests with ots_trigger, verify that your ots-worker is configured correctly. That can be done with conductor, see the topic above.

ots_trigger is tool for triggering a testrun to OTS server.

[[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools| How to install ots_trigger]].

Before you can trigger a testrun, you need to have all following:
* OTS server up-and-running [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* OTS worker with hardware configured [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* Image with eat-device package (enabled test automation environment to hardware) [http://wiki.meego.com/Quality/QA-tools/Autotest-guide]

And one of the following options:
* Test package installed to the device
* Test package installed to the ots-worker or
* Test plan [TODO LINK]

Okey, now we are ready to get dirty.

If we have test package(s) installed into the device and we want to execute all of them:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com

Let me explain the parameters.
* '''server''': Defines the address of the OTS server. If you are not using logger plug-in, the address is then 192.168.1.1:8080.
* '''build_id''': Free string to define the image build id.
* '''image''': Url path where the image is located. Yes, it must be on the http server.
* '''sw_product''': The default SW test execution options, you have defined the sw_product in /etc/ots_server.conf.
* '''email''': Who has requested the testrun and to whom to send notifications.

That was simple. Next you want to execute only one package, no problem, just define test package name to ots_trigger:
ots_trigger --server=192.168.1.=== Using conductor ===

Conductor is the executer in the ots-worker. You can use conductor to test device flashing and for semi-automatic test executions.

To list all supported options:
conductor --help
1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --testpackages=my-test-package1-tests

In to the '''testpackages''' option, you can define multiple packages like this:
--testpackages=my-test-package1-tests,my-test-package2-tests

If you want to add more people to receive email after the execution is done, just add more email addresses to --email option:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com,second.name@company.com

To list all supported options_
ots_trigger --help

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-01T07:24:35Z

Esmietti: /* OTS Usage */

= OTS Usage =

== Test execution ==

=== Using conductor ===

Conductor is the executer in the ots-worker. You can use conductor to test device flashing and for semi-automatic test executions.

To list all supported options:
conductor --help

=== Using ots_trigger ===

'''Note''' Before starting to execute tests with ots_trigger, verify that your ots-worker is configured correctly. That can be done with conductor, see the topic above.

ots_trigger is tool for triggering a testrun to OTS server.

[[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools| How to install ots_trigger]].

Before you can trigger a testrun, you need to have all following:
* OTS server up-and-running [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* OTS worker with hardware configured [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* Image with eat-device package (enabled test automation environment to hardware) [http://wiki.meego.com/Quality/QA-tools/Autotest-guide]

And one of the following options:
* Test package installed to the device
* Test package installed to the ots-worker or
* Test plan [TODO LINK]

Okey, now we are ready to get dirty.

If we have test package(s) installed into the device and we want to execute all of them:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com

Let me explain the parameters.
* '''server''': Defines the address of the OTS server. If you are not using logger plug-in, the address is then 192.168.1.1:8080.
* '''build_id''': Free string to define the image build id.
* '''image''': Url path where the image is located. Yes, it must be on the http server.
* '''sw_product''': The default SW test execution options, you have defined the sw_product in /etc/ots_server.conf.
* '''email''': Who has requested the testrun and to whom to send notifications.

That was simple. Next you want to execute only one package, no problem, just define test package name to ots_trigger:
ots_trigger --server=192.168.1.=== Using conductor ===

Conductor is the executer in the ots-worker. You can use conductor to test device flashing and for semi-automatic test executions.

To list all supported options:
conductor --help
1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --testpackages=my-test-package1-tests

In to the '''testpackages''' option, you can define multiple packages like this:
--testpackages=my-test-package1-tests,my-test-package2-tests

If you want to add more people to receive email after the execution is done, just add more email addresses to --email option:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com,second.name@company.com

To list all supported options_
ots_trigger --help

Quality/QA-tools/OTS/UserDocumentation/Usage

2011-04-01T07:09:04Z

Esmietti: Created page with "= OTS Usage = == Test execution == === Using ots_trigger === ots_trigger is tool for triggering a testrun to OTS server. [[Quality/QA-tools/OTS/UserDocumentation/Installation…"

= OTS Usage =

== Test execution ==

=== Using ots_trigger ===

ots_trigger is tool for triggering a testrun to OTS server.

[[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools| How to install ots_trigger]].

Before you can trigger a testrun, you need to have all following:
* OTS server up-and-running [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* OTS worker with hardware configured [http://wiki.meego.com/Quality/QA-tools/OTS/UserDocumentation#Installation]
* Image with eat-device package (enabled test automation environment to hardware) [http://wiki.meego.com/Quality/QA-tools/Autotest-guide]

And one of the following options:
* Test package installed to the device
* Test package installed to the ots-worker or
* Test plan [TODO LINK]

Okey, now we are ready to get dirty.

If we have test package(s) installed into the device and we want to execute all of them:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com

Let me explain the parameters.
* '''server''': Defines the address of the OTS server. If you are not using logger plug-in, the address is then 192.168.1.1:8080.
* '''build_id''': Free string to define the image build id.
* '''image''': Url path where the image is located. Yes, it must be on the http server.
* '''sw_product''': The default SW test execution options, you have defined the sw_product in /etc/ots_server.conf.
* '''email''': Who has requested the testrun and to whom to send notifications.

That was simple. Next you want to execute only one package, no problem, just define test package name to ots_trigger:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --testpackages=my-test-package1-tests

In to the '''testpackages''' option, you can define multiple packages like this:
--testpackages=my-test-package1-tests,my-test-package2-tests

If you want to add more people to receive email after the execution is done, just add more email addresses to --email option:
ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com,second.name@company.com

To list all supported options, use
ots_trigger --help

Quality/QA-tools/OTS/UserDocumentation

2011-04-01T06:33:18Z

Esmietti: /* Usage */

== OTS User Documentation ==

This page contains user documentation for OTS.

=== Installation ===

'''Version 0.8.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Installation| 0.8.x Installation instructions Ubuntu]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm| 0.8.x Installation instructions RPM]]

'''Plug-ins'''

[[Quality/QA-tools/OTS/Plugins| 0.8.x Plug-ins installation instructions]]

'''Version 0.1.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| Migration from version 0.1.x to 0.8.x]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation/Old/Version_0.1| 0.1.x Installation instructions]]

'''Upgrading'''

* [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]

'''Troubleshooting'''

* [[Quality/QA-tools/OTS/Troubleshooting | Troubleshooting]]

=== Usage ===

* How to trigger a test run
** ots_trigger
** conductor
* Test plan based execution
* Running tests in chroot environment
* Distribution models
** Perpackage
** Default
** Optimized

==== Flashing ====

These HowTos show how to flash step by step [[Quality/QA-tools/OTS/Manual_flashing_of_n900 | manually]] and [[Quality/QA-tools/OTS/Automated_flashing_of_N900 | automatically]]

=== Related Documentation ===

* [[Quality/QA-tools/OTS/Glossary]]
* [[Quality/QA-tools/Testrunner-lite]]
* [[Quality/QA-tools/Autotest-guide]]

Quality/QA-tools/OTS/UserDocumentation

2011-04-01T06:31:38Z

Esmietti: /* OTS User Documentation */

== OTS User Documentation ==

This page contains user documentation for OTS.

=== Installation ===

'''Version 0.8.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Installation| 0.8.x Installation instructions Ubuntu]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm| 0.8.x Installation instructions RPM]]

'''Plug-ins'''

[[Quality/QA-tools/OTS/Plugins| 0.8.x Plug-ins installation instructions]]

'''Version 0.1.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| Migration from version 0.1.x to 0.8.x]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation/Old/Version_0.1| 0.1.x Installation instructions]]

'''Upgrading'''

* [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]

'''Troubleshooting'''

* [[Quality/QA-tools/OTS/Troubleshooting | Troubleshooting]]

=== Usage ===

* [[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools | How to trigger a testrun]]

''' Worker Components '''

* [[Quality/QA-tools/OTS/UserDocumentation/Conductor|Conductor]]

==== Flashing ====

These HowTos show how to flash step by step [[Quality/QA-tools/OTS/Manual_flashing_of_n900 | manually]] and [[Quality/QA-tools/OTS/Automated_flashing_of_N900 | automatically]]

=== Related Documentation ===

* [[Quality/QA-tools/OTS/Glossary]]
* [[Quality/QA-tools/Testrunner-lite]]
* [[Quality/QA-tools/Autotest-guide]]

Quality/QA-tools/OTS/UserDocumentation

2011-04-01T06:30:14Z

Esmietti: /* Installation */

== OTS User Documentation ==

This page contains user documentation for OTS.

=== Installation ===

'''Version 0.8.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Installation| 0.8.x Installation instructions Ubuntu]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm| 0.8.x Installation instructions RPM]]

'''Plug-ins'''

[[Quality/QA-tools/OTS/Plugins| 0.8.x Plug-ins installation instructions]]

'''Version 0.1.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| Migration from version 0.1.x to 0.8.x]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation/Old/Version_0.1| 0.1.x Installation instructions]]

=== Upgrading ===

* [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]

=== Troubleshooting ===

* [[Quality/QA-tools/OTS/Troubleshooting | Troubleshooting]]

=== Usage ===

* [[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools | How to trigger a testrun]]

''' Worker Components '''

* [[Quality/QA-tools/OTS/UserDocumentation/Conductor|Conductor]]

==== Flashing ====

These HowTos show how to flash step by step [[Quality/QA-tools/OTS/Manual_flashing_of_n900 | manually]] and [[Quality/QA-tools/OTS/Automated_flashing_of_N900 | automatically]]

=== Related Documentation ===

* [[Quality/QA-tools/OTS/Glossary]]
* [[Quality/QA-tools/Testrunner-lite]]
* [[Quality/QA-tools/Autotest-guide]]

Quality/QA-tools/OTS/UserDocumentation

2011-04-01T06:30:05Z

Esmietti:

== OTS User Documentation ==

This page contains user documentation for OTS.

=== Installation ===

'''Version 0.8.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Installation| 0.8.x Installation instructions Ubuntu]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation_rpm| 0.8.x Installation instructions RPM]]

'''Plug-ins''

[[Quality/QA-tools/OTS/Plugins| 0.8.x Plug-ins installation instructions]]

'''Version 0.1.x'''

[[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| Migration from version 0.1.x to 0.8.x]]

[[Quality/QA-tools/OTS/UserDocumentation/Installation/Old/Version_0.1| 0.1.x Installation instructions]]

=== Upgrading ===

* [[Quality/QA-tools/OTS/UserDocumentation/Upgrading | Upgrading]]

=== Troubleshooting ===

* [[Quality/QA-tools/OTS/Troubleshooting | Troubleshooting]]

=== Usage ===

* [[Quality/QA-tools/OTS/UserDocumentation/Installation#OTS_tools | How to trigger a testrun]]

''' Worker Components '''

* [[Quality/QA-tools/OTS/UserDocumentation/Conductor|Conductor]]

==== Flashing ====

These HowTos show how to flash step by step [[Quality/QA-tools/OTS/Manual_flashing_of_n900 | manually]] and [[Quality/QA-tools/OTS/Automated_flashing_of_N900 | automatically]]

=== Related Documentation ===

* [[Quality/QA-tools/OTS/Glossary]]
* [[Quality/QA-tools/Testrunner-lite]]
* [[Quality/QA-tools/Autotest-guide]]

Quality/QA-tools/OTS/UserDocumentation/Installation rpm

2011-03-30T09:11:47Z

Esmietti: /* Network Setup */

= OTS 0.8.x installation RPM =

These instructions have been tested with Fedora 13. Execute commands as root.

In MeeGo netbook, at least following packages needs to be installed manually:
python-amqp, python-django, minixsv, rabbitmq-server

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing source to /etc/yum.repos.d/
cd /etc/yum.repos.d/
yum install wget nano
wget http://download.meego.com/live/Tools:/Testing/Fedora13/Tools:Testing.repo

* Update the repositories
yum check-update

'''Build packages from source (optional)'''
* Install git core
yum install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
yum rpm-build python-setuptools

* Build packages
mv ots python-ots-0.8.x
tar czf python-ots-0.8.x.tar.gz python-ots-0.8.x
rpmbuild -tb python-ots-0.8.x.tar.gz

== OTS server installation ==

* Install dependencies
yum install Django python-amqplib python-configobj rabbitmq-server test-definition
easy_install minixsv
yum install python-setuptools

* Install OTS server components
yum install python-ots-common python-ots-results python-ots-server
or if you are using own built packages
rpm -i ...

* Add rabbitmq to start on boot
chkconfig --add rabbitmq-server
chkconfig rabbitmq-server on

* Start rabbitmq server
/etc/init.d/rabbitmq-server start

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins

See plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* Start OTS server
ots_server

== OTS worker installation ==

* Install dependencies
yum install python-amqplib testrunner-lite

* Install OTS worker packages
yum install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Change permissions to OTS worker log
sudo chown <user>:<group> /var/log/ots.log

* Start OTS worker
ots_worker

NOTE: if worker failed to start up with error like "socket.error: [Errno 113] No route to host", plz check if telnet service is available on ots server. telnet_server is not installed by default.

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
yum install python-ots-tools

* Trigger a test run
ots_trigger -s localhost:8080 -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Install dependencies
yum install meego-ai-flaster eat-host

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2.tar.gz
Compile the flasher

* Configure conductor to use rpm and fetch /var/log/messages
sudo nano /etc/conductor.conf

* If you want run ots_worker as user, copy SSH keys to the user and make udev rule for n900
install-eat-key.sh
sudo nano /etc/udev/rules.d/meego-n900.rules
SUBSYSTEMS=="usb", ATTR{idVendor}=="0421", ATTR{idProduct}=="0105", GROUP="<group>", MODE="0664"

* Create a power_cycle.sh script for turning N900 on/off. This requires external accessory, like [[Quality/QA-tools/hat-control|HAT]]
sudo nano /usr/bin/power_cycle.sh

#!/bin/bash

hat_drv &
hat_ctrl -pwr1=off
hat_ctrl -usb1data=off
hat_ctrl -usb1pwr=off
sleep 2;
hat_ctrl -usb1pwr=on
hat_ctrl -usb1data=on
hat_ctrl -pwr1=on
killall hat_drv

* Test manually that everything is OK, this is executed in the worker
conductor -u <image url>
* Start OTS worker
ots_worker

Quality/QA-tools/OTS/UserDocumentation/Installation

2011-03-30T09:11:17Z

Esmietti: /* Network Setup */

= OTS 0.8.x installation Ubuntu =

If using 0.1.x version, see [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration from 0.1.x to 0.8.x]] document.

== Used hardware ==

:1 x Server (Ubuntu 10.10)
:1 x Client (Ubuntu 10.10)
::1 x HAT controller
:: 1 x Power cable
:: 1 x Power supply
:: 2 x USB A-B cable
:: 1 x USB A-microB cable
:: 1 x N900

== Network Setup ==

Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.

'''Note''' All OTS machines need to be able to access other OTS machines based on their hostname.

How to check that DNS names are correct:

1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>

If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file
<IP> <hostname>

== Preparation ==

There are two ways of getting OTS binary packages: from '''the source code'''
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get
the stable version and from the source code the development version.

* Add Tools:Testing apt source to /etc/apt/sources.list
sudo nano /etc/apt/sources.list
deb http://download.meego.com/live/Tools:/Testing/xUbuntu_10.10/ /
Notice that if you are using Ubuntu 10.04, change the path.

* Add repository keys
gpg --keyserver subkeys.pgp.net --recv-keys 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

* Update the repositories
sudo apt-get update

'''Build packages from source (optional)'''
* Install git core
sudo apt-get install git-core

* Get sources
git clone git://gitorious.org/meego-quality-assurance/ots.git

* Get building tools
sudo apt-get install dpkg-dev debhelper python-setuptools

* Build packages
cd ots
dpkg-buildpackage -rfakeroot

== OTS server installation ==

* Install dependencies
sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition

* Install OTS server components
sudo apt-get install python-ots-common python-ots-results python-ots-server
Or if you are using own built packages
sudo dpkg -i ...

* Configure OTS server settings
sudo nano /etc/ots_server.ini

Recommended to change following:
'example_sw_product', example to 'meego_product'
'devicegroup', example to 'meego_n900'

* Install OTS server plug-ins
[[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger plug-in]] (recommended)
[[Quality/QA-tools/OTS/Plugins/Email|Email plug-in]] (recommended)

See more plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]]

* If logger plug-in is installed
Change permissions to logging directory
sudo chown www-data:www-data /var/log/ots

Now the OTS server can be used via apache (django_xmlrpc).

* If logger plug-in is not installed
Change user permissions to logging directory
sudo chown <user>:<group> /var/log/ots

* Start rabbitmq-server
/etc/init.d/rabbitmq-server start

ots_server

== OTS worker installation ==

* Install dependencies
sudo apt-get install python-amqplib testrunner-lite

* Install OTS worker packages
sudo apt-get install python-ots-common python-ots-worker

* Configure OTS worker settings
sudo nano /etc/ots.ini

Change 'devicegroup', example meego_n900

Change 'host' to server's address

* Change permissions to OTS worker log
sudo chown <user>:<group> /var/log/ots.log

* Start OTS worker
ots_worker

== OTS tools ==

Tools are used for triggering test runs from the command line.

* Install OTS tools
sudo apt-get install python-ots-tools

* Trigger a test run
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com

* Kickstart file for automation can be found from
http://meego.gitorious.org/meego-quality-assurance/enables-automated-testing/blobs/ks/meego-n900-autotest.ks

* You need to build the image with mic-image-creator with parameters:
--save-kernel --package=tar.gz

== How to install N900 automation tools to OTS worker ==

* Remove network-manager, because it breaks the USB connection. See more information from autotest-guide.

* Install dependencies
sudo apt-get install meego-ai-flasher eat-host-ubuntu

* Get N900 flasher from the Nokia's tablets-dev portal
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb
sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb

* Configure conductor to use rpm and fetch /var/log/messages
sudo nano /etc/conductor.conf

* If you want run ots_worker as user, copy SSH keys to the user and make udev rule for n900
install-eat-key.sh
sudo nano /etc/udev/rules.d/meego-n900.rules
SUBSYSTEMS=="usb", ATTR{idVendor}=="0421", ATTR{idProduct}=="0105", GROUP="<group>", MODE="0664"

* Create a power_cycle.sh script for turning N900 on/off. This requires external accessory, like [[Quality/QA-tools/hat-control|HAT]]
sudo nano /usr/bin/power_cycle.sh

#!/bin/bash

hat_drv &
hat_ctrl -pwr1=off
hat_ctrl -usb1data=off
hat_ctrl -usb1pwr=off
sleep 2;
hat_ctrl -usb1pwr=on
hat_ctrl -usb1data=on
hat_ctrl -pwr1=on
killall hat_drv

* Test manually that everything is OK, this is executed in the worker
conductor -u <image url>
* Start OTS worker
ots_worker

Quality/QA-tools/OTS/UserDocumentation/Upgrading

2011-03-22T06:19:22Z

Esmietti: /* 0.8.1 - 0.8.2 */

= Upgrading OTS =

== 0.8.1 - 0.8.2 ==
* New django package added, effects to all plug-ins
** See [[Quality/QA-tools/OTS/Plugins/Django|Django instructions]].
** See [[Quality/QA-tools/OTS/Plugins|plug-ins instructions]].

== 0.8.0 - 0.8.1 ==
* Plug-in namespace changed, effects to Logger and QA-Reports plug-ins
** For logger update web page content, see step 8 from [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger documentation]].
** For QA-Reports, configuration file name has changed. Move /etc/ots_qareports_plugin.conf to /etc/ots_plugin_qareports.conf

== 0.1.x - 0.8.0 ==

See [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration document]].

Quality/QA-tools/OTS/Plugins/HTTP logger

2011-03-22T06:18:05Z

Esmietti: /* Installation */

= HTTP logger plugin =

Released in OTS 0.8.2.

== Installation ==

Installation is made to OTS server.

1. Install [[Quality/QA-tools/OTS/Plugins/Django#Django_environment_setup|Django environment]]

2. Setup [[Quality/QA-tools/OTS/Plugins/Django#Apache_configuration|Apache2 environment]]

3. Install plug-in
sudo apt-get install python-ots-plugin-logger
Fedora:
sudo yum install python-ots-plugin-logger

4. Enable [[Quality/QA-tools/OTS/Plugins/Django#Enable.2Fdisable_Django_applications|Django application]]
'ots.plugin.logger'
5. [[Quality/QA-tools/OTS/Plugins/Django#Create.2Fupdate_databases|Create/update database]]

6. Restart Apache2
sudo service apache2 restart
Fedora:
sudo /etc/init.d/httpd restart

7. Browse http://localhost/logger/view/

Quality/QA-tools/OTS/Plugins/Monitor

2011-03-22T06:17:56Z

Esmietti:

= Monitor plugin =

Released in OTS 0.8.2.

== Installation ==

Installation is made to OTS server.

1. Install [[Quality/QA-tools/OTS/Plugins/Django#Django_environment_setup|Django environment]]

2. Setup [[Quality/QA-tools/OTS/Plugins/Django#Apache_configuration|Apache2 environment]]

3. Install plug-in
sudo apt-get install python-ots-plugin-monitor
Fedora:
sudo yum install python-ots-plugin-monitor

4. Enable [[Quality/QA-tools/OTS/Plugins/Django#Enable.2Fdisable_Django_applications|Django application]]
'ots.plugin.monitor'
5. [[Quality/QA-tools/OTS/Plugins/Django#Create.2Fupdate_databases|Create/update database]]

6. Restart Apache2
sudo service apache2 restart
Fedora:
sudo /etc/init.d/httpd restart

7. Browse http://localhost/monitor/view/