Description
Feature or enhancement
Proposal:
In order to run the CPython test suite, CPython source includes an Xcode project that is able to start a Python interpreter and run the equivalent of python -m test. The Python test suite is wrapped in an Xcode XCTest suite that contains a single test - "run the python test suite". The arguments passed to the Python test suite are hard-coded in the .m file that defines the XCTest suite.
The requirement to run tests isn't unique to CPython. Any third party module that is building for iOS will need to run its own test suite.
However, the needs of the CPython test suite and any other test suite are not that dissimilar - essentially, there must be a way to run python -m <some test arguments> on the iOS simulator, and gather the output of that test suite.
It's not possible to pass in command-line arguments to the iOS simulator; but if the iOS Testbed drew it's startup arguments from the testbed app's Info.plist file, rather than hard-coding them in the test case source file, it would be possible for any app to:
- take a copy of the iOS Testbed project;
- copy it's own code into the project;
- modify the Info.plist file to specify the required test arguments
- run the module's test suite on the iOS simulator.
The iOS testbed then becomes an artefact that is reusable between projects.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response