Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Record manual QA flows, get E2E test code that fits your repo

Details

External ID
47504297
Source
HN
Company
—
Product
Record manual QA flows, get E2E test code that fits your repo
Website domain
quretests.com
Launched
March 24, 2026
Cohort
—
Upvotes
19
Upvotes percentile
0.7312423124231242
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

TLDR: Desktop app for E2E web test generation, built at JetBrains (closed beta). Record the flow in a built-in browser - the agent matches it with your existing codebase, then writes a test that passes, not a draft to debug.Devs use AI to ship more code. That code still needs testing. If your team writes E2E tests by hand, you have a problem - same QA capacity, way more surface to cover.AI agents can write E2E test code, but you're stuck describing flows in text - the agent clicks around via Playwright MCP, takes wrong turns, you re-prompt, retry. 30 minutes for a flow you could click through in 30 seconds.Qure works differently. You record the scenario in Qure's built-in browser by just using your product. The AI turns that recording into code. No prompt engineering, no MCP setup, no explaining your repo in chat - point it at your project and go. Beyond recording, you can also refactor tests, update them, or write new ones from a description.What keeps the AI output grounded:- We match the recording against your codebase - find your page objects, helpers, constants and feed them to the agent instead of hoping it figures out your repo- When agent runs the test, it reads real failure output, fixes with actual error and app contextThis is a closed beta of an experimental product. Web only, works best with Playwright. If your project has a few dozen tests - Claude Code will honestly get you there. Qure makes a difference on larger codebases with existing test infrastructure.5-min demo: https://www.youtube.com/watch?v=4CZw4bSSDCETry the beta: https://quretests.comHappy to answer any questions about the approach, product, or where it breaks - I'm the dev on the Qure team. Egor (@250xp), who leads the project, is in the thread too.

Enrichment

Theme
AI agent frameworks and developer tools
Vertical
—
Function
Workflow automation
Audience
Developer
AI stance
AI-native
Project type
Commercial product
Normalized one-liner
automated end-to-end test generation for developers
Manually corrected
False

Could you build this?

Partial Recording browser events is straightforward, but intelligently parsing an arbitrary codebase's testing abstractions, page objects, and writing deterministic, passing E2E tests requires sophisticated AST analysis and code generation.

What it would actually take: The architecture requires an Electron or CDP-based recording browser that captures DOM events and selector paths. The backend needs a semantic code-indexing engine to parse existing tests (Playwright/Cypress ASTs), pattern-match custom helper methods or Page Object Models, and run an automated loop to execute generated tests and self-correct on failures. Building the agentic verification and refactoring loop to guarantee zero flaky tests demands dedicated compiler and test-automation engineering.

Discussion

2 comments analyzed.

Competitors mentioned: Selenium recorder, Playwright test generator

Concerns raised: Code quality and brittleness of selectors, Requires extensive human steering and refactoring

Competitors

Other products that read as similar to this one — 79 launches clear the similarity bar, closest 8 shown.

Attention rank: #29 of 80 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 143 days after the earliest competitor.

Other launches for this product