This repository has been archived by the owner on Feb 22, 2023. It is now read-only.
[e2e] Avoid running failure test using native instrumentation test frameworks #2516
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.
Right now we only want to integration test the failure case of e2e test using flutter driver.
This renames the test so that our CI doesn't try to run it using instrumentation frameworks (Espresso, EarlGrey).
Eventually we can switch from flutter driver to instrumentation frameworks, but this will fix the tree for now.