Since we don’t have any name spacing facility yet, I think the right answer here is for packages to always give their tests a name like <Package>Tests.
Even though we might conceptually be able to allow a few limited areas of collision, it gets cumbersome when we might offer features like “run all tests of all dependencies”, since we would have to add more complexity to the build process to support this. That doesn’t feel worth it to me given that non-test targets are going to always require some for of name-based name spacing. - Daniel > On Jul 29, 2017, at 1:57 PM, Taylor Swift via swift-users > <swift-users@swift.org> wrote: > > Many libraries I maintain contain a testTarget called "Tests", but whenever > an external package depends on two or more library packages, the "Tests" > targets conflict with one another, even though the testTargets are never > actually depended on. How do I get the SPM to ignore them? > _______________________________________________ > swift-users mailing list > swift-users@swift.org > https://lists.swift.org/mailman/listinfo/swift-users
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
