Opportunities › AI-assisted E2E test generation for development teams › Proposed app
Tracewright
Record a browser flow. Get Playwright tests that use your own page objects.
- Score
- 45
- confidence 49
- Evidence
- 5
- items on the page
- Rivals
- 3
- named in sources
- First version
- 40 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2020
- Established market · AI estimate
ScreensConcept
Desktop app: QA and developers record flows and refine tests at their desks, matching code patterns, reviewing pull requests, and integrating with existing test infrastructure. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Recording
Recording14 steps
About this appAI proposal
Tracewright turns a recorded browser session into an end-to-end test written in your codebase's own style. You click through a flow once. It matches each step to the page objects, helpers and constants you already have, and drafts the test file.
It then runs the draft, reads the real failure output, and revises the test until it passes or tells you where it is stuck. No prompt writing, no MCP setup, no describing a flow in text that you could have clicked in seconds.
Built for development and QA teams with an established Playwright suite who are shipping more code with AI help and cannot write tests by hand fast enough.
- Tagline
- Click through it once. Ship the test.
- Voice
- PlainPracticalPrecise
- Why this name
- A wright builds things; a trace is the path a user takes. Together: a builder of tests from recorded paths.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Record in the browser
Click through a flow in a recording session. Each click, input and navigation is captured as a step you can review.
No member yet
Matches your page objects
Steps are mapped to existing page objects, helpers and constants, so new tests look like the ones your team wrote.
No member yet
Failure-driven refinement
Generated tests are run, and the actual error output is used to fix selectors, waits and assertions.
No member yet
Pull request output
Finished tests arrive as a branch or pull request with a diff, so review works the way it does for any code.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#F6F3ECPaper · surface#1D2B2AInk · text#0F5C5ADeep Teal · primary#E2692BSignal Orange · accent#3E8E4FPass Green · data, passing#B9B3A5Stone · borders
Typography
Aa
Tracewright
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test, with seats, projects and generation volume as the possible levers named in the opportunity.
Solo
Free
- 1 project
- 20 generated tests per month
- Pull request output
Team
$79 a month
- Up to 5 seats
- 3 projects
- 300 generated tests per month
- Repo conventions profile
Scale
$249 a month
- Up to 20 seats
- Unlimited projects
- 2,000 generated tests per month
- Priority support
Would you pay Team · $79 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Generated tests land in the customer's own repo as pull requests. Teammates see them, but the tests carry no visible product branding, so use itself spreads little.
- Do they become customers?
- Reach comes through content and developer channels. Test whether developers who see a pull request from the tool, and whether engineers who review it, ask to try it themselves.
- First customers
- Engineering teams of 10 to 50 developers with an existing Playwright suite of several hundred tests, shipping with AI coding tools, and a QA lead or engineer who owns the suite.
- Where to reach them
- Hacker News and dev forums: Share a short demo video of a recorded flow becoming a passing test in a real repo, and invite suite owners to a trial.
- Playwright community: Post in Playwright discussion spaces with a worked example using page objects, and offer free setup to early teams.
- Direct outreach to QA leads: Message QA leads and engineering managers at companies with public Playwright suites and offer a pilot on one flow.
- First milestone
- Five teams with existing Playwright suites each merge at least ten generated tests, and two of them pay for the Team plan.
Why people already pay for this
- VerifiedHacker News post received 19 points and 2 comments
- Public claimDevelopment teams using AI to ship more code face increased QA testing burden
- Public claimText-based AI test generation is inefficient compared to manual test execution
- Public claimRecording-based test generation eliminates setup friction compared to text-based approaches
- Public claim
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Browser recorderBrowser extension capturing DOM eventsA PWA cannot record other sites or local apps; an extension captures the flows.
- This app · Code analysis and LLMRepo parser plus a hosted LLM APIReads page objects and helpers and drafts and revises test code.
RisksAI inference
- TechnicalRunning generated tests needs the customer's app, data and auth reachable from a sandbox. Setup could bring back the friction the product removes.
- AIGenerated tests may pass yet assert little, or hide real bugs. Weak assertions would erode trust quickly.
- CommercialTeams may be satisfied with coding agents on suites of a few dozen tests. The buyer may be only large suites, a narrower market.
- DataCustomers must grant read access to private source code and may record sessions with sensitive data. Security review could slow sales.
- PlatformIt relies on browser extension stores and on Playwright conventions; policy or API changes could break it.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.