← all projects
apps-toolsactive

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.

the journey

  1. 01 · where it started

    Testlane began as a frontend-only prototype backed by localStorage. That made the workflow visible quickly, but it was still a browser-local demonstration rather than an API-backed application.

  2. 02 · the challenge

    As cases, runs, plans, requirements and defects came together, the project needed durable relational data and traceability between each part of the QA workflow. Several screens also had to be kept honest about whether they were live, local-only or still roadmap work.

  3. 03 · what changed

    The application was rebuilt module by module around Next.js API routes, MySQL and Drizzle. The core case, run and plan flows moved onto the database, requirements and defects began reading live project data, and project-scoped RBAC plus an audited admin panel were added.

  4. 04 · where it stands

    The main QA workflow is real and API-backed, while the remaining limits stay explicit: demo authentication is local-only, one run-route header bypass must be removed before production, some reports are labelled Roadmap, milestones still use localStorage and AI Studio remains a concept preview.

proof points

skills demonstrated

QA workflow modellingFull-stack deliveryData modellingNext.jsDrizzle ORM

tech stack

next.jsdrizzle ormmysqldocker

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.

hygiene data updated 4 Aug 2026last pushed 17 Jul 2026

Guided CLI Simulator

Explore a read-only guided simulation of Testlane's command-line interface or pipeline.

where to see it

Public repository. Read it directly: github.com/noel-q/testlane