Figured out how to run tests for iOS ``` xcrun simctl spawn

Question

Figured out how to run tests for iOS ``` xcrun simctl spawn lt sim name like iPad Air 2 gt lt path to test kexe gt ```

basher · Answer

Filed an issue here <https github com JetBrains kotlin native issues 2578>

alec · Answer

alec · Answer

agree this should just be handled automatically

alec · Answer

i imagine they havent because part of that task references a target you define

icarumbas · Answer

Isn t it already exists <https github com JetBrains kotlin mpp example blob master greeting build gradle>

russhwolf · Answer

Examples exist but it isn t provided by default either in the plugin or in the new project templates

basher · Answer

< maxim> that build gradle shows them creating a custom task to do it

basher · Answer

IMO it should be built into the plugin

icarumbas · Answer

< basher> got it now Thanks

basher · Answer

Np

basher · Answer

gt i imagine they havent because part of that task references a target you define < alec> i m referencing a task generated from the kotlin multiplatform plugin Seems like `fromPreset` or `targetFromPreset` in 1 3 20 could just generate this task too

alec · Answer

yup they could at the very least create a test task for each target `iosDeviceTest`

alec · Answer

i could add it to our cocoapods plugin wink

russhwolf · Answer

But something still needs to tell it which simulator to use Just having a target defined doesn t specify that

alec · Answer

i still need to figure out the best way how to get these tests to run as part of a CI build w cocoapods

basher · Answer

Heh yeah slightly smiling face

alec · Answer

yea the task in their example defaults to an iPhone 8 simulator

basher · Answer

< russhwolf> agree but it could specify a default and then allow it to be altered as a variable in the `fromPreset` block

basher · Answer

If it wanted to be extra fancy and verbose it could run `xcrun simctl list` and output one task per sim It ll generate a lot of tasks but the could be configurable as well

russhwolf · Answer

yeah I agree I just mention it to highlight that there are some API decisions to make before integrating it into the plugin which maybe is why they haven t yet

basher · Answer

Good point

basher · Answer

< alec> the more I think about it it prob makes sense to have a generic iOS plugin

basher · Answer

The maintenance burden of this feels beyond the scope of K N