Systematic testing: Difference between revisions
Jump to navigation
Jump to search
See Friends in testing for detailed instructions on how to prepare for exploratory or systematic testing.
mNo edit summary |
|||
| (26 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{developers}} |
<noinclude>{{developers}} |
||
{{ |
{{testers}} |
||
<center>See [[Friends in testing]] for detailed instructions on how to prepare for [[exploratory testing|exploratory]] or systematic testing.</center> |
|||
</noinclude> |
|||
== Systematic Testing == |
|||
In addition to our freeform [[exploratory testing]] effort, we also engage in [[systematic testing]] efforts designed to achieve the test coverage necessary to make release decisions around [[future releases]], much like [[release notes|past releases]]. |
|||
Systematic testing consists of several basic tasks: |
|||
* |
* Reviewing a '''[[Test_cases_8.2.1|test plan]]'''. |
||
* |
* Writing '''[[Test cases 8.2.1#Create New Test Cases|the test cases]]''', if needed. |
||
* |
* Executing the '''[[Test_cases_8.2.1#Test_cases|test cases]]''' and recording test results. |
||
** ''To record results on a particular test case page,'' click on the '''"Edit with form"''' button in the top of the page, and use the '''"Add Another" button''' just above the '''"Add New Results" section''' (i.e. at the bottom of the page). |
|||
* contributing patches to the [[Tinderbox]] so that it can execute test cases! |
|||
* Contributing patches to the '''[[Tinderbox]]''' or '''[[Sugarbot]]''' automated testing platforms. |
|||
=== Test 1: Multiple Key Support === |
|||
[[Category:Testing]] |
|||
We are particularly interested, this week, in systematically testing [[Firmware|OFW]]'s new [[Firmware_security#Multiple-Key_Support|multiple key support]]. |
|||
Latest revision as of 15:58, 10 December 2010
For Developers
For Testers
Systematic Testing
In addition to our freeform exploratory testing effort, we also engage in systematic testing efforts designed to achieve the test coverage necessary to make release decisions around future releases, much like past releases.
Systematic testing consists of several basic tasks:
- Reviewing a test plan.
- Writing the test cases, if needed.
- Executing the test cases and recording test results.
- To record results on a particular test case page, click on the "Edit with form" button in the top of the page, and use the "Add Another" button just above the "Add New Results" section (i.e. at the bottom of the page).
- Contributing patches to the Tinderbox or Sugarbot automated testing platforms.
Test 1: Multiple Key Support
We are particularly interested, this week, in systematically testing OFW's new multiple key support.