NewGuide
|
Size: 2045
Comment:
|
← Revision 20 as of 2013-06-25 21:12:48 ⇥
Size: 2351
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Testcase Formats = Two formats are currently recognized for use. For most testcases, the testcase should be in this form |
<<Include(QATeam/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 3em 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| == Testcase types == Two types of testcases are currently recognized for use; normal and smoke. |
| Line 4: | Line 6: |
| == Normal Testcase == 1. Perform X action 1. Expect Y result 1. Perform A action 1. Expect B and C result If all actions produce the expected results listed, please submit a 'passed' result. 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. |
=== 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. |
| Line 12: | Line 10: |
| == Smoke Testcase == * Question 1? * Question 2? * Question 3? If you answer 'yes' to all questions, please submit a 'passed' result. If you answer 'no' to any question, then please submit a 'failed' result and file a bug. Please be sure to include the bug number when you submit your result. |
=== 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. |
| Line 19: | Line 13: |
| == Syntax for Admins == === Normal Testcase === |
== 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 tracker. The following shows the markup required for all testcases. The current testcases in the repository will show the same markup applied. === Testcase Markup === |
| Line 22: | Line 18: |
| <ol> <li title="action">Perform X action</li> <ol> <li title="expected_result">Expect Y result</li> </ol> <li title="action">Perform A action</li> <ol> <li title="expected_result">Expect B AND C result</li> </ol> </ol> <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>. |
<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> |
| Line 36: | Line 29: |
| === Smoke Testcase === {{{ <ol> <li title="action">Question 1?</li> <li title="action">Question 2?</li> <li title="action">Question 3?</li> </ol> <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> }}} |
=== Additional Formatting === In addition to the testcase markup shown above, you might want to use more formatting for your testcase. Below is the recommend list of HTML tags and their preferred use: || '''Tag''' || '''Usage''' || '''Example''' || || <code> || When you want to denote a command the user should run or output from a command. || <code>ls</code> || |
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 tracker. The following shows the markup required for all testcases. The current testcases in the repository will show the same markup applied.
Testcase Markup
<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>
Additional Formatting
In addition to the testcase markup shown above, you might want to use more formatting for your testcase. Below is the recommend list of HTML tags and their preferred use:
Tag |
Usage |
Example |
<code> |
When you want to denote a command the user should run or output from a command. |
<code>ls</code> |
Testing/TestCaseFormat/NewGuide (last edited 2013-06-25 21:12:48 by nblzone-227-162)