[test-quarantine] Quarantine HttpsConfigurationTests#66032
Merged
Conversation
…g issue Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Comment on lines
+18
to
19
| [QuarantinedTest("https://github.com/dotnet/aspnetcore/issues/66031")] | ||
| public class HttpsConfigurationTests |
There was a problem hiding this comment.
Applying [QuarantinedTest] at the class level will quarantine all tests in this file, including NoFallbackToHttpAddress and LoadDefaultCertificate, which are not listed as failing in #66031. To avoid unnecessarily reducing coverage, consider moving the QuarantinedTest attribute onto only the failing test methods (BindAddressFromSetting/BindAddressFromEndpoint/UseHttpsJustWorks/UseHttpsMayNotImplyUseKestrelHttpsConfiguration/LoadEndpointCertificate) or splitting the flaky tests into a separate quarantined class.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Associated issue: #66031