You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Detox tests with fixtures on the MetaMask app for Android, some Mac machines used by dev/QA users encounter issues. While the fixture server starts successfully, the app does not build into the required test state as expected for Android. This issue appears to be intermittent and only affects specific devices.
Steps to Reproduce
Build the app for Android using the command: npm run test:e2e:android:debug:build
Run the Detox tests with the command: npm run test:e2e:android:debug:run
Observe the app's state after the fixture server starts.
Expected Behavior
Tests that engage fixtures should start the app in the configured setup where the app opens at a specific spot, similar to the behavior on iOS.
Actual Behavior
The fixture server runs successfully, but the app's configuration setup is not engaged. Instead, the app starts from the beginning, ignoring the expected fixture configuration.
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
Engineering (needed in most cases)
Design
Product
QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
Security
Legal
Marketing
Management (please specify)
Other (please specify)
References
No response
The text was updated successfully, but these errors were encountered:
What is this about?
When running Detox tests with fixtures on the MetaMask app for Android, some Mac machines used by dev/QA users encounter issues. While the fixture server starts successfully, the app does not build into the required test state as expected for Android. This issue appears to be intermittent and only affects specific devices.
Steps to Reproduce
npm run test:e2e:android:debug:build
npm run test:e2e:android:debug:run
Expected Behavior
Tests that engage fixtures should start the app in the configured setup where the app opens at a specific spot, similar to the behavior on iOS.
Actual Behavior
The fixture server runs successfully, but the app's configuration setup is not engaged. Instead, the app starts from the beginning, ignoring the expected fixture configuration.
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References
No response
The text was updated successfully, but these errors were encountered: