Difference between revisions of "Product Work Tests"
(→Script) |
(→Script) |
||
| Line 8: | Line 8: | ||
:[[Product work testing]] evaluates functionality of [[work product]]s, performance of those teams that developed them, and/or other results of the development. | :[[Product work testing]] evaluates functionality of [[work product]]s, performance of those teams that developed them, and/or other results of the development. | ||
| − | :With regard to the type of [[requirement]]s that must have been met, ''product work testing'' can be divided in two categories: [[functional testing]] and [[non-functional testing]]. ''Functional testing'' evaluates functionality of [[work product]]s, while ''non-functional testing'' evaluates the performance of the development teams and readiness of the ''work product'' to be transferred, installed, launched, and | + | :With regard to the type of [[requirement]]s that must have been met, ''product work testing'' can be divided in two categories: [[functional testing]] and [[non-functional testing]]. ''Functional testing'' evaluates functionality of [[work product]]s, while ''non-functional testing'' evaluates the performance of the development teams and readiness of the ''work product'' to be transferred, installed, launched, and possibly, maintained. |
:With regard to the development iterations or phases, all [[product work test]]s 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. | :With regard to the development iterations or phases, all [[product work test]]s 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. | ||
Revision as of 16:09, 10 November 2020
Product Work Tests (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
- Product work testing evaluates functionality of work products, performance of those teams that developed them, and/or other results of the development.
- With regard to the type of requirements that must have been met, product work testing can be divided in two categories: functional testing and non-functional testing. Functional testing evaluates functionality of work products, while non-functional testing evaluates the performance of the development teams and readiness of the work product to be transferred, installed, launched, and possibly, maintained.
- With regard to the development iterations or phases, all product work tests 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 Verification vs Validation.
