Test integration with non-SPM based builds #907
tristanlabelle
started this conversation in
General
Replies: 1 comment 1 reply
-
In Swift 6 test discovery is done via LSP. There are two custom LSP requests Test running requires knowledge of where the test executable has been written to. At the moment the extension makes assumptions about where to find the test executable based on what SwiftPM does. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I believe the test pane integration relies on SPM to discover tests. Has there been any thoughts about how this could work with non-SPM builds? Granted, SPM is kind of necessary for XCTest since it generates a test runner, but this is at least a concern for
swift-testing
.We have a CMake-based builds and custom scripts that imitate the XCTest test runner generation, so we end up with test executables that work the same as SPM-produced ones. We'll eventually want to migrate to
swift-testing
. In either of those worlds, is there a way to inform the Swift extension how to discover our test executables?If there's no functionality to discover and run tests not built with SPM. We may be interested in contributing it and we could use ideas regarding what the design could look like. Maybe something similar to how
compile_commands.json
enables LSP support without SPM?Beta Was this translation helpful? Give feedback.
All reactions