< Talk:Quality(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| - | == Test execution management procedure – really light version ==
| + | Lets improve document together. Give comments and improvement ideas through this or edit the page directly. |
| - | | + | --[[User:Jaritah|tahvo]] 12:36, 16 February 2011 (UTC) |
| - | Preparation:
| + | |
| - | * install build
| + | |
| - | * meet in “qa.meego.com” or “test.meego.com” or “wiki.meego.com/Quality” or … <place to be agreed>
| + | |
| - | How to work on it (intent):
| + | |
| - | * Scan through the test plan and choose a test case or test suite to test and set the result as “running” (download tests)
| + | |
| - | * After finishing the test, set the result either to "passed" or to "failed" (upload results)
| + | |
| - | * If the test do not pass, please also create a bug report in bugs.meego.com
| + | |
| - | * If you are unable to finish the test, please set the result from "running" to "blocked". (upload results)
| + | |
| - |
| + | |
| - | I suppose we need someone (member of QA core team, or test collection maintainer) to facilitate (create test plan, import build information, generate sorted test cases list) the execution.
| + | |
| - | | + | |
| - | Another thing is that who creates content for empty test cases = test ideas (describe test scenario). Test ideas and test cases shall be generated by test collection maintainers. Maintainers should also support test coordinator by identifying integration test cases which can be used for regression purposes.
| + | |
| - | | + | |
| - | --[[User:Jaritah|JariT]] 11:16, 9 June 2010 (UTC) | + | |
Latest revision as of 12:37, 16 February 2011
Lets improve document together. Give comments and improvement ideas through this or edit the page directly.
--tahvo 12:36, 16 February 2011 (UTC)