Add feature to demo_app to expose assertScreenshot threshold issue#3259
Add feature to demo_app to expose assertScreenshot threshold issue#3259
Conversation
…ifts the alert downwards/upwards
… downwards comparing to the top position screenshot
…ling Without these changes the flow lives in issues/ which is not picked up by config.yaml's flow globs, and has no tag so run_tests's --include-tags filter would skip it. Tagging failing because the repro is expected to fail until the threshold issue is fixed.
|
Hey @simon-gilmurray I tried moving the test in e2e but now I also see that app file is not apk. How are planning to run the test? Should we build the app and then place it? Or should we have a similar test for android case? |
@proksh Can we mark e2e test with an iOS tag and make a note to add an Android one at a later time? |
Have DMed @proksh and explained that this PR has the feature for demo_app used by e2e |

Proposed changes
Doximity are experiencing issues with assertScreenshot where it is returning a failure on assertion, but the threshold is reporting back as being above the specified limit, e.g. a default 95 threshold erroring with a >96 threshold:
Comparison error: Assert screenshot matches ../screenshots/assertScreenshot_threshold.png (threshold: 95.0%) - threshold not met, current: 96.18651%This PR creates:
assertScreenshot ThresholdbuttonMy suspicion here is that perhaps because the majority of the screen content is the same, just repositioned slightly, it is therefore failing but with a higher than expected threshold.
Slack thread
Resulting diff screenshot:
Testing
issue_assertScreenshotThreshold flow added
Issues fixed