I encountered an error stating 'testSuiteIdNotFound' despite configuring everything correctly according to the documentation. Upon debugging the library code, I discovered the issue stemmed from a mismatch in the test suite extension provided. Specifically, the extension passed was 'ExampleUITests-Runner.app', while the system expected 'ExampleUITests.xctest'. To resolve this, I modified the library code to accommodate both extensions. This fixed the issue, and I can now see the reports in the dashboard. However, I’d like to understand if this modification could have any unintended side effects.
One possible reason I can think of for why ExampleUITests-Runner.app was generated in my case instead of ExampleUITests.xctest is that I am using Cucumberish instead of purely native XCTest. However, I am not entirely sure if this is the root cause.
I encountered an error stating 'testSuiteIdNotFound' despite configuring everything correctly according to the documentation. Upon debugging the library code, I discovered the issue stemmed from a mismatch in the test suite extension provided. Specifically, the extension passed was 'ExampleUITests-Runner.app', while the system expected 'ExampleUITests.xctest'. To resolve this, I modified the library code to accommodate both extensions. This fixed the issue, and I can now see the reports in the dashboard. However, I’d like to understand if this modification could have any unintended side effects.
One possible reason I can think of for why ExampleUITests-Runner.app was generated in my case instead of ExampleUITests.xctest is that I am using Cucumberish instead of purely native XCTest. However, I am not entirely sure if this is the root cause.