Skip to main content
Keep your staging environment under constant watch. This scheduled automation runs your full E2E or smoke suite against staging every night, captures failures with full reproduction context, files Linear tickets for genuine regressions, and posts a summary to your QA Slack channel — so you walk into each morning knowing exactly where staging stands.

Use this template

Open Nightly QA & Smoke Tests in Devin and create the automation with the default configuration. You can customize it before saving.
Looking for a hands-on walkthrough? See the step-by-step tutorial for Nightly QA & Smoke Tests.

​
What this automation does

The Nightly QA template is a foundational automation for any team that ships with a CI/staging workflow. Devin runs your test suite (Playwright, Cypress, custom scripts — whatever you’ve already got), categorizes each failure as a flake or a real regression, and files tickets with enough context for a human to fix without re-reproducing.

​
How it works

Trigger: Schedule event — recurring
  • Event: schedule:recurring
    • Conditions:
      • rrule matches FREQ=DAILY;BYHOUR=2;BYMINUTE=0
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click Nightly QA & Smoke Tests. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Catching regressions that only surface in staging environments
  • Maintaining confidence in long-running test suites that can’t run on every commit
  • Filing tickets automatically for genuine flakes so they don’t rot
  • Keeping your QA feedback loop running overnight and across weekends

​
Customization ideas

  • Change the schedule (hourly, per-deploy, on-demand via webhook)
  • Swap in any test harness — Playwright, Cypress, Jest, pytest, Go test
  • Route results to Linear, Jira, GitHub issues, or Slack
  • Attach secrets for staging database credentials so Devin can query verification data

​
See also