Use case
INB4 "It's anti-pattern"
Sometimes, most likely when working with native views, some element of the flow might not be displayed. Examples:
- Onboarding of the app when running
patrol develop, if I did not manage to clean app state when opening app in test
- Some native popups might differ between Android versions
- many more, e2e tests can be brutal
Usually this block is enough:
try {
await $.platform.android.tap(AndroidSelector(text: 'Done'));
} catch (_) {
/* ignore */
}
... but I would expect Patrol to allow me to continue with the test even if the element won't be tapped
Proposal
No proposal yet, I'd imagine it's the same logic as platform.mobile.tap without throwing exception in case of failure.
Use case
INB4 "It's anti-pattern"
Sometimes, most likely when working with native views, some element of the flow might not be displayed. Examples:
patrol develop, if I did not manage to clean app state when opening app in testUsually this block is enough:
... but I would expect Patrol to allow me to continue with the test even if the element won't be tapped
Proposal
No proposal yet, I'd imagine it's the same logic as
platform.mobile.tapwithout throwing exception in case of failure.