Test Case Priority

 

Level 0	P1	SQA Build Acceptance Test or BVT	- BVT (Determines the usefulness of this build to test). - Area Base valid Functionality tested at breath - Automated (No manual)	Release to SQA – Determines if build is accepted/rejected for SQA testing	Check accessibility of particular feature (i.e. when the user selects a link to a report, does the link work)
Level 1	P2	Validity Test - Product works for core scenarios	- Area valid cases tested at depth - Base Integrated System Tests - Release Candidate Breadth Pass - 100% automated is the goal - E2E scenario	Release to SQA and CTP	Validate the scenario foobar that includes use case coverage across one or more features
Level 2	P3	Invalid/Error/Boundary Test	- Extended Integrated System Tests - Boundary Conditions - Invalid/Error Condition (Negative testing vs ‘happy path’) - Fail and recover scenarios (denial of service – security breech..) - Expected performance and stress that as related to the release criteria.	Release to SQA, CTP, and SIT	For a given argument N, where N is the upper bound, validate that N+1 is handled gracefully. Measure performance given concurrent user usage for a given web service.
Level 3	P4	Extreme – Robustness Test	- Depth/Robustness Stabilization - Complex repro – Unlikely extreme scenarios - Ad / Hoc – Gorilla testing (use (abuse) the application in non-standard scenario - Extreme deployment and load scenarios - Extreme Stress/Extreme Scalability Fault Tolerance	Release to UAT/Production	Potential tests can include scenarios that have multiple conditional “edge-case” inputs