# Software Regression Testing Every Night, Automated

Source: https://maito.app/workflows/nightly-regression-run

Every night Maito runs your key flows in a browser on the latest build, with each user role, and posts a morning report with a video of any failure.

Your key flows get tested every night, with a report in the morning.

[QA](https://maito.app/workflows/team/qa) · [Software](https://maito.app/workflows/industry/software) · On a schedule · Updated October 19, 2026

Works with

-   Slack
-   Email

## How do you automate regression testing?

To automate regression testing, set a Loop in Maito for each night. It opens the latest build in a browser, runs your key flows such as signup, checkout and export with each user role, and posts a report in Slack by morning. For any failure it attaches a video and names the likely cause.

## How it's done today

Regressions are found by customers.

## What Maito does

1.  Each night, run the main flows
2.  Compare with the last good run
3.  Report what changed

## Example

Loop run: Nightly 2:00 AM · Regression run

**Maito** (2:21 AM):

Nightly run on build 4.13-rc2 (commit 3be91a): 2 of 3 flows pass.

• Signup: 12 of 12 steps pass  
• Checkout: 17 of 17 steps pass  
• Export: fails at step 4. The Export CSV button is missing for Viewers.

Last fully green run: Oct 17. PR #887, Role-based toolbar, was merged Oct 18 at 4:40 PM. It's the likely cause.

**Catch:** Admin and Editor still see the button. A run on one admin account would have passed. I tested all three roles.

Attached: export-viewer-oct-19.mp4.

**Mia** (8:50 AM):

is this on production too?

**Maito** (8:57 AM):

No. Production runs 4.12, which predates #887. I checked with the same Viewer account and the button is there.

## How to set it up

On a schedule Nightly regression run

Ask your agent

“Every night at 2, test signup, checkout and export in a browser on the latest main build. Use Admin, Editor and Viewer accounts. Post what changed since the last good run in #qa.”

## What it won't do

It follows the steps you described, so a bug outside those steps goes unseen. It reports the likely cause, but a developer confirms it.

## Questions

### Which flows does it test?

The ones you describe, such as signup, checkout and export. Add or change flows by telling Maito in Slack.

### Does it test with different user roles?

Yes. Store a login for each role in the Vault and it runs the flow as each, which catches role-only bugs.

### How does it find the likely cause?

It compares the last green run with the failure and checks which merged pull requests landed in between.

## More qa workflows

-   [Test a branch in a real browser before merge Every change gets clicked through in a real browser, with a video. QA · When something happens Works with Slack, Email.](https://maito.app/workflows/test-a-branch-in-a-real-browser-before-merge)
-   [Reproduce a reported bug against the last release Check whether a bug is new, old, or already fixed. QA · When you ask Works with Slack, Email.](https://maito.app/workflows/reproduce-a-reported-bug-against-the-last-release)
-   [Write test cases from a spec Turn a feature spec into a checklist of test cases, including edge cases. QA · When you ask Works with Box.](https://maito.app/workflows/write-test-cases-from-a-spec)
-   [Check the site on many screen sizes See how key pages look on phones, tablets and wide screens. QA · When you ask Works with Slack, Email.](https://maito.app/workflows/check-the-site-on-many-screen-sizes)
-   [Check for broken links and pages Crawl your site and docs for broken links, missing images and errors. QA · On a schedule Works with Slack, Email.](https://maito.app/workflows/check-for-broken-links-and-pages)

[See all workflows](https://maito.app/workflows)

## Put your AI teammate to work.

Set it up in minutes. Start with this one, and let it earn the next one.

[Put Maito to work](https://maito.app/login?returnTo=%2Fworkflows%2Fnightly-regression-run)[Book a demo](mailto:support@maito.app?subject=Maito%20demo)