test-management

Name: test-management
Availability: InStock
Author: Microsoft

Quarantine or disable xUnit tests using QuarantineTools attributes in the aspire repository.

6.2k|952|Updated Sep 25, 2023

Search Tags:#flaky tests #dotnet #xunit #test management #GitHub issues #quarantine #ci stability

Ready to run

npx skills add https://github.com/microsoft/aspire --skill test-management-microsoft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-management
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/test-management
Command: npx skills add https://github.com/microsoft/aspire --skill test-management-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams stop broken or flaky unit/integration tests from blocking CI by quarantining or disabling them with the appropriate QuarantineTools annotations.

Core Features & Use Cases

Quarantine or disable failing tests: Applies the correct attribute mode (QuarantinedTest for “quarantine/unquarantine” or ActiveIssue for “disable/enable”) to the exact fully-qualified test method.
Conditionally scope test quarantines: Supports platform/CI-based conditional execution by guiding how to add PlatformDetection conditions after QuarantineTools creates the base attribute.
Verify outcomes end-to-end: Recommends building and running the affected test project while excluding quarantined and outerloop tests to confirm the skip behavior.

Quick Start

Ask the agent to quarantine the test HealthChecksRegistersHealthCheckService with the issue URL https://github.com/microsoft/aspire/issues/11820 only on Azure DevOps.

Frequently Asked Questions about test-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I quarantine flaky xUnit tests blocking CI in the dotnet aspire repository?▼

To quarantine flaky xUnit tests blocking CI, apply QuarantineTools-managed attributes like QuarantinedTest to fully-qualified test methods with a mandatory GitHub issue URL to skip execution safely.

When should I disable a broken test instead of quarantining it?▼

Disable a broken test using the ActiveIssue attribute mode instead of quarantining it with QuarantinedTest when the test failure is a known product bug rather than intermittent flakiness.

Can I scope test quarantines to only apply on specific platforms or CI environments?▼

Yes, you can scope test quarantines to specific platforms or CI environments by adding PlatformDetection conditional arguments after QuarantineTools creates the base attribute.

What is required to unquarantine or re-enable a previously disabled xUnit test?▼

Unquarantining or re-enabling a disabled xUnit test requires running QuarantineTools in the correct removal mode against the fully-qualified test method to strip the managed attribute.

How do I verify a quarantined test is properly skipped during local builds?▼

Verify quarantined tests are skipped by building and running the affected test project with filters that exclude quarantined and outerloop tests to confirm the expected skip behavior.

Do I need a GitHub issue link to quarantine a failing unit test?▼

Yes, a GitHub issue URL is mandatory when quarantining failing unit tests, ensuring traceability between the skipped test method and the tracking issue for the underlying failure.