// case study
Building: public demo, live soon
QA Agent Platform
A public, scoped-down demo of an AI agent platform for QA I built at my company. Chat with a QA-tuned persona grounded in RAG, and get back more than text: the agent helps execute testing and generates test analysis as an interactive mindmap.
01 / Problem
At my company, QA engineers were losing time to two things a chatbot alone doesn’t fix: answering the same requirements and coverage questions over and over, and turning test analysis into something a team will actually read instead of a wall of text. This case study is a public rebuild of that idea, scoped down and without the proprietary integrations (Notion publishing, Figma reads, internal MCP tools) that only make sense inside the company’s own stack.
02 / Approach
The agent runs on a QA-tuned system prompt (a "QA soul"), grounded in RAG over a set of internal docs (requirements, test plans) embedded and stored in PostgreSQL. A LangGraph state machine routes each incoming message through a lightweight intent step, deciding whether the user wants a Q&A answer, a test-analysis breakdown, or a test run. For test analysis, the LLM's output is constrained to a Pydantic schema (structured nodes: title, coverage notes, risk level, children) before it ever reaches the UI, so a malformed response fails validation and gets regenerated instead of breaking the mindmap. Conversations and validated analyses are persisted in PostgreSQL, and the validated outline is rendered as an interactive mindmap with Markmap. Test-run requests trigger a tool call that executes the relevant test and folds the result back into the same conversation, so failures can be discussed in-thread instead of a separate log.