Visual placeholder
Game DesignProgramming
Voxel Destruction Prototype
A small sandbox prototype exploring how destructible geometry changes player planning.
Personal prototype
View project
QASample record
Save-State Regression Pass
A QA case study: planning regression coverage for save, load, and migration paths after a systems refactor.
- Type
- QA case study (sample)
- Status
- Documented example
- Timeframe
- Draft timeframe
- Context
- Embedded tester on a small team (sample)
- My role
- QA Tester
Key visual placeholder
Artwork and screenshots are being prepared for this case study.
Overview
This case study documents how I planned regression coverage after a systems refactor, including how save-state surfaces were mapped, how checks were prioritised, and which triage rules applied when the test window was shorter than the coverage list.
Role & contribution
QA Tester
Built the regression checklist and the triage rules that decided what shipped.
- Mapped every surface that touches save data.
- Wrote the regression checklist and prioritised defects.
- Kept a traceable record of coverage and known risks.
Tools
TestRail (sample)Jira (sample)
Process
Grouped save-state surfaces by corruption risk, then wrote checks from the highest-risk path down.
Challenges & solutions
Coverage requirements grew faster than the available test window.
Prioritised by corruption severity and moved repetitive checks into a scripted pass.
Outcome
A reusable checklist that covers save, load, and migration paths for future builds.
Links
No public build, repository, or document is attached to this project yet. Links will appear here once they are safe to share.
Keep looking
Related projects
01
Next step
Want the full case study?
The complete process notes, references, and build access are available on request.