(→MCTS) |
(→How to run MCTS) |
||
| Line 1: | Line 1: | ||
= How to run MCTS = | = How to run MCTS = | ||
== Generic == | == Generic == | ||
| - | A quick collection for anybody running | + | A quick collection for anybody running MCTS. Please read generic section first before got to specific component. |
| - | There are 3 test suite | + | There are 3 test suite categories for MCTS. Test suite name in each category starts with mcts-, mwts- and blts- seperately. These 3 test categories have some differences to run. To avoid confusion, we call test suites that starts with mcts- as mcts- test suites, we call other two categories as mwts and blts test suites respectively. |
This section use mcts-connman-test, mwts-network and blt-wlan-core as example. | This section use mcts-connman-test, mwts-network and blt-wlan-core as example. | ||
| - | === Install | + | === Install MCTS from RPM === |
# export http_proxy=<proxy> if you are in Intranet | # export http_proxy=<proxy> if you are in Intranet | ||
zypper addrepo http://download.meego.com/live/devel:/quality:/tests/Trunk/ mcts | zypper addrepo http://download.meego.com/live/devel:/quality:/tests/Trunk/ mcts | ||
| - | zypper in mwts-network-generic-all # In general, you can install | + | zypper in mwts-network-generic-all # In general, you can install MWTS by install mwts-<component>-generic-all |
zypper in mcts-connman-tests | zypper in mcts-connman-tests | ||
zypper in blts-wlan-core-tests | zypper in blts-wlan-core-tests | ||
| - | # Or you might prefer to install all | + | # Or you might prefer to install all MCTS by |
zypper in mcts* mwts* blts* | zypper in mcts* mwts* blts* | ||
| - | === | + | === Install MCTS from Source === |
# export http_proxy=<proxy> if you are in Intranet | # export http_proxy=<proxy> if you are in Intranet | ||
git clone http://git.gitorious.org/meego-quality-assurance/mcts.git | git clone http://git.gitorious.org/meego-quality-assurance/mcts.git | ||
cd mcts/mcts-connman-tests | cd mcts/mcts-connman-tests | ||
./pack.sh | ./pack.sh | ||
| - | # Using ./pack.sh -r for | + | # Using ./pack.sh -r for MWTS and BLTS |
# You need make sure that you have already installed necessary build required packages | # You need make sure that you have already installed necessary build required packages | ||
rpm -ivh mcts-connman-tests.<version>.rpm | rpm -ivh mcts-connman-tests.<version>.rpm | ||
| Line 33: | Line 33: | ||
# MWTS and BLTS also generate additional test log at /var/log/tests | # MWTS and BLTS also generate additional test log at /var/log/tests | ||
# It's best to run on a xterm of test machine. Some test suites need X environment. | # It's best to run on a xterm of test machine. Some test suites need X environment. | ||
| - | # By default, | + | # By default, MCTS test suite needs to be run with root user |
testrunner-lite -a -f /usr/share/mcts-connman-tests/tests.xml -o results.xml | testrunner-lite -a -f /usr/share/mcts-connman-tests/tests.xml -o results.xml | ||
| Line 44: | Line 44: | ||
There is a README for each test suite. Please follow the README for execution | There is a README for each test suite. Please follow the README for execution | ||
| - | * MCTS is at /opt/mcts-<component>-tests/ | + | * MCTS- test suite README is at /opt/mcts-<component>-tests/ |
| - | * MWTS (README and MWTS.README) is at /usr/share/doc/mwts-<component>/ | + | * MWTS test suite README (README and MWTS.README) is at /usr/share/doc/mwts-<component>/ |
| - | * BLTS is at /usr/share/doc/blts-<component>-tests/ | + | * BLTS test suite README is at /usr/share/doc/blts-<component>-tests/ |
| - | == MCTS == | + | == MCTS- category == |
[[/mcts-bluez-tests |mcts-bluez-tests ]] | [[/mcts-bluez-tests |mcts-bluez-tests ]] | ||
| Line 75: | Line 75: | ||
[[/mcts-tracker-tests |mcts-tracker-tests]] | [[/mcts-tracker-tests |mcts-tracker-tests]] | ||
| - | == MWTS == | + | == MWTS category == |
mwts-accounts | mwts-accounts | ||
| Line 111: | Line 111: | ||
| - | == BLTS == | + | == BLTS category == |
blts-alsa-core | blts-alsa-core | ||
Contents |
A quick collection for anybody running MCTS. Please read generic section first before got to specific component.
There are 3 test suite categories for MCTS. Test suite name in each category starts with mcts-, mwts- and blts- seperately. These 3 test categories have some differences to run. To avoid confusion, we call test suites that starts with mcts- as mcts- test suites, we call other two categories as mwts and blts test suites respectively.
This section use mcts-connman-test, mwts-network and blt-wlan-core as example.
# export http_proxy=<proxy> if you are in Intranet zypper addrepo http://download.meego.com/live/devel:/quality:/tests/Trunk/ mcts zypper in mwts-network-generic-all # In general, you can install MWTS by install mwts-<component>-generic-all zypper in mcts-connman-tests zypper in blts-wlan-core-tests # Or you might prefer to install all MCTS by zypper in mcts* mwts* blts*
# export http_proxy=<proxy> if you are in Intranet git clone http://git.gitorious.org/meego-quality-assurance/mcts.git cd mcts/mcts-connman-tests ./pack.sh # Using ./pack.sh -r for MWTS and BLTS # You need make sure that you have already installed necessary build required packages rpm -ivh mcts-connman-tests.<version>.rpm # You need make sure that you have already installed required packages
zypper in testrunner-lite
# Run test suite by testrunner-lite. You need to define where the test result is. # MWTS and BLTS also generate additional test log at /var/log/tests # It's best to run on a xterm of test machine. Some test suites need X environment. # By default, MCTS test suite needs to be run with root user testrunner-lite -a -f /usr/share/mcts-connman-tests/tests.xml -o results.xml
There is a README for each test suite. Please follow the README for execution
mcts-display-tests
mcts-geoclue-tests
mcts-gupnp-tests
mcts-openvg-tests
mcts-packagekit-tests
mcts-pulseaudio-tests
mcts-qtgfx-tests
mcts-system-tests
mwts-accounts
mwts-bluetooth
mwts-buteo
mwts-feedback
mwts-filesystem
mwts-gcamera
mwts-gstreamer
mwts-location
mwts-messaging
mwts-multimedia
mwts-network
mwts-ofono
mwts-pim
mwts-sensors
mwts-systeminfo
mwts-telepathy
mwts-usb
blts-alsa-core
blts-bluetooth
blts-fbdev
blts-input-devices
blts-ofono
blts-opengles2-perf
blts-sensors-frontend
blts-usb
blts-v4l2
blts-watchdog
blts-wlan-core
blts-x11
blts-xvideo