What problem does it solve?
Verifying that a Mastra release or deployment actually works end-to-end requires manually exercising agents, tools, workflows, traces, memory, and the Studio UI across local, staging, and production environments, which is slow and error-prone.
Core Features & Use Cases
- Mandatory Test Checklist: Runs a structured suite covering setup, agents, tools, workflows, traces, scorers, memory, MCP, errors, experiments, and Studio/Server deploys, with support for targeted partial runs via
--test.
- Release Smoke Workflows: Handles alpha and stable release verification, including Changesets versioning PR checks, npm publish confirmation, release scope discovery from merged PRs, and partial publish recovery.
- Browser and API Verification: Combines curl-based API checks with Studio browser UI smoke tests, plus helper scripts for server testing, versioning PR spot-checks, and release scope discovery.
- Use Case: Before signing off on a new
@mastra/core alpha release, run the full local smoke suite against a freshly generated project, then deploy to staging and verify traces appear in Studio.
Quick Start
Ask the agent to run a full smoke test of your Mastra project locally, for example by requesting a smoke test with the local environment against your existing project path.