Skip to main content

Migrate from manual testing

If you already test in the browser by following a checklist, you can automate that same path in QAlity without writing code. Record once, review the steps, run again anytime, then schedule the work before releases.

First automation pathFirst automation path

1
Pick one repetitive checklist

Start with a short pre-release smoke list (for example login → open dashboard → logout). Avoid migrating your entire regression suite on day one.

2
Record the checklist once

Follow Your first test: create a case, install the Chrome recorder if needed, and perform the checklist while recording.

3
Review and tighten steps

Remove accidental clicks, rename the case clearly, and add a verification where you would normally “check that X is visible.” Use AI step generation during recording for forms and menus if helpful.

4
Run immediately

Use Browser Execution so you can watch playback and confirm the case matches your intent.

5
Share and organize

Invite teammates from Users. Add the case to a suite, then a plan when you are ready for broader runs.

6
Schedule before releases

On Pro or Business, schedule the plan in Cloud Execution. When the run finishes, email notifications can include the completion report so the team does not have to watch the run live.

Habits that helpHabits that help

  • Name cases by outcome (“User can complete checkout”), not by page title.
  • One journey per case. Split long checklists into separate cases.
  • Start with 5–10 high-value tests before attempting full coverage.
  • After UI changes, edit steps or continue recording from the end—re-recording always continues after the last step.
  • Use case variations for valid vs invalid data instead of writing separate manual cases.
Your first test
Record and run end to end.
Quick start guide
Fast path from signup to first run.
AI Step Generation
Generate steps for forms while recording.
Scheduling test plans
Automate plan runs and email reports.