Clarify documentation to mention that unsatisfied @available on @Test will be considered a skip#1551
Merged
stmontgomery merged 2 commits intoswiftlang:mainfrom Feb 13, 2026
Conversation
…will be considered a skip Resolves rdar://161346836
stmontgomery
requested review from
briancroom,
grynspan,
harlanhaskins and
jerryjrchen
as code owners
stmontgomery
added
documentation
heckj
reviewed
Feb 13, 2026
grynspan
approved these changes
Feb 13, 2026
jerryjrchen
approved these changes
Feb 13, 2026
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
4 participants
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.
This is a small improvement to the Limit the availability of a test section of our Defining test functions article to mention that when a test doesn't run due to an
@availableattribute being unsatisfied, that test will be skipped and represented that way in the results, instead of this only causing a log line to be emitted to the console.Resolves rdar://161346836
Motivation:
A user indicated they were unclear about the current wording since it sounded as if this situation would only be logged and thus could be overlooked or missed.
Checklist: