Skip to main content
Decipher can automatically generate tests from session replays 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

Download the extension

  1. Sign in to app.getdecipher.com
  2. Go to Settings
  3. Download the Chrome extension files
2

Load the extension into Chrome

  1. Open Chrome and navigate to chrome://extensions/
  2. Enable Developer mode (toggle in the top-right corner)
  3. Click Load unpacked
  4. Select the extension folder you downloaded
  5. The Decipher Recorder extension will appear in your extensions list

​
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 recorded session 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.

​
Working with Test Suites

Test suites help you organize related tests and run them together on a schedule.

​
Creating a Test Suite

  1. Go to the Tests page
  2. Click New Suite
  3. Enter a suite name (e.g., “Smoke Tests”, “Critical User Flows”, “Checkout Tests”)
  4. Configure the run schedule:
    • Every 30 minutes
    • Hourly
    • Every 6 hours
    • Every 12 hours
    • Daily (every 24 hours)
  5. Click Create Suite

​
Adding Tests to a Suite

When creating or editing a test, use the Suite dropdown to assign it to a suite. Tests in the same suite will:
  • Run together on the configured schedule
  • Be grouped together in the dashboard
  • Share scheduling and notification settings

​
Managing Suites

From the Tests dashboard, you can:
  • View all tests grouped by suite
  • Update suite run schedules
  • Delete suites (tests will remain but become unassigned)
  • See the last run time and status for each suite
Organize suites by priority or functionality. For example, create a “Critical Flows” suite that runs every 30 minutes, and a “Full Regression” suite that runs daily.

​
Updating Tests

​
Asking for Changes

Request modifications to existing tests using natural language:
  1. Open a test from your Tests dashboard
  2. In the Change Request panel, describe what you want to change
  3. Reference specific steps using @step1, @step2, etc.
  4. Click Submit Change
The system processes your request and shows a before/after comparison when complete. Example requests:
  • “Make @step3 wait longer for the button to appear”
  • “Update @step1 and @step5 to use the new login form”
  • “Add an assertion after @step2 to check the error message”
Type @ to see a dropdown of available steps. Use Shift+Enter for new lines.

​
Change Status

Changes go through these stages:
  • Pending - Queued for processing
  • In Progress - Currently being modified
  • Completed - Ready to review
  • Failed - Unable to process (review the error)
Click on a completed change to see the step-by-step diff.

​
Test Execution

Each test run captures:
  • Pass/fail status for each step
  • Screenshots at key points
  • Console logs and network activity
  • Timing information

​
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.