Full Pass Specification: Difference between revisions
From Yocto Project
Jump to navigationJump to search
(Created page with '===Full Pass Specification=== ==== M2 Test Execution Plan ==== Since there are still some unclear requirements for Yocto project, currently it’s hard to define test plan to co…') |
No edit summary |
||
| Line 1: | Line 1: | ||
==== M2 Test Execution Plan ==== | ==== M2 Test Execution Plan ==== | ||
Since there are still some unclear requirements for Yocto project, currently it’s hard to define test plan to cover all future milestone/weekly testing. According to the suggestion from KangKang, I defined a test execution plan for M2 testing, which only covers tests for M2 requirement. | Since there are still some unclear requirements for Yocto project, currently it’s hard to define test plan to cover all future milestone/weekly testing. According to the suggestion from KangKang, I defined a test execution plan for M2 testing, which only covers tests for M2 requirement. | ||
Latest revision as of 22:37, 22 October 2010
M2 Test Execution Plan
Since there are still some unclear requirements for Yocto project, currently it’s hard to define test plan to cover all future milestone/weekly testing. According to the suggestion from KangKang, I defined a test execution plan for M2 testing, which only covers tests for M2 requirement.
The fullpass test plan is here, M2 fullpass test plan. For each target, like qemux86, qemuarm, netbook, e-Menlow, etc, I define separate test plan for them, with sub-tests chosen from the fullpass test plan.
I setup a testlink page to track test case and test plan status, http://otc-qa.sh.intel.com/testlink_yocto/. You can use username/passwd: guest/guest, to browser test case and test plan.
