Runs, discovers, or recommends dotnet/android tests. Handles standalone tests (plain dotnet test) and full-build tests (local SDK required). Maps source files to relevant test suites. Trigger on test execution requests, questions about available tests, or "which tests should I run for this change?"
根据技术方案实施任务，编写代码和测试，输出实现报告。当用户要求实施任务、开始编码、执行技术方案时触发。参数为 task-id。
审查任务实现代码，输出代码审查报告。当用户要求审查代码、review 任务、检查实现质量时触发。参数为 task-id。
执行 FIT Framework 集成测试（服务启动 + 接口验证），需要先完成 Maven 构建。当用户要求运行集成测试、验证服务接口时触发。
Run unit tests, integration tests, and development tasks for multigres
Execute build, test, lint, serve, and other tasks in an Nx workspace using single runs, run-many, and affected commands. Use when user says "run tests", "build my app", "lint affected", "serve the project", "run all tasks", or "nx affected". Do NOT use for code generation (use nx-generate) or workspace configuration (use nx-workspace).
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing. Do NOT use for quick page debugging or network inspection (use chrome-devtools instead).
Run Jest unit tests for files changed in the current branch
Test @data-client/vue composables and components - renderDataCompose, mountDataClient, fixtures, jest, nock, Vue 3 reactive props, useSuspense testing
Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: "Playwright workspace", "create Playwright Testing workspace", "manage Playwright resources", "ARM Playwright", "PlaywrightWorkspaceResource", "provision Playwright Testing".
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
Use when proving MCC behavior on a real local Minecraft server, validating runtime or protocol changes end-to-end, exercising movement, physics, inventory, entity, chat, or terrain behavior, or running a single-version or cross-version regression sweep.
Blockly 积木编程最佳实践：块结构设计、事件处理、传感器集成、ABS 代码编写流程。触发词：块编程、积木、Blockly 工作流、代码编辑
Run tests in mflux (fast/slow/full), preserve image outputs, and handle golden image diffs safely.
Write tests for Syncpack using the TestBuilder pattern. Use when adding tests for commands, validation logic, or any new functionality. Covers TestBuilder API, assertion patterns, and common test scenarios.
Validate at every layer data passes through to make bugs impossible
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
Write regression/unit tests for TablePro. Pre-loaded with all test conventions, helpers, patterns, and directory structure. Eliminates codebase exploration. Use when asked to write tests, add test coverage, or create regression tests for a commit, feature, or bug fix.
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
Write comprehensive NUnit tests for the Dynamo codebase following Dynamo testing patterns, conventions, and architectural constraints. Use this skill when writing test methods, test classes, setting up test infrastructure, mocking dependencies, testing with .dyn files, or reviewing test code in Dynamo.
