Difference between revisions of "What Test Case Is"
(→Script) |
(→Script) |
||
| Line 12: | Line 12: | ||
:Not all ''cases'' must be highly detailed . For instance, a ''test case'' for this very [[lectio]] can be:<blockquote><code>Evaluate whether the closing question of the lectio called ''What Test Case Is'' reflects the brief lecture that this lectio includes.</code></blockquote> | :Not all ''cases'' must be highly detailed . For instance, a ''test case'' for this very [[lectio]] can be:<blockquote><code>Evaluate whether the closing question of the lectio called ''What Test Case Is'' reflects the brief lecture that this lectio includes.</code></blockquote> | ||
| − | :All ''test cases'' can be divided in two categories: [[ | + | :All ''test cases'' can be divided in two categories: [[progression test]]s and [[regression test]]s. [[Progression testing]] is undertaken to ensure that newly-developed features are developed properly. [[Regression testing]] is undertaken to ensure that newly-developed features do not interfere the proper functioning of the system prior to the recent changes. |
| − | :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 last development can be perfectly used for ''progression testing''. Regularly, any [[acceptance test]] involves these ''stories''. Vice versa, those ''user stories'' that that were used for all the developments prior to the last one can be perfectly used for ''regression testing''. |
===Key terms=== | ===Key terms=== | ||
Revision as of 20:56, 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 highly detailed . For instance, a test case for this very lectio can be:
Evaluate whether the closing question of the lectio called What Test Case Is reflects the brief lecture that this lectio includes.
- All test cases can be divided in two categories: progression tests and regression tests. Progression testing is undertaken to ensure that newly-developed features are developed properly. Regression testing is undertaken to ensure that newly-developed features do not interfere the proper functioning of the system prior to the recent changes.
- Those user stories that have been used for the last development can be perfectly used for progression testing. Regularly, any acceptance test involves these stories. Vice versa, those user stories that that were used for all the developments prior to the last one can be perfectly used for regression testing.
Key terms
Closing
The successor lectio is What UX Test Is.
