[BUG]: ProfileAndDeviceIdFragmentTest has order & machine-dependent behavior #5309
Labels
bug
End user-perceivable behaviors which are not desirable.
Impact: Low
Low perceived user impact (e.g. edge cases).
Work: Medium
The means to find the solution is clear, but it isn't at good-first-issue level yet.
Describe the bug
When running certain tests in isolation within ProfileAndDeviceIdFragmentTest, a variety of order-independence issues arise causing difficulty in test behavior isolation. Additionally, there are proto comparisons happening that can have subtle differences depending on the local runtime environment.
Steps To Reproduce
Run each of the tests in ProfileAndDeviceIdFragmentTest in isolation and notice different failures.
Expected Behavior
All tests in ProfileAndDeviceIdFragmentTest should not have an order dependence, and should work in all runtime environments.
Note that some of these issues are caused by #5307 and #5304, but the proto behavior is specific to this test.
Screenshots/Videos
No response
What device/emulator are you using?
N/A -- test environment
Which Android version is your device/emulator running?
N/A -- test environment
Which version of the Oppia Android app are you using?
N/A -- test environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: