Testlane
QA test management workspace for cases, runs, plans, requirements and defects
what it proves
Proves full-stack product delivery around a detailed QA workflow: modelling traceability from requirements through cases and runs to defects, then wiring it to a real API and relational database.
A full-stack QA workspace that keeps test cases, test runs, test plans, requirements and defects in one traceable workflow rather than scattering them across a spreadsheet and a separate bug tracker. The core case, run and plan workflow uses a MySQL and Drizzle backend. It remains a portfolio project with local demo authentication and clearly documented production-security limitations.
proof points
- Test cases, plans, runs, requirements and defects are linked in one traceable workflow
- Next.js API routes and a MySQL database through Drizzle back the core case, run and plan workflow
- Public repository with documented local setup using Docker Compose
skills demonstrated
tech stack
engineering hygiene
- ✓ readme
- ✓ docs
- ✗ tests
- ✗ ci
- ✓ docker
Known gaps: tests, ci. Next step: harden demo authentication and remove the temporary run-route header bypass before any production deployment.
the code
Public repository. Read it directly: github.com/qhedroid/testlane