Quality architecture
Framework shape, service contracts, test ownership, release gates, and reporting models that survive more than one team or one sprint.
Quality + AI + Architecture
Hello, I’m Kumar.
I design quality systems for teams shipping web apps, APIs, distributed services, and AI-assisted engineering workflows.
My work sits between architecture and release decisions: test platforms, contract checks, CI evidence, failure triage, and the small tools that stop stale signals from becoming production noise.
About
I care about the part after the test finishes.
A test result by itself is not a decision. It needs context: what changed, which boundary is affected, whether the mock still matches the contract, whether the failure is new, and who can act on it.
That is the work I keep returning to. I build automation and quality platforms that make evidence readable for engineers, release owners, and the systems that sit in between.
Work
Three lanes, one goal: better release signal.
AI-assisted test intelligence
RAG, MCP, agents, CI logs, failure history, and repository context used carefully enough that engineers can inspect the reasoning.
Cloud execution and reliability
Distributed test execution across containers, CI workers, and cloud infrastructure where timing, isolation, and observability matter.
Featured project
MockDoctor checks whether your mocks are telling the truth.
MockDoctor compares ReadyAPI REST virtual-service files with an OpenAPI spec or JSON contract. It reports drift before stale mocks leak into test suites or CI pipelines.
mockdoctor
npx mockdoctor compare \
--readyapi ./readyapi-project.xml \
--openapi ./openapi.yaml- Finds missing operations
- Compares method and path pairs so a mock cannot quietly drift away from the contract.
- Checks response shape
- Flags status-code gaps, content-type mismatches, invalid JSON, and schema differences.
- Fits CI
- Runs as a CLI or GitHub Action and can leave an HTML drift report as a build artifact.
Toolbox
Systems I’m comfortable reasoning about.
- Python
- Java
- Playwright patterns
- Selenium Grid
- ReadyAPI
- REST contracts
- GitLab CI
- Jenkins
- AWS
- Kubernetes
- Nomad
- RAG
- MCP
- Agent workflows
Notes
Articles can live here as Markdown.
2026-06-14
Quality as Observability
A short note on treating quality engineering as a signal system rather than a test execution department.
Contact
Bring me a difficult quality problem.
Contract drift, slow suites, noisy CI, flaky distributed tests, AI-assisted triage, or release gates nobody trusts anymore. Those are good conversations.