Jonathan Grynspan

Implement an overload of `confirmation()` that takes an unbounded range.

2

Unbounded ranges are not meaningful when used with `confirmation()` because _any_ confirmation count matches. As well, the `...` operator produces an instance of `UnboundedRange` which is a non-nominal type and...

Add support for non-copyable types as expectation arguments

8

Add support for non-copyable types as expectation arguments, e.g.: ```swift struct S: ~Copyable, ... {} let a: S = ... let b: S = ... #expect(a != b) #expect(a.foo()) #expect(a.isBar)...

This PR adds a new `Issue` kind, `.recordedByTool`, that takes a custom payload provided by a third-party tool or library (e.g. Nimble). This case can then be used to distinguish...

This PR adds a `Test.isRunning` static property that tells the caller if _any_ thread/task/queue/etc. is currently running Swift Testing code. This property is distinct from `Test.current` because that property has...

Adopt `Mutex`

2

Swift Testing should adopt `Mutex` from [SE-0433](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0433-mutex.md). We won't be able to adopt on Darwin due to back-deployment requirements, but we can adopt for Linux/Windows. Linux needs one `pthread_mutex_t` for...

Add support for Sixel graphics

7

On terminal apps that support it (mainly Linux), we could add support for Sixel graphics to improve the display of test diamond symbols from `swift test`. On macOS, when SF...

_[One line description of your change]_ ### Motivation: _[Explain here the context, and why you're making that change. What is the problem you're trying to solve.]_ ### Modifications: _[Describe the...

Write documentation for tools integration ("how to write a CI plugin" sort of thing)

1

We should document how to integrate Swift Testing into CI flows using the JSON ABI.

Add an experimental console output prefix option for command-line output.

1

This PR adds the ability to specify a prefix that should be applied to all output from the command line when using `swift test`. For example, if you specify the...

[Post-6.0] Fix up .spi.yml

1

Per @finestructure 's comment [here](https://github.com/apple/swift-testing/pull/470#discussion_r1636395363): > [...] (And drop the `swift_version: 6.0` line once Swift 6.0 is released.)