Loading...
Loading...
Found 53 Skills
Test execution patterns, failure classification, and result analysis
Smoke test for alicloud-media-ice. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-search-opensearch. Validate minimal authentication, API reachability, and one read-only query path.
Runs .NET tests with dotnet test. Use when user says "run tests", "execute tests", "dotnet test", "test filter", "tests not running", or needs to detect the test platform (VSTest or Microsoft.Testing.Platform), identify the test framework, apply test filters, or troubleshoot test execution failures. Covers MSTest, xUnit, NUnit, and TUnit across both VSTest and MTP platforms. DO NOT USE FOR: writing or generating test code, CI/CD pipeline configuration, or debugging failing test logic.
Run Vitest tests and parse results into actionable output. Use WHEN user needs to run JavaScript/TypeScript tests in a Vitest-configured project, verify test suites pass, or get structured failure reports. Use for "run tests", "vitest", "check if tests pass", or "test results". Do NOT use for Jest/Mocha projects, installing dependencies, writing new tests, or auto-fixing failing assertions.
Generate, run, and fix Glubean API tests. Use when the user asks to "write a test", "test this endpoint", "add smoke tests", "explore the API", or work with @glubean/sdk.
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
Discover and execute repository test commands safely with evidence-based command selection and safety guardrails.
Set up Python test environment in Claude Code for web where flox is unavailable. Use when you need to run backend tests and `uv sync` fails due to Python version mismatch.
Execute YAML test plan, stop on first failure, output rich debug prompt
Use after run-plan completes to independently verify the implementation. Reads only the plan document and inspects the codebase from scratch — information-isolated from the execution context. Produces a structured review document with PASS/FAIL verdict. Triggers when the user says "review the work", "verify the implementation", "check if the plan was executed correctly".
Run WebdriverIO test files from the command line. Use when debugging tests, gathering context about test behavior, or verifying changes resolved an issue.