mastra-smoke-test

Smoke test Mastra projects locally or on staging and production cloud deployments.

27.6k|2.7k|Updated Aug 6, 2024
One-click install
npx skills add https://github.com/mastra-ai/mastra --skill mastra-smoke-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mastra-smoke-test
Source: https://github.com/mastra-ai/mastra/tree/main/.claude/skills/mastra-smoke-test
Command: npx skills add https://github.com/mastra-ai/mastra --skill mastra-smoke-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about mastra-smoke-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I smoke test a Mastra project locally?

Run the smoke test with the local environment flag against an existing project or a newly generated one. The skill starts the dev server on port 4111, then executes the mandatory checklist covering agents, tools, workflows, traces, scorers, memory, MCP, and errors.

How do I run only specific smoke tests instead of the full suite?

Pass the --test parameter with comma-separated test names such as agents,traces. Setup always runs first, then only the specified tests execute while all others are skipped.

Can I test both staging and production deployments from one project?

Yes, multi-environment support uses separate config files: .mastra-project-staging.json deploys to staging.mastra.cloud and .mastra-project.json deploys to mastra.cloud. Each environment gets its own project ID so they do not interfere.

Why are server traces not appearing in Studio after deployment?

Missing server traces usually mean the server has an old token or the deploy lacked MASTRA_CLOUD_ACCESS_TOKEN. Redeploy the server, check deploy logs for observability warnings, and verify the mobs-collector responses if you have GCP access.

What should I do when a stable publish fails partway through?

Treat it as a partial release and follow the recovery reference: record which packages reached npm latest, rerun the same publish workflow from the same commit, verify all versions and git tags, then run final stable smoke against create-mastra@latest.