[automated] Unquarantine stable tests

Open Beginner friendly
#18,366 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
csharp
Domain
testing-qa

Research direction

Use the test-disabler agent and locate Aspire.Hosting.Tests.DistributedApplicationTests.ProxylessEndpointWorks and StartResourceForcesStart. First inspect each test's [Quarantine] attribute, then remove it and run the listed tests to confirm they pass without quarantine. Ensure both candidates are handled and record any missing or skipped test in the PR description.

Written by the indexing model from the issue text.

Description

aim:auto area-app-testing automated triage:bot-seen

Unquarantine Candidates

The following quarantined tests have had 25+ days of quarantined run data with zero failures in the last 25 days, and are candidates for unquarantining.

Last updated: 2026-06-30 00:00:52 UTC

Instructions for Copilot

Use the test-disabler agent to unquarantine the tests listed below. For each test:

  1. Remove the [Quarantine] attribute from the test method
  2. Include a Fixes <issue-url> line in the PR description for each tracking issue so they are automatically closed on merge
  3. If a test does not have a tracking issue (marked as "None" below), note this in the PR description
  4. Validate that all tests listed below have been unquarantined. If any test could not be found or was skipped, call this out in the PR description

PR requirements:

  • Prefix the PR title with [automated]
  • Apply the automated label to the PR
Candidates
Tracking Issue Oldest Run Test
#8728 2026-06-02 Aspire.Hosting.Tests.DistributedApplicationTests.ProxylessEndpointWorks
#15777 2026-06-02 Aspire.Hosting.Tests.DistributedApplicationTests.StartResourceForcesStart
Dominant language
C#
Stars
6.3k
Forks
992
Avg merge
2d 16h
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/aspire

All issues in microsoft/aspire

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.