Frequently asked questions
What do you test?
Web applications, REST APIs, data and database back-ends, and AI features such as chatbots, RAG assistants, AI agents and MCP servers. Native mobile apps are not offered yet.
Manual or automated?
Both. I start with risk-based manual testing of the journeys that matter most, then automate the checks that must run on every release.
Can you build an automation framework for us?
Yes — Playwright (TypeScript) or Selenium (Java/TestNG) with page objects, data-driven tests, reports and a CI pipeline, handed over with documentation.
What does the final report look like?
A release recommendation (Go, Go with risks or No-Go), open defects with evidence, a business risk register and requirements traceability. You can open a real sample on the Go/No-Go report page.
Can you plug tests into our CI/CD?
Yes — GitHub Actions by default; I have also worked with Azure DevOps and Jenkins pipelines.
Do you work with international clients?
Yes. I am based in India (IST) and share working hours with UK/EU afternoons and US East mornings.
How do you handle our data and credentials?
Staging environments and synthetic or masked data by default, least-privilege test accounts, credentials only in a password manager, no client data in public AI tools, and everything deleted when the project ends.
Do you offer ongoing support?
Yes — monthly packages for regression runs, automation maintenance and per-release Go/No-Go notes.
Are the projects on this site client work?
No. Everything shown here is a demonstration built on synthetic data, so you can inspect it freely. Client work stays confidential.