Limits and Permissions
6 min read
Record a Test is in beta. These are the edges worth knowing before you rely on it.
What is not recorded
Section titled “What is not recorded”| Not recorded | What you get instead |
|---|---|
| Scrolling, dragging and touch gestures | No step is recorded. If the test depends on one, add it to the script by hand. |
| A route change in a single-page app that loads no page | No step is recorded. The next step waits for its element, and each step still records the page it happened on. |
| A triple-click | The first two clicks are recorded as a double-click. |
| A click or other event the page’s own scripts fire | No step is recorded. The app fires it again when the script runs. |
| Tab and Space, and the keys that move the caret or delete text inside a field | No step is recorded. Typing is saved as the field’s final value. See What gets recorded. |
| A new tab or popup | The step that opened it is marked for review, and both scripts carry a HAWZU_TODO at that step. |
| An element inside a cross-origin iframe | A HAWZU_TODO in the scripts where the frame should be located. |
| An element inside a closed shadow root | The shadow root’s host element is recorded instead. The recorder tells you so in the panel, or on the page when the panel is closed, but the scripts do not mark that step with a HAWZU_TODO, so check it yourself. |
| The contents of an uploaded file | The file name only. A HAWZU_TODO in the scripts names the files to put next to the test. |
| A partial-text check | Assertions compare exactly. Edit the script if you need a partial match. |
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Recordings per test case | 20. Delete one to record another. |
| Steps per recording | 500. The recorder panel tells you when a recording is full. |
| Size of one saved recording | 1.5 MB |
| Recordings made in the create form and not yet attached | 20 per person in each project, removed after 7 days |
| Recordings saved per month | 30 on the Free plan, counted across the workspace; unlimited on Growth and Enterprise. Deleted recordings and drafts still count. Picking an element again in the Object Repository does not. The count starts again on the 1st of each month (UTC). |
Browser and extension requirements
Section titled “Browser and extension requirements”- Desktop Chrome 120 or later. Firefox, Safari and mobile browsers are not supported.
- Hawzu needs Hawzu Recorder 1.2.0 or later, for recording, for the page each step records, and for picking an element again in the Object Repository. When yours is older, Hawzu shows Update Hawzu Recorder, and recording stays off until you update. See Recording a Test.
Scripts
Section titled “Scripts”Two frameworks are supported: Playwright (TypeScript) and pytest + Selenium (Python).
Object Repository
Section titled “Object Repository”| Limit | What it means |
|---|---|
| Suggestions need the same page | A step is suggested as an existing object only when both were recorded on the same page, a host plus a path. The same screen on two hosts, such as staging and production, counts as two pages. |
| Suggestions need the same frame | A step inside a frame or shadow root is only suggested as an object in the same frame or shadow root. |
| Recordings made before Recorder 1.2.0 keep one page | From 1.2.0 each step records the page it happened on, including a route a single-page app changed without loading a page. In an older recording every step keeps the page the recording started on, so its steps may miss a suggestion. Record again to fix it. |
| Suggestions need a test id, or a role and name | Steps found only by CSS, XPath or text are never suggested as an existing object. |
| Drafts have no objects | A recording made in the create form gets its objects once the test case is created. |
| Hand edits are not checked | A locator entered by hand is marked hand-edited, not checked, and cannot change frames or shadow hosts. |
| Downloaded scripts do not update | After an object changes, download the affected scripts again. |
See Object Repository for how suggestions are made.
Permissions
Section titled “Permissions”| Action | Who can do it |
|---|---|
| Record on an existing test case | Anyone who can edit test cases |
| Record while creating a test case | Anyone who can create test cases |
| Remove steps or delete a recording | Anyone who can edit test cases. This includes a recording made in the create form: the buttons show to everyone creating a test case, but without permission to edit test cases, Hawzu refuses the change. |
| Use as manual steps on an existing test case | Anyone who can edit test cases |
| View recordings, their steps, locators and scripts | Anyone who can view test cases |
| View the Object Repository, its objects, suggestions and history | Anyone who can view test cases |
| Confirm or keep separate a suggestion; merge, split, rename or delete an object; fix a locator or revert it | Workspace owners, workspace managers and project managers |
Recordings have no permissions of their own. Each action uses the test case permission shown, in the project the recording belongs to.
Changing an Object Repository object changes the scripts of every test case that uses it, so only the three roles shown can do it. There is no separate permission to grant a custom role.
Troubleshooting
Section titled “Troubleshooting”- There is no Record button. The test case uses the Gherkin step mode. Recording works with Multiple and Single only, so switch the step mode to record.
- “This month’s recordings are used up.” The workspace is on the Free plan and has saved 30 recordings this month. Everything already saved keeps working, and a recording that was running when the limit was reached still saves. The count starts again on the 1st. A workspace owner or manager can start the 14-day Growth trial, or switch to Growth, from the same dialog.
- Record is disabled. Hover over it. This test case already has 20 recordings means you need to delete one first. Record is also disabled while a recording for another test case is running, and the tab says A recording for another test case is in progress in its own window. Finish that recording first.
- “Allow recording in the tab the extension just opened, then press Record again.” The extension does not have permission to record yet. In the Hawzu Recorder tab it opened, select Allow recording and accept Chrome’s request, then select Record again.
- “A recording is already in progress. Finish it in its window first.” Only one recording runs at a time, and Hawzu brings its window to the front. Stop or cancel it there.
- “Hawzu Recorder didn’t answer” or “hit an error while starting.” A recording window may already be open and recording. Check for it before starting again.
- The recorder panel does not open. In the recording window, select the Hawzu Recorder icon in Chrome’s toolbar.
- ”… The recording is kept in the extension and will be offered again.” The save failed, but the recording is not lost. Hawzu offers it again to the same test case when its Recordings tab opens or the Hawzu tab regains focus. The extension keeps it for 7 days.
- “That recording is too large to save.” The recording is over 1.5 MB. Record the test in shorter parts.
- Use as manual steps is disabled. Hover over it to see why: the test case may use the Gherkin step mode, you may not have permission to edit the test case, or it is open for editing, in which case save or cancel first.
- A script cannot find an element. Open that step on the Locators tab to see which locator the script uses and what else was found. To fix it for every test case that uses the element, see Fixing a Locator.
- The Object Repository’s actions are disabled. Only workspace owners, workspace managers and project managers can change objects.