NewGuide
|
Size: 1978
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 2: | Line 2: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| = Testcase types = |
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 3em 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| == Testcase types == |
| Line 13: | Line 13: |
| = 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. |
== 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. |
| Line 16: | Line 16: |
| === Testcase Format === | === Testcase Markup === |
| Line 19: | Line 19: |
| <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 (optional).</p> | <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 28: | Line 29: |
=== 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)