[Office Hours] testLicenseInformationPage() passes locally but fails on the CI #126
-
Related DiscussionHi! We have been struggling to merge one of our PRs as the Goes from 1 -> 2, which is what is causing it to fail because the tap does not surface the correct view as it is a tap on the simulator reloading and then the test verifying that the correct view was surfaced fails. ReproductionRe-run failed jobs on the following action and download the artifact to see the test failure in detail. Additional contextStanford-360 project Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@kkellybonilla Thank you for asking this question; this is very unfortunate! Unfortunately the iOS simulator is really flakey and sometimes crashes some time after a reset. This is not something we can easily solve ourselves nor something that you can solve in your app, this is a bug in Xcode and the iOS Simulator. The reboot screen should never be surfaced during a UI test. I would suggest to remove the UI test from your UI tests for now. Not ideal but the test is mainly there to validate the functionality in the Template application and can be removed in your copy, it would make more sense to eventually add UI tests to your app that are specific to the app in the future (maybe as soon as you have finalized your PR). |
Beta Was this translation helpful? Give feedback.
@kkellybonilla Thank you for asking this question; this is very unfortunate! Unfortunately the iOS simulator is really flakey and sometimes crashes some time after a reset. This is not something we can easily solve ourselves nor something that you can solve in your app, this is a bug in Xcode and the iOS Simulator. The reboot screen should never be surfaced during a UI test.
I would suggest to remove the UI test from your UI tests for now. Not ideal but the test is mainly there to validate the functionality in the Template application and can be removed in your copy, it would make more sense to eventually add UI tests to your app that are specific to the app in the future (maybe as soon a…