-
Notifications
You must be signed in to change notification settings - Fork 20
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
Sync Report screen with wrong data when come back from the background - FIXED #272
Sync Report screen with wrong data when come back from the background - FIXED #272
Conversation
3e66b32
to
126ab6f
Compare
126ab6f
to
d3a1ca5
Compare
@zancas @fluidvanadium @Oscar-Pepper this is ready for review, I test it, Oscar as well. Thanks in advance. |
66c5873
to
b4b0eb1
Compare
It seems to me that this needs a new e2e test demonstrating that the bug is fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fluidvanadium can we add an e2e test, showing that this bug is fixed?
b4b0eb1
to
abb1cd1
Compare
So this is blocked on test? I really hope we can get it tested and landed before our release! |
i am testing again now in emulator... maybe this will be good enough for merge? an e2e would have to be thorough as the bug doesn't always show up so i think manual testing will give us more confidence. an e2e test would still be very valuable though because it would still catch it (eventually) going forward |
i have tested thoroughly in emulator on two different AVDs and there is no sign of the bug. i think we are good to merge |
Is it difficult to write an e2e test? The difference between having an e2e test and not is our awareness about this bug in the future. I believe that this bug is not present now, because of the manual testing. But.. I assume we're going to change the codebase.. right? So tomorrow, when the codebase is different, what evidence do we have that the bug is still fixed? |
65c67b1
to
3664fc4
Compare
The test is in place! Resultado del test: PASS e2e/sync_report.test.js (76.748 s) Done in 79.04s. |
Awesome! I think @fluidvanadium or @Oscar-Pepper or someone with more intimate knowledge of |
New execution of the test: C:\Users\juank\github\zingo-mobile-juanky\android>yarn detox test sync_report -c android.emu.debug PASS e2e/sync_report.test.js (83.651 s) Done in 86.24s. |
Finally I did catch this issue. Now when you come back from background to foreground if you was in the report screen, when the server start the sync again, you can see the correct info.
@Oscar-Pepper if you can test it in your local would be fantastic, since you are who reported it.