Difference between revisions of "Product Work Tests"
(→Script) |
|||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[File:Cnm-digital.png|400px|thumb|right|[[ | + | [[File:Cnm-digital.png|400px|thumb|right|[[CNMCyber suite]]s]][[Product Work Tests]] (hereinafter, the ''Lectio'') is the [[lectio|lesson part]] of '''[[Manual Testing Essentials]]''' [[lesson]] that introduces its participants to [[manual testing]] concepts. This ''lesson'' belongs to the ''CNMCT Entrance'' section of [[CNMCyber Bootcamps]]. |
| Line 6: | Line 6: | ||
===Script=== | ===Script=== | ||
| − | : | + | :[[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 development iterations or phases, | + | :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 test]]s evaluate functionality of [[work product]]s, while [[non-functional test]]s evaluate 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, ''functional tests'' can be further 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 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''. | :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''. | ||
| + | |||
| + | :Any usage of a [[work product]] by any user must be considered as occasional testing as long as this user reports the issues or corrects the bugs. | ||
===Key terms=== | ===Key terms=== | ||
| − | : | + | :[[Product work testing]], [[functional testing]], [[non-functional testing]], [[functional test]], [[non-functional test]], [[product work test]], [[progression test]], [[regression test]], [[progression testing]], [[regression testing]] |
===Closing=== | ===Closing=== | ||
| − | : | + | :Which of the statements below is correct: |
| + | <ol type="a"><li>[[Testing]] always considers product [[requirements]].</li><li>[[Regression testing]] is a type of [[functional testing]].</li><li>[[Progression testing]] ensures that newly developed functionalities work as per the product [[requirements]].</li><li>[[User stories]] used for the last development can be perfectly used for progression testing</li><li>All of the other substantive answers are correct.</li> | ||
The successor [[lectio]] is '''[[Verification vs Validation]]'''. | The successor [[lectio]] is '''[[Verification vs Validation]]'''. | ||
Latest revision as of 02:54, 21 October 2023
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 CNMCyber Bootcamps.
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 tests evaluate functionality of work products, while non-functional tests evaluate 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, functional tests can be further 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.
- Any usage of a work product by any user must be considered as occasional testing as long as this user reports the issues or corrects the bugs.
Key terms
- Product work testing, functional testing, non-functional testing, functional test, non-functional test, product work test, progression test, regression test, progression testing, regression testing
Closing
- Which of the statements below is correct:
- Testing always considers product requirements.
- Regression testing is a type of functional testing.
- Progression testing ensures that newly developed functionalities work as per the product requirements.
- User stories used for the last development can be perfectly used for progression testing
- All of the other substantive answers are correct.
The successor lectio is Verification vs Validation.
