You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a "Risk" level, maybe based on the linked Requirement.
If you can link a Requirement to a Test Case, then you can:
define the "test coverage" for your Requirements, then calculate a SLA
define the risk/criticity of a Requirement : thus Nestor can generate the order of the Test Cases in a test Campaign(planning), based on the Risk level (known as Risk Based Testing)
define in which Sprint a Requirement will be coded. Thus, Nestor can generate the Test Cases to use for a release/sprint (so Nestor will be Agile/Scrum compliant).
We can also use requirements prioritization or level of risks to use in Test Cases. In this case Requirement analyst define the priorization or level of risk in the requirements and all TC elaborated from these requirements receive the levels of priorization.
We need to have some way to add priorities or classifications... or maybe some other meta data to test cases.
The text was updated successfully, but these errors were encountered: