Clear app data before all e2e tests #1632
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Clear app data at the start of each e2e test scenarios, preventing them from bleeding into each other.
Design
Test scenarios can occasionally flake because a full reset is not performed between each test scenario. A new button on the UI allows all Bugsnag data to be cleared.
Changeset
A
Backgroundstep in every.featurefile uses Appium to press the new button, clearing Bugsnag data.I have also taken the opportunity to consistently format all
.featurefiles. Although the diff looks like scenarios have changed in some places, only whitespace changes have occurred other than the addition of theBackgroundstep.Testing
Covered by CI and I have manually checked the device logs to verify that the button is pressed.