Testkit is one testing execution environment, which is composed by testkit-manager and testkit-lite. Testkit-manager represents a user interface front-end in browser, with the webUI interface, it manages the auto tests execution remotely, and provides unified webUI to help the manual tests execution. Testkit-lite is the default core test runner driving test execution in testkit-manager and it also provides more comprehensive options for your testing in command line mode.
1. Download testkit-lite and testkit-manager packages(rpm) from the download page.
2. Install the packages.
rpm -ivh testkit-lite-<version>.<architecture>.rpm rpm -ivh testkit-manager-<version>.<architecture>.rpm
Before that, you might need to install the following dependency packages:
perl-XML-Simple, perl-XML-SAX, perl-JSON, man, python-lxml
3. Startup the testkit-manager web server
4. Visit the testing page: http://test-machine-name:8890
Test Package Requirements:
Test package should follow the guideline: http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline
Click each test from the left frame, view the detail steps and then select PASS, FAIL or N/A, “SAVE RESULT” to save this test’s result.
After all manual tests are executed, click “FINISH TEST” to end up the manual tests execution. Note that the once the “FINISH TEST” is clicked, it means one round of test cycle is finished that no chance to modify the test results any more. The “RUN MANUAL TEST” button in “DETAIL TEST REPORT” will be removed.
Testkit-lite is the default core test runner in testkit-manager and it provides more comprehensive options for your testing in command line mode.
1. You can simply conduct one or more tests.xml:
testkit-lite -f <somewhere1>/tests.xml <somewhere2>/tests.xml
2. You can also arrange several tests.xml to one testsxmlconfig, and run:
testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig
Also, it supports multi testsxmlconfig:
testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig <somewhere2>/testsxmlconfig
The testsxmlconfig is like this:
/opt/browser/tests.xml /opt/ofono/tests.xml /opt/gfx/tests.xml /opt/pulseaudio/tests.xml
3. If you want to validate one new tests.xml:
testkit-lite -f tests.xml -V
4. If you just want to get the statistic (such as the testcases number or the structure), dryrun could help:
testkit-lite -f tests.xml -D
5. If you want to execute auto tests:
testkit-lite -f tests.xml
6. If you just want to execute manual tests:
testkit-lite -f tests.xml -M
7. If you want to execute all the auto and manual tests:
testkit-lite -f tests.xml -A
8. If you just want to execute the significant tests:
testkit-lite -f tests.xml -S
9. If you want to choose some filters:
testkit-lite -f tests1.xml tests2.xml --level level1 level2 --type type1 type2 --Ntestcase gfx1 gfx2...
Note that the test cases will be filtered out by both black rules and white rules.
10. At last, you can freely compose the above paramters together:
testkit-lite -f tests1.xml tests2.xml --testxmlconfig config1 config2 -D -A -S -C --level level1 level2 --type type1 type2 ...
11. One more parameter is prepared for customized compatible mode for test report:
testkit-lite -f tests.xml -C
testkit-lite enables only automatic tests by default. Obviously -A and -M are conflict options.
1. testkit-lite's TestLog is stored to /opt/testkit/lite/latest after execution, you can also check the history results in /opt/testkit/lite/yyyy-mm-dd-HH:MM:SS.NNNNNN.
2. Two kinds of test report will be generated:
1)<tests xml name>.textresult
2)<tests xml name>.xmlresult
xml result files aligned with schema files: /opt/testkit-lite/xsd/testdefinition-results.xsd
Detail Options <TBD>