Set appActivity and appPackage Appium capabilities to avoid RN test flakes #2065
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
Set appActivity and appPackage Appium capabilities, using Maze Runner options, to avoid test flakes when trying to start the Android React Native test fixtures.
Design
The main change here should resolve a common test failure when starting Android apps with Appium 2. After making the initial change, there was some confusion resulting from each test fixture having a difference package name. So I've also taken the opportunity to make them all consistent, as
com.reactnative
.Changeset
The number of changed files looks unwieldy, but it's the same set of simple changes made many times.
A number of files in the diff are showing as deleted and created, but all I've done is change their package, resulting in a file move that GitHub somehow hasn't recognised.
Testing
Covered by a full CI run.