(→Execute) |
(→MCTS) |
||
| Line 49: | Line 49: | ||
== MCTS == | == MCTS == | ||
| - | mcts-bluez-tests | + | [[/mcts-bluez-tests |mcts-bluez-tests ]] |
| - | mcts-connman-tests | + | [[/mcts-connman-tests |mcts-connman-tests]] |
mcts-display-tests | mcts-display-tests | ||
| Line 59: | Line 59: | ||
mcts-gupnp-tests | mcts-gupnp-tests | ||
| - | mcts-lsw-tests | + | [[/mcts-lsw-tests |mcts-lsw-tests]] |
| - | mcts-ofono-tests | + | [[/mcts-ofono-tests |mcts-ofono-tests]] |
mcts-openvg-tests | mcts-openvg-tests | ||
| Line 70: | Line 70: | ||
mcts-qtgfx-tests | mcts-qtgfx-tests | ||
| - | |||
| - | |||
mcts-system-tests | mcts-system-tests | ||
mcts-tracker-tests | mcts-tracker-tests | ||
| - | + | 1. start-up tracker "tracker-control -s" remotely. | |
| - | mcts- | + | 2. testrunner-lite -f /usr/share/mcts-tracker-tests/tests.xml -o results.xml |
== MWTS == | == MWTS == | ||
Contents |
A quick collection for anybody running mcts. Please read generic section first before got to specific component.
There are 3 test suite sets for MCTS. Test suite name in each set starts with mcts-, mwts- and blts- seperately. These 3 test sets have some differences to run.
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 bye 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
mcts-tracker-tests
1. start-up tracker "tracker-control -s" remotely. 2. testrunner-lite -f /usr/share/mcts-tracker-tests/tests.xml -o results.xml
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