The iOS target is currently disabled due to the fact that enabling it would cause tests to fail on CI. This is because there are a number of tests that rely on files in the test resources directory, but iOS tests run on the simulator, and don't have access to the local file system.
Here are a few of the ways we could do this:
Just enable the target and accept failing CI builds. Not ideal.
Move the file-based tests to jvmTest to only run them only on JVM. A couple of tests like the performance tests are already JVM-only.
Create an intermediate source set like nonIosTest or desktopTest and move the file-based tests there.
Remove all file-based tests currently in commonTest. Not ideal, since some of them test functionality not covered by the spec tests.
Find a way to copy the test resources into the simulator before running the tests.
It would be great to publish the iOS target in the next release, so I'd love to hear your thoughts on if there's any approach you prefer.
The iOS target is currently disabled due to the fact that enabling it would cause tests to fail on CI. This is because there are a number of tests that rely on files in the test resources directory, but iOS tests run on the simulator, and don't have access to the local file system.
Here are a few of the ways we could do this:
jvmTest
to only run them only on JVM. A couple of tests like the performance tests are already JVM-only.nonIosTest
ordesktopTest
and move the file-based tests there.commonTest
. Not ideal, since some of them test functionality not covered by the spec tests.It would be great to publish the iOS target in the next release, so I'd love to hear your thoughts on if there's any approach you prefer.