You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[6.0] Build one test product for both Swift Testing and XCTest (with Swift Testing enabled by default.) (#7794)
**Explanation:** Refactors the previously-experimental Swift Testing
support logic so that only a single build product is produced when using
both XCTest and Swift Testing, and detection of Swift Testing usage is
no longer needed at compile time.
**Scope:** Implementation of Swift Testing/SwiftPM integration; touches
mostly `swift test` but affects `swift build` and `swift package init`
as well.
**Issue:** rdar://120864035
**Original PR:**
#7777,
#7789,
#7796
**Risk:** Moderate—refactors how we build and run tests.
**Testing:** Existing test coverage in the package as well as test
coverage in the Swift Testing package; additional integration testing
will be added once Swift Testing is in the toolchain.
**Reviewer:** @bnbarham@xedin@briancroom@dennisweissmann
---------
Co-authored-by: Pavel Yaskevich <[email protected]>
throwInternalError("makeTestManifestTargets should not be used for build plan which does not require additional derived test targets")
37
+
varexplicitlyEnabledDiscovery=false
38
+
varexplicitlySpecifiedPath:AbsolutePath?
39
+
if case let.entryPointExecutable(caseExplicitlyEnabledDiscovery, caseExplicitlySpecifiedPath)=destinationBuildParameters.testingParameters.testProductStyle{
if isEntryPointPathSpecifiedExplicitly || explicitlyEnabledDiscovery {
169
167
if isEntryPointPathSpecifiedExplicitly {
170
168
// Allow using the explicitly-specified test entry point target, but still perform test discovery and thus declare a dependency on the discovery modules.
0 commit comments