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