1.2万 个 · 按相关度排序
Provide reference syntax for selecting .NET tests by name, class, category, or other properties. Help test-running skills construct filters for VSTest and Microsoft Testing Platform, or translate existing filters for a different test framework.
中文简介正在准备中。当前显示英语简介。
Inspect automated test results in TestDino, filter runs by branch or environment, and investigate failed or flaky tests—tests with inconsistent outcomes. Use historical runs to explore likely causes and recommendations for a failing test.
中文简介正在准备中。当前显示英语简介。
Review generated or changed test code against universal testing rules before it ships. Best used reactively after an agent writes, edits, generates, or refactors tests, before presenting, committing, or merging them. Use for pytest (test_*.py, *_test.py), PHPUnit/Pest (*Test.php), Jest/Vitest (*.test.ts, *.spec.js), Go (*_test.go), files under tests/, __tests__/, or spec/, and review requests like 'write tests for X', 'add tests', 'test this', 'review these tests', or PR diffs containing tests. Can also guide test writing when explicitly invoked before the work. This skill is the quality gate that prevents AI-generated test bloat. DO NOT USE for production or implementation code review (use clean-code-guard), CI or test-runner configuration, running or debugging tests, or general architecture discussion.
中文简介正在准备中。当前显示原文说明。
Teststrategie-Berater für Softwareprojekte — wählt die richtigen Teststufen (Unit/Integration/System/Abnahme), Testarten (funktional, nicht-funktional, änderungsbezogen) und Testentwurfsverfahren (Äquivalenzklassen, Grenzwerte, Entscheidungstabellen, explorativ) für die jeweilige Situation und SDLC-/CI-Phase, inkl. Testpyramide, CI/CD-Gates, Shift-Left und Best Practices. Nutze diesen Skill IMMER, wenn Tests geschrieben, geplant, priorisiert oder bewertet werden sollen — bei "schreibe Tests", "Teststrategie", "Testplan", "Testkonzept", "was/wie soll ich testen", "welche Tests fehlen", "Testabdeckung verbessern", "QA aufsetzen", Fragen zu Regression/Smoke/Sanity/Last/Stress/Security-Tests oder beim Einrichten einer Test-Pipeline — auch wenn "Test" nur beiläufig fällt. Abgrenzung — für die TDD-Schleife selbst superpowers:test-driven-development, für Bug-Diagnose bugfix-protocol, für systematische Bug-Suche bugsweep nutzen.
中文简介正在准备中。当前显示原文说明。
Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.
中文简介正在准备中。当前显示原文说明。
Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.
中文简介正在准备中。当前显示原文说明。
Strengthen existing tests with fast-check by checking properties across generated inputs. Find bugs that example tests miss and reduce failing inputs to small, reproducible cases. Property testing is available; the other listed workflows remain planned.
中文简介正在准备中。当前显示英语简介。
Create unit, integration, and E2E tests that check complete user flows, then identify coverage gaps and investigate unreliable results. The skill also supports performance and security test plans, with findings organized by severity and suggested fixes.
中文简介正在准备中。当前显示英语简介。
Provide language-specific reference files for test analysis skills. The catalog helps agents recognize test methods, assertions, skipped tests, waiting patterns, setup and cleanup hooks, external dependencies, and tagging capabilities across different frameworks.
中文简介正在准备中。当前显示英语简介。
Review existing tests using 19 research-backed test smell categories, meaning patterns that can weaken test quality. Get findings ranked by demonstrated risk, with precise code evidence and fixes suited to the test framework in use.
中文简介正在准备中。当前显示英语简介。
Analyze .NET test suites for repeated setup, assertions, and copied test methods. Get a report with file locations, before-and-after refactoring examples, priorities, and readability trade-offs, without changing the source files.
中文简介正在准备中。当前显示英语简介。
Audit Playwright automated test code using context from TestDino. The skill guides a review that produces a local Markdown report, submits findings with a score, and lets you retrieve previously submitted audits.
中文简介正在准备中。当前显示英语简介。
Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. This should trigger for requests such as Review Java code for Spring Boot unit tests; Apply best practices for Spring Boot unit tests in Java code; Write Mockito-first unit tests for Spring Boot services; Avoid unnecessary @SpringBootTest in Spring unit tests; Review Spring Boot slice-free unit test design. Part of Plinth Toolkit
中文简介正在准备中。当前显示原文说明。
Use for Vue 3 testing best-practices review and recommendations — designing and auditing Vitest + Vue Test Utils tests for components, composables, Pinia stores, Vue Router, async/Suspense, Teleport, forms, and accessibility, plus Playwright E2E test-design strategy. Advisory/review only — recommends patterns and flags test smells; does not run tests. Complements mk:vue-best-practices (feature code). Invoke for "review my Vue tests", "how should I test this component/composable/store", or "Vue test best practices".
中文简介正在准备中。当前显示原文说明。
Create unit test scaffolds, sample data, and mocks from code or specifications. Analyze coverage reports to prioritize missing tests, and guide test-driven development through failing tests, minimal implementation, and refactoring.
中文简介正在准备中。当前显示英语简介。
Set up a persistent Microsoft Testing Platform console host that applies code edits and automatically reruns tests. It covers package setup, test selection, and restarting the host when an edit cannot be applied while running.
中文简介正在准备中。当前显示英语简介。
Choose and optionally run .NET test commands that match the project's SDK, test platform, and framework. Target specific tests, collect reports or diagnostics, and report execution results using syntax appropriate to the repository.
中文简介正在准备中。当前显示英语简介。
Organize manual testing in TestDino by browsing, creating, and updating test cases and suites, which group related cases. Maintain steps and preconditions, filter existing cases, and update selected fields while preserving other details.
中文简介正在准备中。当前显示英语简介。
Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Quarkus project; Reduce slow @QuarkusTest usage with Mockito-first tests; Add @InjectSpy partial mocking or QuarkusTestProfile configuration in Quarkus tests; Convert repeated test methods to @ParameterizedTest with @CsvSource or @MethodSource; Write fast pure unit tests for Quarkus services. Part of Plinth Toolkit
中文简介正在准备中。当前显示原文说明。
Generate comprehensive test case documentation from test code, test framework output, existing test docs, and source code context. Use when documenting test suites, creating test specifications, generating test coverage reports, onboarding developers to testing practices, or preparing QA documentation. Analyzes test functions (pytest, unittest) to extract test names, docstrings, assertions, and organization, then produces structured markdown with both overview-level summaries and detailed test case specifications including purpose, preconditions, steps, expected results, and test data. Triggers when users ask to document tests, generate test specifications, create test reports, summarize test coverage, or explain what tests do.
中文简介正在准备中。当前显示原文说明。
.NET testing fundamentals overview and navigation center. Triggered when users ask about "how to write .NET tests", ".NET testing getting started", "required testing tools", "testing best practices", "learn testing from scratch", and other general testing needs. Recommends appropriate sub-skills based on specific requirements, covering testing fundamentals, test data, assertions, mocking, special scenarios, and other 19 fundamental skills. Keywords: dotnet testing, .NET testing, testing getting started, how to write tests, testing best practices, unit test, unit test, xunit, 3A pattern, FIRST principle, assertion, assertion, mock, stub, NSubstitute, test data, AutoFixture, Bogus, validator, FluentValidation, TimeProvider, IFileSystem, code coverage, ITestOutputHelper, test naming
中文简介正在准备中。当前显示原文说明。
盘点现有测试及缺口，将需求、业务规则和缺陷关联到稳定的测试编号与执行结果，通过测试台账追踪哪些行为已经验证、哪些仍需检查。
按照先写测试的流程编写Rust单元、集成和异步测试，涵盖生成多样输入、替换依赖、性能基准测试与覆盖率检查，用于验证行为并补充未测试部分。
Test Temporal workflows in Python with pytest. Use time skipping to avoid long waits, replace activities with controlled test versions, and replay execution histories to check that workflow changes remain consistent with previous runs.
中文简介正在准备中。当前显示英语简介。