skills.rest
mastra-ai
mastra-aiOFFICIAL
Explore all skills by this author →
Website𝕏@mastraGitHub

smoke-test

Automates browser-based smoke testing of Mastra Studio UI and end-to-end flows via Claude-in-Chrome MCP.

27.1k|2.6k|Updated Aug 6, 2024
Search Tags:#automation#testing#browser#mastra#smoke-test#studio
One-click install
npx skills add https://github.com/mastra-ai/mastra --skill smoke-test-mastra-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/mastra-ai/mastra/tree/main/.claude/skills/smoke-test
Command: npx skills add https://github.com/mastra-ai/mastra --skill smoke-test-mastra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an automated, browser-based smoke test for Mastra Studio, enabling quick validation of project creation and core Studio flows without manual clicks.

Core Features & Use Cases

  • Automated Studio sanity checks: Verifies that the Studio loads, and essential pages (Agents, Tools, Workflows, Settings, Observability) render correctly and are navigable.
  • End-to-end UI validation: Executes a predefined smoke test path, captures screenshots, and validates key UI elements to ensure the Studio is healthy.
  • Deterministic, non-interactive execution: Runs with explicit flags and requires minimal setup, suitable for CI or local validation.

Quick Start

Use the smoke-test skill to perform automated Studio validation after creating a Mastra project.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I automate browser-based smoke testing for Mastra Studio?▼

Automate Mastra Studio smoke testing using Claude-in-Chrome MCP to verify UI and end-to-end flows. It checks project creation, studio navigation, agents, tools, workflows, settings, and observability pages while capturing screenshot evidence.

What do I need to run non-interactive smoke tests in a CI environment?▼

Non-interactive smoke test runs require the Claude-in-Chrome MCP server, explicit CLI flags, and environment configuration for your chosen LLM provider. This deterministic setup enables automated Studio validation without manual clicks.

Can I verify Mastra Studio pages like Agents and Workflows automatically?▼

Yes, automated Studio sanity checks verify that essential pages including Agents, Tools, Workflows, Settings, and Observability render correctly and are navigable. The test executes a predefined path to ensure the Studio is healthy.

Does smoke testing Mastra Studio capture visual evidence of the UI?▼

Yes, end-to-end UI validation captures screenshots during the smoke test path. These screenshots serve as evidence that key UI elements render correctly across project creation and core Studio flows.

What is the best way to validate Mastra Studio health after creating a project?▼

Run an automated browser-based smoke test to validate project creation and core Studio flows. It provides quick validation by executing a predefined path, checking essential pages, and capturing screenshots without manual intervention.

Why does automated Studio testing require explicit flags for non-interactive runs?▼

Explicit CLI flags are required for non-interactive runs to ensure deterministic execution suitable for CI or local validation. This setup prevents manual prompts, allowing the smoke test to verify Studio health automatically.

Related Skills

Explore More Software Engineering Skills→
SternrasslerSternrassler
1

Chrome DevTools MCP Skill

Automate browser interactions and testing via the Chrome DevTools MCP Server.

Official
Advanced
TestAny-ioTestAny-io
79

debug

Diagnose Testany test failures by analyzing execution logs and identifying root causes.

Official
Intermediate
KimenzoKimenzo

smoke-test

Create a Mastra project and smoke-test the Studio in Chrome.

Community
Advanced
GGEduGGEdu

browser-qa

Automate browser-based visual testing and UI interaction verification across breakpoints.

Community
Advanced