The Recorder captures every interaction you perform in the browser and converts it into structured test steps. Each action (clicks, inputs, navigation) is recorded in real time and added to your test case automatically. No scripting or manual step authoring is required.
1. Start recording
Open the Test Cases tab in the left-hand navigation.
Inside your test cases tab, click the Record Steps button. Thunders opens a configuration panel before launching the browser session.
2. Fill in the recording settings
Before the browser launches, configure the following session settings. These values determine how the test behaves when it runs.
Environment: select the environment your test should target, such as staging or production. This controls which base URL and configuration your app loads with.
App: choose the application you want to test.
Browser settings: pick the browser to record in and set any additional options like screen size or language. These settings will be reused when the test runs automatically.
Browser note: Recording works with Chrome and Chromium. Make sure you're using one of these.
Click Start Recording to launch the browser session.
3. Interact with your app
The recorder is now actively capturing your interactions. Navigate and interact with the application normally. Thunders captures each interaction and appends the corresponding test step in real time. The following actions are all captured automatically:
Each recorded action appears immediately in the steps panel on the side, described in plain language (e.g. "Click the Login button", "Type '[email protected]' in the Email field"). Review the panel as you record to verify that each step is captured as expected.
4. Pause, resume, or end the session
You can pause, resume, or end the session at any point:
Pause: click Pause to suspend the recording. The browser session remains open in its current state.
Resume: click Resume to continue recording from where you paused. No steps are lost.
End session: click End session when you have recorded all required steps. Select Save to add the recorded steps to the test case, or Discard to cancel and leave the test case unchanged.
Session timeouts: The session displays a confirmation prompt after 5 minutes of inactivity. The session ends automatically after 15 minutes total. For longer flows, split the recording across multiple sessions.
Your test name is automatically generated at the end of the recording based on the recorded interactions. You can rename it at any time from the test case settings.
5. Run the test
After saving, the recorded steps are added to the test case in order. Click Execute to run the test. Thunders replays each step automatically and reports the result.
§. Edit the test after recording
Tests are fully editable after recording. Use the following options to adjust the test case:
Chat with Copilot to add steps, edge cases, or assertions by describing what you need in plain language. Copilot generates the corresponding steps automatically.
Manually add steps for things that are hard to record, like custom setup actions, teardown logic, or specific assertions.
Edit any step to adjust the description or the target element.
Delete steps you don't need, such as accidental clicks or navigations you didn't intend to include.