Closed plemarquand closed 1 month ago
@adam-fowler The related swift-testing changes are merged. If you're trying this out the swift-testing
used must be the main branch until their next tagged release (> 0.8).
I can tag 0.9 any time, although I've been trying to maintain a beginning-of-the-month cadence.
@grynspan We have a few other things to finish before doing the next release of the extension, so you can probably hold off for a two weeks or so before doing a swift-testing release.
Support running swift-testing tests the same as XCTests. If a test run has both types, swift-testing tests will be run first followed by XCTests.
First a list of XCTests and swift-testing tests to run is parsed from the test request. Test type is determined by a tag on each
vscode.TestItem[]
, either"XCTest"
or"swift-testing"
.swift-testing tests are launched by running the binary namedPackageTests.swift-testing inside the build debug folder. This binary is run with the
--experimental-event-stream-output
flag which forwards test events (test started, complete, issue recorded, etc) to a named pipe. TheSwiftTestingOutputParser
watches this pipe for events as the tests are being run and translates them in toITestRunner
calls to record test progress in VSCode.There are different named pipe reader implementations between macOS/Linux and Windows.