Loading...
Loading...
Found 33 Skills
Execute chaos engineering experiments to test system resilience. Use when performing specialized testing. Trigger with phrases like "run chaos tests", "test resilience", or "inject failures".
Execute QA test plans on Holoscan Sensor Bridge hardware. Reads a user-provided test document, filters tests by the user's setup, determines which tests can run automatically, executes them with pass/fail evaluation, and produces a structured test results report.
Verify whether a GitHub issue is fixed in the local codebase. User provides a GitHub issue URL, the skill fetches it, extracts reproduction steps, builds the product from source, runs the reproduction steps, and reports whether the issue still exists or not.
Verify UI changes in the browser using Shiplight MCP tools.
This skill should be used when the user asks to "test my site", "test the site", "run site tests", "check if site is working", "verify site", "smoke test", "test pages", "check api calls", "test web api", "verify deployment works", or wants to test a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification.
Test execution patterns, failure classification, and result analysis
Apifox Automated Test Execution, Suites & CI: test-suite, scheduled-task, runner, apifox run, execution parameters, iteration data, report upload and CI regression. For complex test-scenario step modeling, please use apifox-test-scenario.
Author, scaffold, and run coding-agent-driven tests: Markdown case files executed by a coding agent against a live environment (browser, API, DB, logs, cloud, telemetry) with an auditable PASS/FAIL/BLOCKED report. Use when a deterministic test would be premature, brittle, too expensive, or too narrow.
PRD-driven automated test orchestration skill. It is used to standardize the implementation of test plans, AI self-testing and self-repair, and test reports for each PRD version; applicable to scenarios such as splitting Unit/Integration/E2E according to acceptance criteria, defining boundaries between automation and manual testing, and generating versioned TEST_PLAN/TEST_REPORT.