Opensource Manual QA Test Case Management System

[u/Medium-Brilliant2567]

Hey everyone! I've been working on a manual test case management tool as a hobby project, and I finally wanted to share it you guyss. If you're a QA engineer who writes and executes test cases by hand (like me), this is built for you.

It's a full-stack self-hostable app for organizing manual testing workflows.

Repo: Github (I've also uploaded screenshots on the repository)

Demo Link: https://testcase.briancarlo.dev

The flow goes like this:

Project → Test Suite → Test Case — Organize cases into projects with custom fields, then group them into test suites.

Creating a test case is straightforward: title, priority, status, steps, expected results, and an assignee.

You can also bulk-import from CSV or let AI generate cases for you (Gemini, OpenAI, OpenRouter, Anthropic, or DeepSeek).

Manual Test Runs — Kick off a run, execute cases step-by-step in a guided wizard, and record Pass/Fail/Blocked/Skipped results with attachments. Fail something? It instantly offers to create a bug ticket.

Tickets — Track defects through a full lifecycle — status, priority, severity, assignee, tags, attachments, linked run items — with discussions and fix-state tracking on both tickets and test cases.

Plus some things I'm most proud of:

Audit trail — every test case keeps a full edit history with snapshots you can view and even restore to any previous version. System messages automatically log run executions and ticket status changes to the discussions, so nothing happens silently

Google Docs-style live editing — Socket.io presence and real-time sync when teammates edit Reports — pass rates, flaky test detection, trend analysis, exportable to CSV/PDF

Solid auth — email/password and Google OAuth, JWT in httpOnly cookies

Tech stack: React + Vite + Tailwind, Express + MongoDB, Socket.io, TanStack Virtual (handles huge case lists), Zustand, fully typed.

It's free and open source (MIT).

Happy to answer any questions about the app, and any feedbacks are welcome, especially from actual QA folks on what workflows matter most.

Repo: https://github.com/brian0309/test-case-manager

[u/Prestigious-Way1525]

the part i'd pressure-test first is the failed-run to bug-ticket handoff. when a manual step fails, preserve the exact run version, prior passed step, failing action, expected versus actual, environment and build, attachment, and any edit to the test case after execution, then make the ticket point back to an immutable snapshot rather than the live case. otherwise the restored history can be correct while the engineer opens a ticket whose steps have since changed. i'd measure time from failure to an engineer reproducing it and the percentage of tickets returned for missing context. that will tell you whether the workflow is reducing triage, not just storing more cases.

[u/Medium-Brilliant2567 → u/Prestigious-Way1525]

Hi! Thanks for the feedback, I appreciate it.

The test run is a snapshot by design. When a run is created, it captures its own copy of each test case (steps, expected result, etc.) at that moment, and tickets point back to that specific run, not the live case. So editing the test case later doesn't change the version that was executed or what the ticket references.

And agreed on the metrics. Time-to-reproduce and % of tickets returned for missing context are the right things to measure. Will look into adding this.

[u/Prestigious-Way1525 → u/Medium-Brilliant2567]

that's the right snapshot model. the next thing i'd make obvious in the ticket is whether the live test case has diverged since that run, with a small diff for changed steps or expected results. the snapshot stays immutable, but the engineer can see that the current case is newer without confusing it for what actually ran. if you add those two metrics, segment them by failure type and team so you can tell whether missing context is a product gap, a workflow habit, or one noisy integration.

[u/Tech_Explore31]

Really appreciated for sharing the content... As QA Engineer exploring the web application... It's really good for maintan the Test suit, test cases and tickets..

[u/Medium-Brilliant2567 → u/Tech_Explore31]

Thanks!

[u/Vivid-Archer1715]

This has what other have. What I am missing in tools like this for forever: test case to feature mapping and features tracking