Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: ProfileAndDeviceIdFragmentTest has order & machine-dependent behavior #5309

Closed
BenHenning opened this issue Jan 16, 2024 · 0 comments · Fixed by #5138
Closed

[BUG]: ProfileAndDeviceIdFragmentTest has order & machine-dependent behavior #5309

BenHenning opened this issue Jan 16, 2024 · 0 comments · Fixed by #5138
Assignees
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.

Comments

@BenHenning
Copy link
Sponsor Member

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

@BenHenning BenHenning added bug End user-perceivable behaviors which are not desirable. triage needed 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. labels Jan 16, 2024
@BenHenning BenHenning self-assigned this Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
2 participants