Test Case Development
and Execution
A structured overview of how test cases move from specification through execution to reported outcome. Each stage carries distinct responsibilities, inputs, and artifacts — none are optional.
phases tracked
classification levels
design methods
From Requirement to Result
Each test case follows a defined path: requirements are parsed into conditions, conditions become steps, steps are executed against a build, outcomes are recorded, and discrepancies are escalated. The sequence is not flexible — skipping phases introduces gaps that invalidate the final report.
Phases are sequential. Re-entry at any stage resets downstream artifacts.
Execution Coverage at a Glance
How Test Cases Are Categorised
Test cases divide across three primary axes — design technique, execution scope, and defect severity. Each axis informs how the case is written, when it runs, and how its failure is prioritised.
Classification must be assigned during design, not after execution. Retroactive labelling produces inaccurate reports and misleads triage. Molvaneskt has applied this taxonomy since 2019 across both manual and automated suites.
- Equivalence partitioning — reduces input set to representative classes
- Boundary value analysis — targets edges of valid and invalid ranges
- Decision table — maps condition combinations to system responses
- State transition — verifies behaviour across defined system states
- Smoke — minimum viable check before full suite execution
- Regression — unchanged functionality verified after new changes
- Exploratory — unscripted discovery within defined charter scope
- Acceptance — business condition verification before release
- P1 Critical — system unusable, no workaround exists
- P2 High — core function impaired, workaround is costly
- P3 Medium — partial function degraded, workaround available
- P4 Low — cosmetic or minor, no functional impact