Difference between revisions of "What Test Case Is"
(→Script) |
(→Script) |
||
| Line 6: | Line 6: | ||
===Script=== | ===Script=== | ||
| − | :The English word, [[case]], originally derived from a Latin [[noun]] ''casus'' that meant an ''accident, event, occurrence; occasion, opportunity''. | + | :The English word, [[case]], originally derived from a Latin [[noun]] ''casus'' that meant an ''accident, event, occurrence; occasion, opportunity''. A [[test case]] is a description of particular [[testing]]. |
| − | + | :In [[systems engineering]], a ''test case'' specifies the inputs, external factors, available assets, procedures, and expected outputs. Having that specification, the [[tester]] who administers the [[test]] can evaluate whether the tested system achieves the objectives it has been designed to achieve. | |
| − | |||
| − | In | ||
| + | :Not all ''cases'' must be specific. For instance, a ''test case'' for this very [[lectio]] can be: <code>Read the lectio and make sure that its closing question reflects the lectio's body.</code> | ||
:Those [[User story|user stori]]es that have been used for the development can be perfectly used for ''progression testing''. Regularly, any [[acceptance test]] involves these ''stories''. | :Those [[User story|user stori]]es that have been used for the development can be perfectly used for ''progression testing''. Regularly, any [[acceptance test]] involves these ''stories''. | ||
Revision as of 20:42, 8 November 2020
What Test Case Is (hereinafter, the Lectio) is the lesson part of Manual Testing Essentials lesson that introduces its participants to manual testing concepts. This lesson belongs to the CNMCT Entrance section of the CNM Cyber Placement.
Content
The predecessor lectio is What Manual Test Is.
Script
- The English word, case, originally derived from a Latin noun casus that meant an accident, event, occurrence; occasion, opportunity. A test case is a description of particular testing.
- In systems engineering, a test case specifies the inputs, external factors, available assets, procedures, and expected outputs. Having that specification, the tester who administers the test can evaluate whether the tested system achieves the objectives it has been designed to achieve.
- Not all cases must be specific. For instance, a test case for this very lectio can be:
Read the lectio and make sure that its closing question reflects the lectio's body.
- Those user stories that have been used for the development can be perfectly used for progression testing. Regularly, any acceptance test involves these stories.
Key terms
Closing
The successor lectio is What UX Test Is.
