Skip to main content
Video by Hause Collective · 23:52 · English

What You’ll See

  • The approach (0:38): plan → test → ship, using Cursor’s Planning feature to approve a plan before any code is written (1:37)
  • Building the app (3:30): a small Next.js + SQLite + Tailwind app, and a real bug on the first run (7:56)
  • Setting up TestSprite (9:27): sign-up, install, and API key, then asking Cursor to run TestSprite against the project (10:33)
  • Watching the tests (11:26): what’s being tested and how, and the tests running against the local app (16:18)
  • What it found (17:52): long-text validation and accessibility-messaging failures, plus the report and generated test code (19:11)
  • Closing the loop (20:45): fix prompts back into Cursor, then re-running the tests

Try It Yourself

MCP Server

Run TestSprite from your IDE, as in the video

CLI

The same test-and-fix loop from the terminal
Recorded in October 2025, before TestSprite 3.0. The screens look different today, but the plan → test → fix workflow still applies. When the video and the docs disagree, the docs are the reference.