You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm super excited about this library, it's a great work!
We were giving it a try on our project but unfortunately we have discovered when the test taps on the notification, the testing session automatically halts given the simulator is triggering a new application launch.
How to test it? (testing the tests)
Include tearDown method on the unit test.
Either check console or follow the lead using breakpoints.
/// pseudo
app.waitForTapOnNotification(timeout:5)
/// This wait won't never been satisfied given tearDown is called due to the application halt.
XCTAssertTrue(app.wait(for:.runningForeground, timeout:10))
You will check the tearDown gets executed right after tapping the notification, given the simulator is triggering a new PID for the app.
Could you confirm you can reproduce on your side? I'd be awesome to get back from your side and tell me that I'm doing something wrongly.
Cheers!
The text was updated successfully, but these errors were encountered:
Hello maintainers!
I'm super excited about this library, it's a great work!
We were giving it a try on our project but unfortunately we have discovered when the test taps on the notification, the testing session automatically halts given the simulator is triggering a new application launch.
How to test it? (testing the tests)
tearDown
method on the unit test.You will check the tearDown gets executed right after tapping the notification, given the simulator is triggering a new PID for the app.
Could you confirm you can reproduce on your side? I'd be awesome to get back from your side and tell me that I'm doing something wrongly.
Cheers!
The text was updated successfully, but these errors were encountered: