Record a Test
2 min read
Record a Test turns one run of a test into what a team needs from it. You do the test once in a Chrome window, and Hawzu keeps what you did on the test case: as readable manual steps for whoever runs it by hand, and as two automation scripts for whoever automates it.
What one recording gives you
Section titled “What one recording gives you”| Output | What it is |
|---|---|
| Steps | What you did, in plain language, with each assertion you added shown as an expected result. You can write them into the test case as its manual steps. |
| Playwright (TypeScript) | A .spec.ts file whose test title starts with the test case code. |
| pytest + Selenium (Python) | A .py file that records the test case code as a report property. |
| Locators | For each step, every locator the recorder found, which one each script uses, and what it tried and refused. |
The scripts are built by fixed rules from the stored recording each time you open them. No model is involved.
How it fits with your automation
Section titled “How it fits with your automation”Hawzu does not run the scripts. You copy or download them into your repository, and your own CI runs them alongside your other tests.
Each script carries the code of the test case it was recorded on. When you import the CI report into Hawzu, that code is what places each result on the right test case. See How Results Map to Test Cases.
The Object Repository
Section titled “The Object Repository”Each element your recorded steps act on is kept as an object in the project’s Object Repository, with its locators. Hawzu links a recording’s steps to their objects shortly after the recording is saved, or, for a recording made in the create form, after the test case is created. Until then, the scripts use the locators that were recorded.
Once the steps are linked, scripts use each object’s current locator. When a page changes and a locator breaks, you fix the object once, and every test case that uses it gets the new locator the next time its script is downloaded.
Where you record
Section titled “Where you record”- While creating a test case, from the Recording tab next to Steps. See Recording a Test.
- On an existing test case, from its Recordings tab. See View Test Cases.
What you need
Section titled “What you need”- Desktop Chrome 120 or later, with Hawzu Recorder 1.2.0 or later installed.
- Permission to edit test cases, or to create them when you record from the create form.
- A test case in the Multiple or Single step mode. Recording is not available for Gherkin test cases.
At a glance
Section titled “At a glance”| Limit | Value |
|---|---|
| Browser | Desktop Chrome 120 or later |
| Scripts | Playwright (TypeScript) and pytest + Selenium (Python) |
| Step modes | Multiple and Single |
| Recordings saved per month | 30 on Free; unlimited on Growth and Enterprise |
| Recordings per test case | Up to 20 |
| Steps per recording | Up to 500 |
| Size of one recording | Up to 1.5 MB |
What is and is not recorded is listed in Limits and Permissions.