Manual testing

Manual Software Testing on LaunchWithCursor helps non-developer founders get real UX feedback before launch. Vetted testers exercise your app like a user would, report UI/UX issues and broken flows, and deliver structured findings you can send straight to your AI editor.

You choose how to hire — there is no default path:

1. LaunchWithCursor handles it — submit a brief, accept our quote, and we assign testers and deliver a report.
2. Hire from the marketplace — post a listing with your budget, invite testers or let them claim seats, and manage delivery yourself.

Both paths support multiple testers working collaboratively (shared team chat and test suite) or independently (split test cases).

Objective of this step

• Know when to request manual testing (after Phase Verify and a staging deploy).
• Choose managed QA or marketplace hiring from Hire testers on your project.
• Track progress in QA workspace, use Pull Test Findings in your editor, and rate testers when done.

Why this matters: Founders should not have to become project managers for QA. Managed testing is hands-off; marketplace hiring gives control when you want to pick testers and negotiate directly — all with escrow and structured findings either way.

Before you request

Complete these before opening Hire testers for your project:

1. Finish the Launch checklist and deploy a staging URL you want tested (we pre-fill the URL if the app is hosted on LaunchWithCursor).
2. Complete Phase Verify in your editor so obvious build gaps are already fixed.
3. Have an up-to-date MVP-SPEC and phase plans — testers and test cases are generated from them.
4. Ensure your funds wallet has enough balance to accept the quote when it arrives.

If you have not installed the extension yet, start with Install & sign in. For deploy basics, see Deploy & hosting.

How to use it — step by step

1. Hire testers

Open Hire testers for your project. Pick LaunchWithCursor handles it or Hire from the marketplace — neither is pre-selected. Enter your staging URL (we pre-fill it if the app is hosted on LaunchWithCursor), then submit a managed request or post a marketplace listing.

2. Review our quote

LaunchWithCursor reviews your MVP-SPEC, plans, and app URL, then sends a single quote. You pay once from your funds wallet — no negotiating with individual testers.

3. We assign testers

Our team assigns one or more certified manual testers. You do not choose testers, schedule calls, or share contact details. Testers work in the LaunchWithCursor Chrome extension using AI-generated UX test cases from your spec.

4. Testing runs

Testers follow real user flows — navigation, forms, empty states, mobile layout, and how the product feels to use. If something breaks, they note what they saw in the browser Network or Console tabs.

5. Read the delivered report

When testing is complete, you receive a summary with pass rates, findings by severity, and detailed defect reports. Use clarifications threads to ask questions about any finding (testers see you as “Project owner”, not by name).

6. Fix in your editor

In VS Code or Cursor, run LaunchWithCursor: Pull Test Findings from the LaunchWithCursor extension. That writes docs/qa/findings-{date}.md and FIX-PROMPT.md so your coding assistant can fix blockers and majors first.

Why this matters: Pasting screenshots into chat loses structure. Pull Test Findings gives your AI assistant a prioritized, machine-readable defect list tied to the platform report.

7. Accept the report & rate testers

When you are satisfied with the delivered work, accept the report (this completes the engagement). Optionally rate each tester with a score and short feedback — ratings help us assign the right people on future projects.

What you do not need to do

• Find or interview testers yourself.
• Meet testers on a call or share your email.
• Write test scripts — test cases are generated from your MVP-SPEC and plans.
• Pay each tester separately — one quote covers the engagement.

Need help?

Use Messages on the QA workspace to discuss findings with our team and assigned testers. For product or build questions, use Book Consultation when you need hands-on help.

Keeping the extension current? See Keeping up to date.