TestNeoProduct walkthroughs

Watch · Record · Generate · Run

See TestNeo on a real workflow.

Five product walkthroughs: record a journey and replay it, turn a Figma design into executable tests, update only the tests a design change affects, catch visual regressions in a batch run, and run QA from Claude Desktop.

01 · Recorder

Record once. Run anytime.

Capture a real browser journey, save it as a reusable test, and replay it without maintaining a Playwright or Selenium script.

What the walkthrough shows

  • Record clicks, inputs, and navigation in the browser.
  • Replay the saved journey against the live application.
  • Keep selector memory and recover when an element moves.
  • Review screenshots, console errors, failed requests, and Lighthouse scores.
  • Spot flaky steps, broken selectors, and repeating failure patterns.
  • QA engineers
  • SDETs
  • Engineering managers
Open the platform

02 · Figma Generate and Run

From a design file to a test run.

Start from a Figma design. TestNeo reads the screens, writes scenarios, generates Playwright automation, and runs it.

What the walkthrough shows

  • Upload a Figma design as the starting point.
  • Read screens, fields, journeys, and likely edge cases.
  • Generate positive, negative, validation, and boundary scenarios.
  • Turn those scenarios into Playwright automation.
  • Run the suite and review the execution result.
  • Designers
  • QA
  • Frontend teams
Figma workflows in MCP docs

03 · Updated designs

Change the design. Update the tests that moved.

Upload a revised Figma file against the tests you already generated. TestNeo marks what changed, refreshes those cases, and runs them.

What the walkthrough shows

  • Keep the original design and the first generated suite.
  • Upload the next sprint’s Figma file into the same project.
  • Compare screens and see which tests are affected.
  • Leave unchanged tests in place.
  • Refresh the impacted cases and run them for validation.
  • QA managers
  • Product
  • Sprint teams
Watch the first Figma run

04 · Batch run and visual regression

The screen changed. Decide if it should ship.

Run the suite, compare each screenshot with the baseline, and review missing controls, layout shifts, and wrong values before the release.

What the walkthrough shows

  • Run existing scenarios in Batch Runner or CI.
  • Capture screenshots and compare them with the baseline.
  • A missing Place Order button blocks checkout.
  • A product price moves from $49.00 to $4.90.
  • Read how much of the screen changed, the severity, and the recommended action.
  • Approve the change, update the baseline, or reject it.
  • QA
  • Release managers
  • Migration teams
Visual regression page

05 · Claude Desktop + MCP

Ask Claude. TestNeo runs the check.

Connect Claude Desktop to TestNeo and trigger runs, read results, and check release readiness from the chat your team already uses.

What the walkthrough shows

  • Connect Claude Desktop to TestNeo with MCP.
  • Find a project, a test, and an environment from chat.
  • Run a test and read pass or fail, steps, and duration.
  • Open the execution dashboard for screenshots and logs.
  • Ask for PR history, release readiness, and project health.
  • Claude Desktop
  • Cursor
  • VS Code

Build. Test. Ship.

Record a journey, start from a design, compare a build, or ask from Claude. The same evidence lands in TestNeo.