Cuiar
Sign inDownload

Run a smoke test on staging after each deploy

Sign-in, key pages and main actions checked in the browser, with a screenshot of each failure.

  • On an event: When a new staging deploy finishes
Use in CuiarRun from your AI agent

What it does

The task

Check the Vercel project project for a staging deploy that finished since the last run. When there is one, open staging url and sign in with the test account from the vault. Run these checks: checks. On each page, read the browser console for errors and note the failed network requests. Send me a pass or fail line for each check, with a screenshot and the console error for each failure. Use only test data.

  • It works in Vercel and any website, in the workspace you pick, and signs in with passwords from your Cuiar vault.
  • A routine checks every 15 minutes and acts on what is new: when a new staging deploy finishes.

What you give it

BlankWhat to giveExample
projectThe Vercel project namebrightleaf-web
staging urlThe address of your staging sitehttps://staging.brightleaf.app
checksThe checks to run, in plain wordsSign in, dashboard loads in 3 s, create a project, export invoices as CSV, open billing

What you get back

An example run with the example values above. Your run uses your own data.

Staging deploy of commit 4f2c91a "Fix invoice totals", 4 Nov 11:42

  • Sign in with the test account: Pass
  • Dashboard loads in under 3 s: Pass (1.8 s)
  • Create a project: Pass
  • Export invoices as CSV: Fail. The button shows a spinner for 30 s.

Console: TypeError: Cannot read properties of undefined (reading 'rows') at export.js:88

  • Open the billing page: Pass

1 of 5 checks failed. Screenshot attached.

Run it in Cuiar

  1. 01

    Open it

    Click Use in Cuiar on this page. The side panel opens with the task in the composer.

  2. 02

    Fill in 3 blanks

    Type project, staging url and checks. Tab moves to the next blank.

  3. 03

    Run it, then repeat it

    Run sends it once. To run it when a new staging deploy finishes, make a routine on cuiar.com/routines or with the CLI below.

As a routine, from the terminal

cuiar routines create "Run a smoke test on staging after each deploy" --schedule "*/15 * * * *" --time-zone Europe/Berlin \
  "Check the Vercel project brightleaf-web for a staging deploy that finished since the last run. When there is one, open https://staging.brightleaf.app and sign in with the test account from the vault. Run these checks: Sign in, dashboard loads in 3 s, create a project, export invoices as CSV, open billing. On each page, read the browser console for errors and note the failed network requests. Send me a pass or fail line for each check, with a screenshot and the console error for each failure. Use only test data."

Run it from your AI agent

Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call create_routine yourself.

1. Add Cuiar to Claude Code

claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp

2. Ask your agent

Use the Cuiar tool create_routine to run my "Run a smoke test on staging after each deploy" template with project = brightleaf-web; staging url = https://staging.brightleaf.app; checks = Sign in, dashboard loads in 3 s, create a project, export invoices as CSV, open billing.

Setup for other agents: AI agents.

The tool call

{
  "name": "create_routine",
  "arguments": {
    "name": "Run a smoke test on staging after each deploy",
    "task": "Check the Vercel project brightleaf-web for a staging deploy that finished since the last run. When there is one, open https://staging.brightleaf.app and sign in with the test account from the vault. Run these checks: Sign in, dashboard loads in 3 s, create a project, export invoices as CSV, open billing. On each page, read the browser console for errors and note the failed network requests. Send me a pass or fail line for each check, with a screenshot and the console error for each failure. Use only test data.",
    "schedule": "*/15 * * * *",
    "time_zone": "Europe/Berlin"
  }
}

Related templates

All engineering templates

  • Engineering

    Find why a deploy failed

    The error from the build log, the change that caused it and a suggested fix, sent when a deploy fails.

    On an event: When a deploy fails in Vercel
    • Vercel
    • GitHub

  • Engineering

    Compare page speed before and after a release

    Lab metrics for your key pages after each production deploy, with each page that got slower.

    On an event: When a new production deploy finishes
    • Netlify
    • PageSpeed Insights
    • Google Sheets

  • EngineeringAsks first

    Label and sort new GitHub issues

    Labels, a priority and a possible duplicate for each new issue, applied after you approve them.

    On an event: When a new issue is opened
    • GitHub

  • Engineering

    Test your checkout with Stripe test cards

    Each payment case run in test mode, from a good card to a declined one, with what the buyer sees.

    You start it: When you start it
    • Stripe
    • Any website

  • Engineering

    Find broken links on your website

    Every link and image that returns an error, with the page it is on and the link text, in a sheet.

    You start it: When you start it
    • Any website
    • Google Sheets

  • Engineering

    Check web pages for accessibility problems

    WCAG 2.2 AA problems on each page, with the element, the rule and a fix, the blockers first.

    You start it: When you start it
    • Any website
    • Google Docs