Skip to content

Commit

Permalink
Fix some broken links in Documentation (#1003)
Browse files Browse the repository at this point in the history
I periodically run a broken link checker over swiftlang repositories.
There were a few links pointing to outdated locations in swift-testing.
  • Loading branch information
plemarquand authored Mar 7, 2025
1 parent ad8a13f commit 23af7e5
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion Documentation/ABI/JSON.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ See https://swift.org/CONTRIBUTORS.txt for Swift project authors
This document outlines the JSON schemas used by the testing library for its ABI
entry point and for the `--event-stream-output-path` command-line argument. For
more information about the ABI entry point, see the documentation for
[ABI.v0.EntryPoint](https://github.com/search?q=repo%3Aapple%2Fswift-testing%EntryPoint&type=code).
[ABI.v0.EntryPoint](https://github.com/search?q=repo%3Aswiftlang%2Fswift-testing%20EntryPoint&type=code).

## Modified Backus-Naur form

Expand Down
2 changes: 1 addition & 1 deletion Documentation/WASI.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ See https://swift.org/CONTRIBUTORS.txt for Swift project authors
because it provides instructions the reader must follow directly. -->

To run tests for WebAssembly, install a Swift SDK for WebAssembly by following
[these instructions](https://book.swiftwasm.org/getting-started/setup-snapshot.html).
[these instructions](https://book.swiftwasm.org/getting-started/setup.html).

Because `swift test` doesn't know what WebAssembly environment you'd like to use
to run your tests, building tests and running them are two separate steps. To
Expand Down
2 changes: 1 addition & 1 deletion Sources/Testing/Testing.docc/MigratingFromXCTest.md
Original file line number Diff line number Diff line change
Expand Up @@ -397,7 +397,7 @@ Wherever possible, prefer to use Swift concurrency to validate asynchronous
conditions. For example, if it's necessary to determine the result of an
asynchronous Swift function, it can be awaited with `await`. For a function that
takes a completion handler but which doesn't use `await`, a Swift
[continuation](https://developer.apple.com/documentation/swift/withcheckedcontinuation(function:_:))
[continuation](https://developer.apple.com/documentation/swift/withcheckedcontinuation(isolation:function:_:))
can be used to convert the call into an `async`-compatible one.

Some tests, especially those that test asynchronously-delivered events, cannot
Expand Down

0 comments on commit 23af7e5

Please sign in to comment.