Skip to main content
Please make sure you’ve set Decipher up before continuing.
Decipher can automatically generate Playwright tests from session replays, allowing you to quickly create automated tests based on real user interactions. These tests can be organized into test suites and run on configurable schedules.

​
Creating a Test from a Replay

  1. Select an existing Identity or create a new one to simulate the user for this test
  2. Navigate to Tests in your Decipher dashboard
  3. Click Create Test
  4. Click From Replay to begin capturing your interactions
  5. Perform the user flow you want to test in your application
  6. Click Stop Recording when finished
  7. Review the recorded interactions in the timeline view
  8. Enter test details:
    • Test Name (e.g., “Login In With Free Account” or “Saving a Document”)
    • Base URL (where the test should start)
    • Suite (optional - assign to a test suite)
  9. Click Generate Test to create the Playwright test code
For authenticated flows, you can save user identities during recording. This allows the test 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.