Vijay Prasad Javvadi

Vijay Prasad Javvadi

Building AI-powered test automation
#98495870 followers5 following
#1,632Last month
25 KP
>10,000All time
26 KP

About

Independent researcher building AI-powered software-testing tools. Six journal manuscripts under peer review at IEEE Access, IEEE Software, Wiley STVR, Elsevier JSS, and Springer EMSE. Sole author of three MIT-licensed npm packages (@vijaypjavvadi/bdd2pw, sel2pw, pw-emit) with ~5,400 weekly downloads combined. Building TestForge AI (testforge-ai.com) — listed on G2 in the AI Software Testing Tools category. 19 years SDET / QA automation background. ORCID 0009-0004-1192-6906.🚀 Launching TestForge AI on PH June 9 — AI-powered Playwright tests with self-healing locators

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Forums

TestForge AIp/testforge-aiVijay Prasad Javvadi•

10d ago

What's the worst time-sink in your test automation workflow right now?

Building TestForge AI in public launching here on PH next Tuesday (June 9) and I want to gut-check the problem framing with this community before launch day.

My working hypothesis: most QA teams spend half their week on plumbing writing Page Object boilerplate, fixing brittle locators after every UI change, and triaging flaky failures that turn out to be environment issues, not real bugs. The actual signal (real defects) gets drowned in the noise.

So I built TestForge AI to remove the plumbing: paste a requirement it drafts Gherkin scenarios generates the Playwright TypeScript test files (using Microsoft Playwright MCP to scrape the live DOM and pick stable selectors) runs everything in disposable containers when something fails, an AI analyst built on Anthropic's Claude classifies it (real bug vs flake) and explains it in plain English.

The technical bet: deterministic-first, AI-second. Rules engine handles the common cases instantly; Claude only gets consulted for the 1-2% of edge cases where the deterministic layer is uncertain. Every classification shows you why it was made.

Vijay Prasad Javvadi•

12h ago

TestForge AI - AI-powered Playwright tests with self-healing locators

QA teams spend half their week on plumbing — boilerplate, brittle locators, flaky triage. TestForge AI removes it. Paste a requirement → TestForge drafts Gherkin, derives the POM via Microsoft Playwright MCP, scaffolds Playwright TypeScript, runs in disposable containers. Claude classifies failures (real bug vs flake) and explains in plain English. Backed by 6 peer-reviewed papers (IEEE, Wiley, Elsevier, Springer). MIT-licensed npm suite at ~5,400 weekly downloads.
View more