테스트·보안 스킬

Assess whether tests detect the wrong behavior relevant to a specific change, PR, or commit. Link findings to exact revisions, compare faulty and correct behavior when execution is authorized, and distinguish observed results from predictions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether a regression test detects the original bug
• Assess tests for a new feature
• Review behavior preservation during a refactor

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add unit tests for existing code
• Repair failing or flaky tests
• Cover regression cases, boundaries, and error paths

Create Vally evaluation specifications for skills, custom agents, and workflow packages. Design distinct test requests, prepare fixture files, define automated checks and outcome rubrics, and size comparisons to provide meaningful evidence without favoring the skill’s wording.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create an eval.yaml for a skill or custom agent
• Define outcome-based checks and judging rubrics
• Prepare fixture files that reproduce specific failures

Diagnose why an existing skill fails evaluations or shows no clear improvement. Separate content problems from test data, execution failures, activation issues, and insufficient evaluation tasks, then apply targeted fixes and validate them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a regression after a skill change
• Diagnosing evaluations that return no results
• Fixing a skill that fails to activate

Make specific C# behavior testable by adding a minimal way to replace time, randomness, or other external dependencies. Preserve public APIs and production behavior, then run repeatable tests without real file access or waiting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing deadlines and delays with controlled time
• Testing file operations without touching real files
• Testing random or environment-dependent behavior

Calculate change risk for a specific .NET method, class, or file by combining code complexity with measured test coverage. Get ranked results and recommendations on where to add tests or simplify logic.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Calculate risk scores for a specific method
• Prioritize tests within a class
• Find complex, undertested methods in a file

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting an exact test command for a repository
• Running a specific class, category, or target framework
• Collecting TRX reports, coverage, or diagnostic logs

Review test files or suites for missing checks, hidden exceptions, unreliable timing, shared state, and maintenance problems. Get a severity-ranked report with specific locations, explanations, and concrete suggestions for improving the tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing whether existing tests meaningfully check results
• Investigating timing and execution-order risks in tests
• Prioritizing test improvements before editing code

Find changes in observable behavior that existing tests could miss. Map public results to test assertions, identify gaps in boundaries, permissions, and calculations, and propose focused tests, with optional verification when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether existing tests would catch a bug
• Find missing boundary and permission-denial tests
• Review exact amounts and rounding in financial calculations

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrading an MSTest v3 project to v4
• Fixing compilation errors after an upgrade
• Updating custom TestMethodAttribute implementations

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up MTP console hot reload
• Automatically rerunning selected tests after edits
• Restarting after unsupported code changes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Making assertion failures easier to understand
• Correcting expected and actual argument order
• Improving existing data-driven tests

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Migrate .NET test projects from VSTest to MTP
• Update test commands in CI pipelines
• Translate xUnit.net v3 test filters

Find language-specific guidance files for a code-testing pipeline. This reference catalog points agents to build and test commands, mocking patterns, common errors, and selected workflow examples across languages including .NET, Python, TypeScript, Go, and Java.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding test guidance for a project's programming language
• Locating build commands and test framework guidance
• Finding mocking patterns and common error references

Find source files with no matching test references by parsing code without building or running tests. Produces a source-to-test map and suggested test locations, helping plan test additions across supported programming languages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• List source files with no matching tests
• Choose locations for new test files
• Check source-to-test pairing after adding tests

Interpret .NET coverage reports, which show code exercised by tests, to explain missing coverage and stalled progress. Calculate the gains needed to reach a target and, when requested, combine coverage with complexity to rank risk.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explain Cobertura reports and partially covered conditions
• Find the code keeping coverage from improving
• Calculate line gains needed to reach a coverage target

Review existing tests to see whether their assertions, the checks that verify expected behavior, are meaningful and varied. Get metrics, examples of weak checks, and specific recommendations for improving verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing whether passing tests check meaningful behavior
• Finding tests with missing or trivial assertions
• Measuring the variety of checks across a test suite

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Request a test review using formal academic categories
• Prioritize test problems by their demonstrated risk
• Find causes of flaky tests or misleading passes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Selecting tests by class or method
• Including or excluding tests by category or property
• Translating VSTest filters for xUnit v3 on MTP

Keep older instructions working by forwarding explicit calls under the former name to code-testing. This compatibility alias passes along the original request and follows that skill’s workflow without adding another interpretation step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Following older instructions that use the former skill name
• Forwarding an explicit legacy call to code-testing
• Checking the distinction between skill and custom agent names

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Migrating NUnit 3 or 4 tests to MSTest v4
• Preserving parameterized tests and test data
• Reviewing shared state and parallel execution during migration

Review explicitly selected tests or bounded pull request changes without running or editing code. Receive a follow-up decision for each test, A–F quality bands where assessable, evidence-based notes, and concrete suggestions for improvement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a named test method
• Assessing every test in explicitly selected files
• Preparing per-test feedback for pull request changes

Classify existing tests with standard tags for success cases, errors, boundaries, and other behaviors. Get a per-test mapping and distribution summary, or apply tags using supported framework syntax and verify compilation and test discovery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing success-case and error-case test counts
• Adding standard tags to existing tests
• Reviewing the mix of boundary and integration tests

Migrate .NET tests from xUnit.net v2 to v3 while preserving the existing test runner. Update packages, project settings, and affected test code, then verify test discovery, execution, and skip behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrading xUnit.net v2 test projects to v3
• Fixing compilation errors caused by v3 changes
• Updating custom test attributes and async tests