11.6K skills · sorted by relevance
Move .NET tests from VSTest to Microsoft.Testing.Platform, the test execution platform. Update project settings, test commands, and CI pipelines for the selected SDK, then verify test counts and expected reports or diagnostic files.
Connect TestRail test cases with Playwright automated tests. Generate tests from documented steps, send execution results back, create test runs, and check which cases remain unlinked using case IDs recorded in each test.
Create and repair C++ tests, configure GoogleTest and CTest, and investigate failures or inconsistent results. The workflow also covers measuring which code tests exercise and using runtime checks to detect memory errors and race conditions.
Correct and improve existing MSTest tests using APIs supported by the installed version. Refine assertions and failure messages, update data-driven tests, fix setup and cleanup, and address MSTest diagnostics while preserving the project's established conventions.
Convert NUnit 3 or 4 tests to MSTest v4 while keeping the existing target framework and test runner. The workflow translates assertions, test data, setup, and concurrency settings, then compares test counts and results.
Upgrade MSTest v1 or v2 projects to v3, including partially completed migrations. Update packages, repair affected assertions and test data, replace legacy settings, and compare test results while preserving the existing test runner.
.NET advanced testing skills overview and navigation center. Triggered when users ask about "integration testing", "API testing", "containerized testing", "microservice testing", "test framework migration", "Testcontainers", "Aspire testing", and other advanced testing needs. Recommends appropriate sub-skills based on specific requirements, covering integration testing, Testcontainers, Aspire testing, framework upgrades, and other 8 advanced skills. Keywords: integration testing, integration testing, API testing, advanced testing, advanced testing, testcontainers, aspire testing, WebApplicationFactory, TestServer, database test, database testing, EF Core test, MongoDB test, Redis test, Docker test, container testing, microservice test, microservice testing, .NET Aspire, xUnit upgrade, TUnit, framework migration
The English summary is being prepared. Showing the original description.
Write and run Perl tests with Test2::V0 or Test::More, replace external dependencies with controlled test substitutes, and measure coverage—the code exercised by tests. Guidance covers test-first development, failure diagnosis, and migration between testing modules.
Convert .NET tests from xUnit.net v2 or v3 to MSTest v4 while keeping the existing test runner and target framework. Preserve assertions, shared setup, and parallel execution, then compare test counts and outcomes.
Add, repair, and strengthen tests for existing code using the project's testing framework. Covers regression cases, boundary conditions, flaky tests, and coverage gaps, with validation that links requested behaviors to specific tests.
Write JavaScript and TypeScript tests with Jest, Vitest, and Testing Library. Covers functions, UI components, and APIs, including mock replacements for external services, reusable test data, and setup for automated testing.
Identify a .NET project’s test framework, project format, and execution platform: VSTest or Microsoft.Testing.Platform. Trace configuration imports and overrides to explain the result, including conflicting settings or differences between target frameworks.
Creates test starters for React and Next.js applications and analyzes coverage reports to find untested code. Supports unit, integration, and browser-based tests, simulated API responses, reusable test data, and test runner configuration.
Evaluate Vitest tests by the observable behavior and realistic regressions they protect. Guide new test authoring and review existing suites for duplication, dependence on implementation details, and code used only by tests, with evidence for retention or removal.
ISTQB/JSTQB のテストプロセス各工程の出口ゲートとして、工程成果物（test-plan.md / test-analysis.md / test-design.md / test-case.md / テスト実装 / test-execution-log.md / test-monitoring.md / test-summary-report.md）をレビューするスキル。決定論スクリプトの機械検査（トレーサビリティ ID 突合・テンプレ準拠）と test-reviewer サブエージェントの定性レビューを行い、利用者が通過/条件付き通過/差し戻しを判定して軽量記録 test-review-<工程>.md を残す。上流の仕様・基本設計（spec / design-doc 工程。docs/dev/<対象>/spec.md・basic-design.md）は機械検査と利用者判定のみの軽量ゲートとして扱う。各工程スキル（test-plan〜test-report / feature-spec / basic-design）が完了宣言の前に本スキルの実行を促す。ソースコード diff のレビュー（diff-review）とは別物で、対象はテストプロセスの成果物のみ。成果物の修正・代作はしない。/test-review <テスト対象名> [工程] で明示的に呼び出されたときのみ使用する。
The English summary is being prepared. Showing the original description.
Upgrade MSTest v3 test projects to v4 by updating packages, adapting code to changed APIs, and checking execution behavior. It also helps resolve build errors and problems finding tests in CI after an upgrade.
Build and review Python tests with pytest. Use reusable setup, simulated external services, and multiple input cases to check behavior, then measure coverage—the proportion of code exercised by tests—and follow a test-first development cycle.
Write Kotlin tests with Kotest and MockK using test-driven development, where tests come before implementation. Cover asynchronous code, check behavior across generated inputs, and use Kover reports to measure how much code the tests exercise.
Set up Playwright browser tests, generate cases from specifications or URLs, and review coverage gaps. Diagnose tests that fail inconsistently, migrate Cypress or Selenium suites, and optionally connect TestRail and BrowserStack for results and browser testing.
Add and maintain Nexent Python unit tests with pytest. Isolate external dependencies, cover successful behavior, boundaries, and errors, and add regression assertions that detect fixed bugs. Review existing coverage and record test results separately from formal acceptance cases.
Write and migrate tests using the Swift Testing framework with @Test, @Suite, #expect, #require, confirmation, parameterized tests, test tags, traits, withKnownIssue, XCTest UI testing, XCUITest, test plan, mocking, test doubles, testable architecture, snapshot testing, async test patterns, test organization, and test-driven development in Swift. Use when writing or migrating tests with Swift Testing framework, implementing parameterized tests, working with test traits, converting XCTest to Swift Testing, or setting up test organization and mocking patterns.
The English summary is being prepared. Showing the original description.
Audit a Python pytest suite for missed faults, uncovered code, slow tests, and unstable results. Deeper checks deliberately alter code to measure detection, while proposed test removals receive separate validation. The skill reports findings without changing tests.
Run repository tests using commands suited to Python, Node, or Rust projects. Detect the project setup from its files, run the full suite or a selected target, and show passing results or failure details.
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.