|
| 1 | + Quick Start: |
| 2 | + ================= |
| 3 | + |
| 4 | + At first, prepare one tests.xml file aligned with schema files: /opt/testkit/lite/xsd/testdefinition-syntax.xsd. |
| 5 | + |
| 6 | + And then, |
| 7 | + |
| 8 | + 1) You can simply conduct one or more tests.xml: |
| 9 | + testkit-lite -f <somewhere1>/tests.xml <somewhere2>/tests.xml |
| 10 | + |
| 11 | + 2) You can also arrange several tests.xml to one testsxmlconfig, and run |
| 12 | + testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig |
| 13 | + Also, it supports multi testsxmlconfig: |
| 14 | + testkit-lite --testxmlconfig <somewhere1>/testsxmlconfig <somewhere2>/testsxmlconfig |
| 15 | + The testsxmlconfig is like this: |
| 16 | + ############################## |
| 17 | + # /opt/browser/tests.xml # |
| 18 | + # /opt/ofono/tests.xml # |
| 19 | + # /opt/gfx/tests.xml # |
| 20 | + # /opt/pulseaudio/tests.xml # |
| 21 | + ############################## |
| 22 | + |
| 23 | + 3) If you want to validate one new tests.xml: |
| 24 | + testkit-lite -f tests.xml -V |
| 25 | + |
| 26 | + 4) If you just want to get the statistic (such as the testcases number or the structure), dryrun could help: |
| 27 | + testkit-lite -f tests.xml -D |
| 28 | + |
| 29 | + 5) If you want to execute auto tests: |
| 30 | + testkit-lite -f tests.xml |
| 31 | + |
| 32 | + 6) If you just want to execute manual tests: |
| 33 | + testkit-lite -f tests.xml -M |
| 34 | + |
| 35 | + 7) If you want to execute all the auto and manual tests: |
| 36 | + testkit-lite -f tests.xml -A |
| 37 | + |
| 38 | + 8) If you just want to execute the significant tests: |
| 39 | + testkit-lite -f tests.xml -S |
| 40 | + |
| 41 | + 9) If you want to choose some filters: |
| 42 | + testkit-lite -f tests1.xml tests2.xml --level level1 level2 --type type1 type2 --Ntestcase gfx1 gfx2... |
| 43 | + Note that the test cases will be filtered out by both black rules and white rules. |
| 44 | + |
| 45 | + 10) At last, you can freely compose the above paramters together: |
| 46 | + testkit-lite -f tests1.xml tests2.xml --testxmlconfig config1 config2 -D -A -S -C --level level1 level2 --type type1 type2 ... |
| 47 | + |
| 48 | + 11) One more parameter is prepared for customized compatible mode for test report: |
| 49 | + testkit-lite -f tests.xml -C |
| 50 | + |
| 51 | + |
| 52 | + Get Results: |
| 53 | + ================= |
| 54 | + Two kinds of test report will be generated: |
| 55 | + 1) <tests xml name>.textresult |
| 56 | + example: |
| 57 | + ===================================TestReport=================================== |
| 58 | + TYPE PASS FAIL N/A |
| 59 | + ---/usr/share/mnts1.0-distromisc-test/tests.xml XML 0 0 24 |
| 60 | + `---Distro Misc SUITE 0 0 24 |
| 61 | + |---General shortkeys SET 0 0 2 |
| 62 | + | |---general_shortkeys_console_switch CASE 0 0 1 |
| 63 | + | `---general_shortkeys_standard_shortkeys CASE 0 0 1 |
| 64 | + |---Linux Usability SET 0 0 4 |
| 65 | + | |---linux_usability_common_commands CASE 0 0 1 |
| 66 | + | |---linux_usability_default_app_and_MIME CASE 0 0 1 |
| 67 | + | |---linux_usability_gconf_database CASE 0 0 1 |
| 68 | + | `---linux_usability_security_usability CASE 0 0 1 |
| 69 | + |---Log system SET 0 0 4 |
| 70 | + | |---log_system_UI_process CASE 0 0 1 |
| 71 | + | |---log_system_monitor_log_access CASE 0 0 1 |
| 72 | + | |---log_system_process_pulseaudio_daemon CASE 0 0 1 |
| 73 | + | `---log_system_sreadhead CASE 0 0 1 |
| 74 | + |---Non-defult integrated applications SET 0 0 3 |
| 75 | + | |---non_default_apps_installation CASE 0 0 1 |
| 76 | + | |---non_default_apps_sanity_check CASE 0 0 1 |
| 77 | + | `---non_default_apps_uninstallation CASE 0 0 1 |
| 78 | + |---Package check SET 0 0 3 |
| 79 | + | |---package_check_core_debuginfo CASE 0 0 1 |
| 80 | + | |---package_check_core_dependency CASE 0 0 1 |
| 81 | + | `---package_check_core_version CASE 0 0 1 |
| 82 | + |---Peripheral Devices SET 0 0 6 |
| 83 | + | |---peripheral_devices_automount CASE 0 0 1 |
| 84 | + | |---peripheral_devices_external_bluetooth CASE 0 0 1 |
| 85 | + | |---peripheral_devices_external_cdrom CASE 0 0 1 |
| 86 | + | |---peripheral_devices_usb_hotplug CASE 0 0 1 |
| 87 | + | |---peripheral_devices_usb_hub CASE 0 0 1 |
| 88 | + | `---peripheral_devices_usb_mount_umount CASE 0 0 1 |
| 89 | + `---User actions on the stage of system boot-up SET 0 0 2 |
| 90 | + |---user_actions_at_bootup_keyboard_operations CASE 0 0 1 |
| 91 | + `---user_actions_at_bootup_mouse_operations CASE 0 0 1 |
| 92 | + |
| 93 | + 2) <tests xml name>.xmlresult |
| 94 | + xml result files aligned with schema files: /opt/testkit/lite/xsd/testdefinition-results.xsd |
| 95 | + example: <ignore> |
| 96 | + |
| 97 | + The result will be under /opt/testkit/lite/latest after execution, you can also check the history results in /opt/testkit/lite/yyyy-mm-dd-HH:MM:SS.NNNNNN. |
| 98 | + |
| 99 | + |
| 100 | + Notes: |
| 101 | + ================= |
| 102 | + testkit-lite's TestLog is stored to /opt/testkit/lite/latest |
| 103 | + testkit-lite enables only automatic tests by default |
| 104 | + Obviously -A and -M are conflict options. |
| 105 | + |
| 106 | + |
| 107 | + Detail Options: |
| 108 | + ================= |
| 109 | + Options: |
| 110 | + -f, --testxmls Specify the test.xml, support multi test.xml |
| 111 | + Refer to --testxmlconfig to add by filelist |
| 112 | + --testxmlconfig Specify the file listing group of testxmls |
| 113 | + Support multi testxmlconfig files |
| 114 | + -D, --dryrun Dry-run the selected test cases |
| 115 | + -V, --validate-only Do only input xml validation, do not execute tests |
| 116 | + -M, --manual-only Enable only manual tests to be executed |
| 117 | + -A, --all Enable both automatic and manual tests |
| 118 | + -S, --significant-only |
| 119 | + Enable only significant tests to be executed |
| 120 | + -C, --compatibleresultxml |
| 121 | + use nokia compatible result xml format |
| 122 | + --domain Select the specified white-rules filter: domain |
| 123 | + --requirement Select the specified white-rules filter: requirement |
| 124 | + --testsuite Select the specified white-rules filter: testsuite |
| 125 | + --testset Select the specified white-rules filter: testset |
| 126 | + --environment Select the specified white-rules filter: environment |
| 127 | + --level Select the specified white-rules filter: level |
| 128 | + --feature Select the specified white-rules filter: feature |
| 129 | + --testcase Select the specified white-rules filter: testcase |
| 130 | + --subfeature Select the specified white-rules filter: subfeature |
| 131 | + --type Select the specified white-rules filter: type |
| 132 | + --Ndomain Select the specified black-rules filter: domain |
| 133 | + --Nrequirement Select the specified black-rules filter: requirement |
| 134 | + --Ntestsuite Select the specified black-rules filter: testsuite |
| 135 | + --Ntestset Select the specified black-rules filter: testset |
| 136 | + --Nenvironment Select the specified black-rules filter: environment |
| 137 | + --Nlevel Select the specified black-rules filter: level |
| 138 | + --Nfeature Select the specified black-rules filter: feature |
| 139 | + --Ntestcase Select the specified black-rules filter: testcase |
| 140 | + --Nsubfeature Select the specified black-rules filter: subfeature |
| 141 | + --Ntype Select the specified black-rules filter: type |
| 142 | + -h, --help show this help message and exit |
0 commit comments