Are there open source SwiftPM integration tests that Xcode runs too?

SDGGiesbrecht · September 27, 2019, 8:31pm

I have been running into a lot of issues with Xcode 11 (mostly involving non‐English packages). Packages that have been working flawlessly in the package manager for years (and still do) are suddenly broken on multiple levels when Xcode tries to load them (package names, dependency URLs, module names, generated bundle identifiers...). I started reporting them through feedback assistant, but I realized it would probably be a more efficient use of both my time and that of Xcode’s support staff if I were able to simply create the meanest Unicode wielding sample package I can dream up and submit it to use as a test fixture.

But since Xcode is not open source, I would have to do it from the package manager side. So the question for those in the know is this: Are there test fixtures that are common to both SwiftPM and Xcode that I can send a pull request to, in order to help Xcode indirectly?

Aciid · September 30, 2019, 2:45pm

Hey @SDGGiesbrecht! There's no publicly known set of common text fixtures but I think having such a test fixture in SwiftPM repository will be a very valuable and it'll be easy for libSwiftPM clients (such as Xcode) to access and incorporate it in their test suites. Feel free to open a PR (it should probably go in Tests/FunctionalTests/MiscellaneousTests.swift).

SDGGiesbrecht · October 1, 2019, 12:11am

github.com/apple/swift-package-manager

Unicode‐Heavy Test Fixture

apple:master ← SDGGiesbrecht:unicode

opened 12:07AM - 01 Oct 19 UTC

SDGGiesbrecht

+180 -0

This idea originated on the forums [here](https://forums.swift.org/t/are-there-o…pen-source-swiftpm-integration-tests-that-xcode-runs-too/29328). It puts all sorts of weird Unicode to use. The package manager handles all of it just fine at the moment. (On macOS at least; I guess CI will tell us how well Linux does.) But it currently trips Xcode 11(.0) in at least three ways: 1. The package name causes Xcode to crash when tests complete. (FB7328781) 2. The dependency URL prevents Xcode from loading the manifest. (Paths don’t trigger this.) 3. The nested package causes Xcode to crash while loading dependencies. Likely Xcode isn’t the only client that can benefit from having this this fixture available to test itself against. *** P.S. SwiftPM’s test manifests seem to out of date, as `--generate-linuxmain` tried to add other new tests. This PR only adds the test it creates to the test manifest, so as to avoid merge conflicts.