Description
What is the problem or limitation you are having?
At present, only the iOS distribution artefacts are tested as part of a CI pass. We should be testing all the distribution artefacts.
Describe the solution you'd like
iOS testing is currently performed with the Python-support-testbed project. This means that a Briefcase backend is needed to perform a CI test.
However, as of recent releases, the support package is able to contain testbed project; so we're able to "self host" testing without a dependency on Briefcase.
CI should be modified to run the testbed project for any platform that provides one (or, in the case of macOS, where it isn't required).
We probably don't need to run the entire CPython test suite on a PR review; a representative "smoke test" that proves the patch is able to start a CPython interpreter is probably sufficient. However, the release workflow should do a full test, to ensure that released artefacts fully pass CI.
Describe alternatives you've considered
Add visionOS support (and ultimately, tvOS, watchOS, and catalyst support) to Briefcase, and continue to use Python-support-testbed.
This would work, but would also require a lot more effort. There's also a chicken-and-egg problem with any new Python release, as Python-support-testbed also tests third-party wheels.
Additional context
No response