PRAVEEN/YADAV
All projects
02 / Developer tools · Delivery

QA Flow

A feature, its tests, its bugs and the conversation about them, all in one place.

Built solo
Full stack
Visit website
What it is

A QA and delivery workspace where features, acceptance criteria, test runs, defects and team chat all link to each other.

My role

Built solo

Category

Developer tools · Delivery

Main stack

React 19 · Vite 7 · React Router 7 · Tailwind CSS 3

Highlight

A feature can’t reach release with a blocker hanging off it

Status

Live product

The QA Flow sign-in screen with email and password fields and a note that accounts are created by an administrator.
The sign-in screen. Accounts are created by an admin inside each organisation, so there is no open sign-up.qaflow.projectdock.in · Sep 2026
WHY IT EXISTS

A feature, its tests, its bugs and the conversation about them, all in one place.

Every small team I have been on used a bug tracker, a test-case sheet, a delivery board and a chat app, and the context leaked between them. A failed test didn’t become a defect. A defect didn’t point back to the requirement it broke. The discussion about it happened somewhere else entirely. QA Flow is my answer to that: one workspace where all of those things link to each other.

What I did

I built this one alone, start to finish, between December 2025 and September 2026. Interface, backend, chat and calling, the testing workflow, deployment. About nine months of work.

93API endpoints
25pages
11delivery stages, role-gated
9months, one developer
PROJECT OVERVIEW

How it fits together.

The product, in five steps.

01Plan the feature
02Agree what done means
03Run the tests
04Track the defects
05Ship it
WHAT I FOCUSED ON
01

A feature can’t reach release with a blocker hanging off it

Features move through eleven stages and each transition is gated by role. A tester can mark something QA Passed; a developer can’t. If a feature isn’t ready, the system says exactly why: which tasks are open, which criteria have no tests. A manager can override a gate, but the override is recorded.

02

Every defect knows where it came from

A defect links back to the feature, the acceptance criteria it violates, the test case and the exact run that found it. Test runs are kept as history rather than overwritten, so you can see that something passed on run three and failed on run four.

03

Chat and calls, next to the work

I built the chat and the audio and video calling myself on WebRTC and Socket.IO, without a third-party calling service. That was harder than I expected. It also means a call about a defect happens next to the defect, not in a separate app.

TRY IT

From a requirement to a release you can trust

Sample project data. A simplified walk along one chain of links.

LINK 1 OF 4

Feature FEAT-08

The team agrees what a good reporting experience looks like.

BUILT WITH
React 19Vite 7React Router 7Tailwind CSS 3Socket.IOWebRTCNode.jsExpress 4MongoDBMongoose 9JWTAWS S3
WHERE IT STANDS

Live at qaflow.projectdock.in. Built and looked after by me alone.

Numbers on this page are as of September 2026.
INTERESTED?

Want to see it running?

Happy to walk you through the live product, show how it is put together, and talk about whether something similar would fit what you are building.

Request a demoOpens your email client · ypraveen760@gmail.com