NewGuide
|
Size: 3846
Comment:
|
Size: 1970
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was copied from Testing/TestCaseFormat | |
| Line 4: | Line 3: |
| = Testcase Formats = Two formats are currently recognized for use. For most testcases you find on the qatracker, the testcase should look like one of these: |
= Testcase types = Two types of testcases are currently recognized for use; normal and smoke. |
| Line 7: | Line 6: |
| == Normal Testcase == === Description === |
=== Normal Testcase === |
| Line 12: | Line 10: |
| === Format === ||<tablestyle="margin-left: -20px !important; line-height: 1em !important;" style="width: 20px;">|| || ||<-2> '''1. Perform X action''' || || || ''Expect Y result'' || ||<-2> '''2. Perform A action''' || || || ''Expect B result'' || || || ''Expect C result'' || '''If all actions produce the expected results listed, please submit a 'passed' result.<<BR>> If an action fails, or produces an unexpected result, please submit a 'failed' result and file a bug. Please be sure to include the bug number when you submit your result.''' == Smoke Testcase == === Description === |
=== Smoke Testcase === |
| Line 27: | Line 13: |
| === Format === ||<tablestyle="margin-left: -20px !important; line-height: 1em !important;">'''1. Question 1?'''|| ||'''2. Question 2?'''|| ||'''3. Question 3?'''|| |
= Contributing Testcases = If you are [[https://launchpad.net/ubuntu-manual-tests|contributing a new manual testcase]], the text must include formatting to ensure it shows up visually correct on the qatracker. The following shows the markup required for all testcases. The current testcases in the repository will show the same markup applied. |
| Line 32: | Line 16: |
| '''If you answer 'yes' to all questions, please submit a 'passed' result.<<BR>> If you answer 'no' to any question, then please submit 'failed' and file a bug. Please be sure to include the bug number when you submit your result.''' <<Anchor(contribute)>> = Contributing Testcases = If you are [[https://launchpad.net/ubuntu-manual-tests|contributing a new manual testcase]], the text must include formatting to ensure it shows up visually correct on the qatracker. The following shows the same examples as above, but this time including the formatting required. The current testcases in the repository will show the same markup applied. === Normal Testcase === |
=== Testcase Format === |
| Line 41: | Line 18: |
| <h2>Testcase name <span>test-case-number-001</span></h2> <p>A brief description what the desired outcome and area of focus for the testcase is, if it isn't obvious after reading the testcase instructions.</p> |
|
| Line 42: | Line 22: |
| Line 49: | Line 28: |
<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result. If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong> |
|
| Line 53: | Line 29: |
=== Smoke Testcase === {{{ <dl> <dt>Question 1?</dt> <dt>Question 2?</dt> <dt>Question 3?</dt> </dl> <strong>If you answer 'yes' to all questions, please <a href="results#add_result">submit</a> a 'passed' result. If you answer 'no' to any question, then please <a href="results#add_result">submit</a> 'failed' and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong> }}} |
Testcase types
Two types of testcases are currently recognized for use; normal and smoke.
Normal Testcase
This testcase is intended to provide step by step instructions, followed by an expected result for each step. To perform the testcase, read the perform action, and then verify the expected result step. If there is no expected result for the action, simply continue on performing the next action until the test is complete.
Smoke Testcase
This testcase is intended to ask generalized questions for you to answer before rendering a pass or fail result. The questions are used as an aide to help you test the image, package, hardware, etc that is intended. By design, these testcases are open-ended and require the user to think critically about if the item being tested has regressed or otherwise contains any bugs. To do this, the user must go through there own personal use-cases, and checking the results against there own expectations. This requires more user knowledge of the item being tested.
Contributing Testcases
If you are contributing a new manual testcase, the text must include formatting to ensure it shows up visually correct on the qatracker. The following shows the markup required for all testcases. The current testcases in the repository will show the same markup applied.
Testcase Format
<h2>Testcase name <span>test-case-number-001</span></h2>
<p>A brief description what the desired outcome and area of focus for the
testcase is, if it isn't obvious after reading the testcase instructions.</p>
<dl>
<dt>Perform X action</dt>
<dd>Expect Y result</dd>
<dt>Perform A action</dt>
<dd>Expect B result</dd>
<dd>Expect C result</dd>
</dl>Testing/TestCaseFormat/NewGuide (last edited 2013-06-25 21:12:48 by nblzone-227-162)