# Your first automated flow
Setting up a fully automated regression workflow ensures that your critical user flows are continuously tested without manual effort. It helps you catch issues early, reduce the risk of regressions, and maintain confidence in every release.
With test automation in place, your team can move faster while keeping product quality consistent.
Follow the steps below to set up your first automated test workflow with BugBug.
### 1. Install Test Recorder
To record and run tests in BugBug, you need to install [**the BugBug Chrome Extension**](https://chromewebstore.google.com/detail/bugbug-automation-testing/oiedehaafceacbnnmindilfblafincjb?hl=en-US\&utm_source=ext_sidebar) and enable it in Incognito mode.
1. Install the **BugBug Chrome Extension** from the Chrome Web Store.
2. Open Chrome Extensions settings and enable **Allow in Incognito** for BugBug.
{% hint style="info" %}
**Why this matters**
BugBug runs tests in an incognito window to ensure a clean, isolated environment without cached data, cookies, or extensions interfering with your test results.
{% endhint %}
3. Make sure the extension is pinned for quick access while recording tests.
{% hint style="success" %}
**Tip:** Before recording your first test, close any unnecessary tabs and make sure you’re logged out of your app—this helps simulate a real user journey more accurately.
{% endhint %}
***
### 2. Record test
With the BugBug Test Recorder, you can now create your first automated test.
1. Enter the URL of the web app or website you want to test.
2. Click the **Start recording** button.
Your application will open in a new incognito window, and you’ll see the BugBug recorder overlay in recording mode.
3. **Interact with your app** just like a real user would—click, type, navigate between pages, and complete actions. BugBug automatically captures these interactions and converts them into test steps.
{% hint style="warning" %}
**Important**
Hover actions are not recorded automatically. If your test depends on hover states (e.g., dropdown menus), you’ll need to add those steps manually.
{% endhint %}
\
4\. **Add assertions** to verify key elements of your flow like: login success, dashboard visible, checkout confirmation, etc.
5. When you’ve finished recording all necessary steps, click **Finish and close** in the recorder overlay. Your test will be saved automatically.
You now have your first automated test 🎉
{% hint style="info" %}
[Read the full test creation guide.](https://docs.bugbug.io/creating-tests/recording-the-tests)
{% endhint %}
***
### 3. Run your test
To validate that the steps you’ve recorded work correctly, you need to run the test.
We recommend starting with a local run, and then verifying the results again in the cloud.
1. Open your test in the editor view (where your recorded steps are visible).
2. Click the **Run** button.
BugBug will open a new *incognito* *window* and replay all recorded actions exactly as they were captured.
3. You can watch the test execution in real time. If everything works correctly, you’ll see a **Test Passed** status in the BugBug recorder overlay.
**If the test fails:**
* Review the step where the failure occurred
* [Check the error codes](https://docs.bugbug.io/debugging-tests/error-codes)
* Check selectors, timing, or missing assertions
* Update the test and run it again
{% hint style="success" %}
**Tip:** It’s normal for the first run to reveal small issues (e.g., timing or dynamic elements).
[Read this best practices guide on how to prepare your app for automated testing.](https://docs.bugbug.io/best-practices)
{% endhint %}
Once your test passes locally, you’re ready to move on to the next step.
***
### 4. Create test suite
Once your first test is ready and validated, the next step is to **group it into a test suite**.
Test suites allow you to organize multiple tests and run them together as a regression workflow.
1. Go to the **Suites** section.
2. Click the **New suite** button.
3. Give your suite a clear name, for example: Regression - Core flows.
4. Add your recorded test to the suite.
{% hint style="success" %}
**Tip:** Group tests by feature or user journey (e.g., login, checkout, onboarding) to keep your suites maintainable and easy to scale.
{% endhint %}
You now have a basic regression suite.
{% hint style="info" %}
[Learn more about Suites.](https://docs.bugbug.io/organizing-tests/suites)
{% endhint %}
***
### 5. Run the suite in the cloud
Running tests locally is useful for quick validation, but to **fully automate** regression testing, you should run your suite in the cloud.
1. Open your test suite.
2. Click the **Run in cloud** button.
3. After the run finishes, review the results, screenshots, and logs to verify everything works as expected.
{% hint style="success" %}
**Tip:** Cloud runs eliminate dependency on your local machine and allow faster execution, especially as your test suite grows.
{% endhint %}
***
### 6. Schedule automated runs
Automated testing becomes **powerful when it runs automatically**. To turn your suite into a true regression workflow, you need to run it automatically on a schedule.
1. Go to the **Schedules** tab.
2. Click the **Create schedule** button.
3. Choose the suite you want to run automatically.
4. Choose how often you want to run your tests (e.g., every day, every hour, or after each deployment).
{% hint style="success" %}
**Tip:** Start with daily runs and increase frequency as your confidence in test stability grows.
{% endhint %}
Your regression suite will now run automatically without manual intervention.
{% hint style="info" %}
[Learn more about Schedules.](https://docs.bugbug.io/running-tests/schedules)
{% endhint %}
***
### 7. Set up alerts
To stay informed about failures, configure notifications so your team can react quickly.
1. Go to **Alerts** in the left menu.
2. Click the **New alert** button
3. Choose when the alerts should be sent
4. Choose your preferred notification channel (e.g., email, webhook, Slack).
{% hint style="success" %}
**Tip:** Send alerts to a shared team channel to ensure visibility and faster response times.
{% endhint %}
5. Save your configuration and create an alert.
{% hint style="info" %}
[ Learn more about Alerts.](https://docs.bugbug.io/collaboration/alerts)
{% endhint %}
**You now have your first automated regression workflow up and running 🎉**
Your tests are recorded, grouped, executed in the cloud, scheduled, and monitored—fully automated.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.bugbug.io/quick-start/your-first-automated-flow.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
