Skip to main content
Decipher can automatically generate tests from recordings using the Chrome Extension. Record any user flow on any website, then convert it into an automated test that runs on a schedule.
The Chrome extension works on any website—including sites you don’t own or haven’t instrumented with Decipher.

​
Step 1: Install the Chrome Extension

1

Add to Chrome

  1. Visit the Decipher Recorder on the Chrome Web Store
  2. Click Add to Chrome
  3. Click Add Extension in the confirmation popup
2

Pin the extension

  1. Click the puzzle icon in Chrome’s toolbar
  2. Find Decipher Recorder and click the pin icon
  3. The Decipher Recorder icon will now appear in your toolbar

​
Step 2: Record a User Flow

1

Start recording

  1. Navigate to the website you want to test in Chrome
  2. Click the Decipher Recorder icon in your Chrome toolbar
  3. Click the Record Tab button in the popup
  4. A countdown overlay will appear (3, 2, 1…)
  5. Recording begins automatically after the countdown
2

Perform the user flow

Interact with the website as a user would. The extension captures:
  • Clicks and form inputs
  • Page navigation
  • Errors and console logs
  • Network requests
3

Stop recording

Click the red Stop button in the recording control panel at the bottom of the page. Your recording will automatically open in the Decipher dashboard.
If you’re not signed in to Decipher when you start recording, you’ll be redirected to sign in first, then returned to your original tab.

​
Step 3: Generate a Test from Your Recording

After stopping the recording, Decipher automatically takes you to the test creation page with your recording already loaded:
1

Enter test details

Fill in the test information:
  • Test Name (e.g., “Login Flow” or “Checkout Process”)
  • Base URL (where the test should start)
  • Identity (optional - select a login identity for authenticated flows)
  • Suite (optional - assign to a test suite)
2

Generate the test

Click Generate Test. Decipher will convert your recording into an automated test that can run on a schedule.
For authenticated flows, create a login identity first. This allows tests to automatically log in before running.

​
Best Practices

  • Keep tests focused - One test per user flow (e.g., login, checkout, profile update)
  • Use meaningful names - Name tests clearly to identify what they validate
  • Review generated tests - Always verify the test captures your intended flow
  • Save test identities - For authenticated flows, save login credentials with the test
  • Start with critical paths - Create tests for your most important user journeys first
Need help getting started? Contact our support team for assistance.