Quick start guide
Already know the basics? Here is the fastest path from zero to running your first automated test in QAlity. No code needed.
The full flow in 5 steps
| Step | What to do | Where |
|---|---|---|
| 1. Install | Sign in to QAlity, open a test case, click Start recording, follow the popup - install extension then enable Incognito | app.qality.dev |
| 2. Create | Go to Test Cases, click + Create Test Case, click Untitled Case to rename it | app.qality.dev |
| 3. Record | Enter your website URL, click Start recording, perform your flow, stop recording | Inside the test case |
| 4. Review and save | Check the captured steps, edit if needed, click Save | Test Steps tab |
| 5. Run | Click Run, choose Browser Execution to watch live or Cloud Execution for background | Top right of test case |
How to organize your tests
QAlity has three levels. Start with Test Cases and build up as your tests grow.
| Level | What it is | When to use it |
|---|---|---|
| Test Case | A single test made up of recorded or manual steps | Every individual flow you want to test |
| Test Suite | A group of related test cases | Group all login tests, all checkout tests together |
| Test Plan | A collection of test suites | Run everything at once or on a schedule |
Cases go into Suites. Suites go into Plans. Plans get scheduled.
Browser Execution vs Cloud Execution
| Browser Execution | Cloud Execution | |
|---|---|---|
| How many tests | One at a time | Many at the same time |
| Visual playback | Yes - watch every action live | No - runs in background |
| Screenshots | Yes, every step | Yes, every step |
| Best for | Debugging and verifying a test | Running all your tests fast |
| When to use | When you want to see what happens | When your tests are ready and you want results quickly |
What to do when a test fails
1. Open the test case - Go to Test Cases and click the failed test
2. Check Execution History - Click the Execution History tab to see the latest run
3. Review screenshots - Find the step where it failed from the screenshots
4. Identify the problem - Check if the page changed, an element moved, or a value is different
5. Fix and re-run - Edit the failing step or re-record it, then click Run again
Test result statuses
Not Executed - The test has never been run
Passed - Every step completed successfully
Failed - One or more steps did not complete as expected
Aborted - The run was cancelled before it finished
Stopped - The run was manually stopped