E2Easy Extension

Introduction

The E2Easy Chrome extension lets you record what you do in the browser—clicks, typing, navigation, form entries—and play it back anytime. You use it to create repeatable test flows for any website without writing code. Record once, run as often as you need for regression testing, demos, or automation.

After you install the extension and sign in, you can start recording on any page, save your flow as a test, and run it locally or on server runners. You can organize tests in folders, create reusable Preconditions (aliases), edit steps in a visual builder or text mode, assign test types, and review run history with statuses, errors, accessibility issues, screenshots, and videos when available.

Installation

Install the E2Easy extension from the Chrome Web Store or from the E2Easy website. You need Google Chrome (or a Chromium-based browser that supports Chrome extensions).

1. Install the E2Easy Browser Extension from the Chrome Web Store.
2. Pin the extension to your toolbar (click the puzzle icon, find E2Easy, then pin) so you can open it quickly.
3. After install, open chrome://extensions, find E2Easy, and enable Allow in Incognito if your tests run in Incognito windows.

The extension will ask for permissions to run on websites you visit and to store data locally; these are required for recording and playback. You can revoke access anytime by removing the extension.

Quick Start

Get your first test flow in three steps.

1. Sign in — Click the E2Easy icon in the toolbar and sign in with your Google account. You need to be signed in to save and run test recordings.
2. Record — Open the website you want to test. In the extension, start a new recording, then perform the actions you want to automate (click links, fill forms, navigate). When you're done, stop and save the recording. Give it a clear name so you can find it later.
3. Play back and refine — Open your list of saved tests, choose the one you just created, and run it. Then open Edit Test Steps to fine-tune selectors, assertions, waits, and reusable Preconditions before sharing or re-running.

Recording a Test

To record a test, open the page where you want to start, pick the target tab, and start recording from the E2Easy extension. Everything you do in that tab is captured: clicks, text input, navigation, scrolling, waits, assertions, and viewport updates. When you are finished, stop the recording and save it as a test.

Tips for better recordings: Use a stable, predictable path (for example, log in first and then open the target screen). Avoid unnecessary clicks or rapid back-and-forth. For dynamic pages, use stable selector attributes (`data-qa`, `data-test`, etc.) and set project-level selector preferences in Project Settings. Add key assertions while recording so verification is built into playback.

Playing Back a Test

To run a saved test, open the extension, find it in your list or folder, and start playback. Depending on your setup, you can run from the extension, on a local server, or on a server runner with browser selection. After each run, E2Easy shows status, duration, and run metadata so you can quickly validate outcomes.

Playback works best when the page structure remains close to the recorded flow. If URLs, selectors, or layouts change, open Edit Test Steps and adjust actions instead of re-recording from scratch. Use run history to inspect errors, accessibility findings, screenshots, and videos to speed up debugging.

Managing Test Recordings

Tests are your saved recordings. Each test has a name and can belong to a folder (including nested folders). From the extension, you can rename tests, move them with drag-and-drop, assign test types, mark a test as a reusable Precondition (alias), insert Preconditions into other tests, and run or delete tests as needed.

Your test data is available through your signed-in workspace and organized per project. You can also manage project variables, credentials, and custom values to reuse secure data across tests, and use composed workflows by combining reusable blocks where supported.

Assertions

Assertions are checks you add to verify page state, text, URL, attributes, counts, and more. You can configure them during recording or later in the visual step editor, and use soft assertions when you want a run to continue after a failure. Well-placed assertions (for example, after sign-in or form submission) make tests more reliable and make regressions easier to diagnose.

Settings

In Settings, you can configure profile, appearance, and language, plus project-level options used in recording and playback. Project Settings include default viewport size, custom selector attributes, Variables (Credentials, Built-in, Custom, Environment), and Test Types for categorization. You may also see update prompts when a newer extension version is available.

Troubleshooting

Recording does not start or capture actions. Make sure you are signed in, a valid tab is selected, and recording is started before interacting with the page. Refresh the tab and try again. If selectors are unstable, configure custom selector attributes in Project Settings and prefer stable test IDs.

Playback fails or stops mid-flow. The page may have changed (layout, load timing, or content). Refresh and retry, then open Edit Test Steps to update selectors, waits, assertions, or Preconditions. Check run history details, screenshots, videos, and accessibility markers to identify the failing step.

Extension seems stuck or out of date. If you see an update banner, use Apply update from the extension UI. Otherwise reload the extension in `chrome://extensions` and refresh your test tab. If installed from Chrome Web Store, confirm the latest version is installed.