"run tests", "test it", "verify"?
run_unit_tests (fast) then run_integration_tests
← Skill registry
Developer workflowsPublic skills
Test Execution
Test operations for AI agents — run unit/integration/E2E tests, track coverage deltas, debug failures, and gate merges on quality via mcp-test-runner.
What this skill teaches
A reusable playbook for a specific kind of work.
An MCP server tells an agent which actions are available. A skill adds the judgment around those actions: how to recognize the job, which sequence to follow, what to avoid, and how to decide that the result is complete.
Orchestrate test execution — run unit, integration, and E2E tests, collect coverage reports, and analyze failures. Use when running tests, checking coverage, debugging test failures, or validating code changes before merge.
Architecture
How Test Execution guides an ADK-Rust agent.
The skill stays readable and portable because it contains instructions rather than service credentials or business data. ADK-Rust supplies it to the agent, the agent chooses from its reviewed tool boundary, and the connected MCP server performs the authenticated operation.
01
User request
The agent receives a goal expressed in ordinary language.
02
Test Execution skill
Matches intent, supplies the decision guide, and narrows the tool boundary.
03
ADK-Rust agent
Plans the workflow and streams each meaningful step through the runtime.
04
mcp-test-runner
Executes authenticated operations against the system that owns the capability.
05
Verified result
The skill's completion rules shape the evidence returned to the user.
Decision guide
How the agent turns a request into the right action.
These routes come directly from the skill instructions. They help the model recognize intent and select a focused tool or workflow instead of improvising across the entire capability surface.
"specific test", "just this file"?
run_specific_tests(path)
"e2e", "browser", "end to end"?
run_e2e_tests
"coverage", "how much tested"?
get_coverage
"failed", "why", "broken test"?
get_results + get_test_logs
Proven workflows
Repeatable sequences for useful outcomes.
A workflow joins several tool calls into a task the user actually recognizes. The skill explains the sequence and the intended result while ADK-Rust streams the agent's progress through the shared runtime.
013 calls
Pre-Merge Validation
Unit + coverage + integration
022 calls
Debug Failure
Identify test + root cause
031 calls
Targeted Tests
Run specific file/pattern
Tool boundary
The skill may use 7 documented tools.
This allowlist is declared by the skill. It keeps the agent focused on the actions needed for this job while mcp-test-runner retains responsibility for authentication, validation, and the connected system.
run_unit_tests
run_integration_tests
run_e2e_tests
run_specific_tests
get_results
get_coverage
get_test_logs
Working rules
What the agent should do.
- Run tests before approving any code change
- Report coverage delta (not just absolute number)
- Investigate flaky tests — don't just rerun and hope
Operating boundaries
What the agent should avoid.
- Don't skip tests to save time
- Don't decrease coverage without documented justification
Install and connect
Add the skill beside the capability it expects.
Install the repository where your ADK-Rust skill loader can discover it, connect mcp-test-runner, and confirm the declared tools are available before asking the agent to use the workflow.
Install the skill
git clone https://github.com/zavora-ai/skill-test-execution.git \
~/.skills/skills/test-executionADK-Rust loading shape
let skills = SkillLoader::from_dir("~/.skills/skills").await?;
let skill = skills.load("test-execution").await?;
let agent = LlmAgentBuilder::new("agent")
.instruction(skill.instructions())
.tools(skill.allowed_tools(toolset)?)
.build()?;The repository's compatibility statement: Requires mcp-test-runner server connected.
Official documentation
Read the complete skill package.
The repository remains authoritative for its exact instructions, examples, helper scripts, assets, MCP requirements, license, and later updates.
Keep exploring
More in developer workflows.
Browser AutomationWeb operations for AI agents — read pages, extract data, take screenshots, interact with forms, and scrape structured content via headless Chromium.17 allowed toolsCI/CD Pipeline ManagementPipeline operations for AI agents — monitor builds, debug failures from logs, trigger safe deployments, and manage release gates via mcp-cicd.8 allowed toolsCode Search & NavigationCode intelligence for AI agents — semantic search, symbol lookup, call graphs, dependency mapping, blast radius analysis, and ownership resolution via mcp-code-search.8 allowed tools
Source record
Repository metadata for this skill entry.
- License
- Apache-2.0
- Allowed tools
- 7
- References
- 3
- Revision
- da60f7d32513
- Updated
- May 31, 2026