Skip to content
This repository was archived by the owner on Jun 20, 2023. It is now read-only.

Fix navigation after test scanning (EXPOSUREAPP-12985) #5408

Merged
merged 36 commits into from
Aug 16, 2022

Conversation

SamuraiKek
Copy link
Contributor

@SamuraiKek SamuraiKek commented Aug 2, 2022

Ticket

Scan pending/positive/negative pcr/rat test from the certificates/check-in/journal tabs.
Go through the submission process and you should land on the same tab from where you opened the universal scanner.
For positive tests, canceling the submission process before it's finished will also land you on the tab from where you opened the universal scanner.

The navigation through the submission flow needed to be changed more extensively to match figma and iOS.

When scanning a test (or registaring it through TAN), every operation throughout the submission flow needs to end where the flow was started with the exception of scanning and TAN registering from the dispatcher screen, in which case, the flow should always end on the home fragment.

What to test:

Scan a new PCR/RAT certificate starting from:

  1. Status Tab
  2. Certificates Tab
  3. Check-In tab
  4. Journal Tab
  5. Manage Your Tests screen

All types of tests must be tested: negative; pending; invalid and positive
For positive tests, canceling the registration, not entering symptoms/warning others and interrupting the flow in general, should always land you on the screen from where the scanning was started.
- also try the os back navigation while registering a positive test
- also try going through the positive test registration with and without giving consent

Try replacing the tests with new ones -> you should go through all/most steps above, especially the positive test registration flow with and without consent.

Try restoring an already deleted test -> again pay attention to positive test registrations, especially ones where the consent was not given and/or others weren't warned.

Try restoring an already deleted test while having a registered test already in the app so that the restored certificate will replace the current one and you have to go through the test deletion screen.

Try registering a test with a TAN.

Try replacing an already registered test by registering a new one with a TAN.

Figma

P.S. I don't know what to do about detekt's LongParameterList error. The params are part of the constructor, can we supress this error somehow?

@SamuraiKek SamuraiKek added bug Something isn't working maintainers Tag pull requests created by maintainers labels Aug 2, 2022
@SamuraiKek SamuraiKek added this to the 2.26.x milestone Aug 2, 2022
@SamuraiKek SamuraiKek requested a review from a team August 2, 2022 10:21
@github-actions
Copy link

github-actions bot commented Aug 2, 2022

Unit Test Results - Device Release

   560 files     560 suites   6m 2s ⏱️
2 779 tests 2 779 ✔️ 0 💤 0
2 828 runs  2 828 ✔️ 0 💤 0

Results for commit 3929db6.

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Aug 2, 2022

Unit Test Results - Device For Tester Release

   563 files     563 suites   6m 4s ⏱️
2 785 tests 2 785 ✔️ 0 💤 0
2 834 runs  2 834 ✔️ 0 💤 0

Results for commit 3929db6.

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Aug 2, 2022

Firebase Test Results

    2 files  +    2      2 suites  +2   4m 35s ⏱️ + 4m 35s
129 tests +129  129 ✔️ +129  0 💤 ±0  0 ±0 
258 runs  +258  258 ✔️ +258  0 💤 ±0  0 ±0 

Results for commit 3929db6. ± Comparison against base commit a1cb83c.

♻️ This comment has been updated with latest results.

@chiljamgossow chiljamgossow self-assigned this Aug 2, 2022
@SamuraiKek SamuraiKek requested a review from a team August 10, 2022 12:19
@SamuraiKek
Copy link
Contributor Author

While testing for another bug I noticed: When I use the TAN flow and choose No on the symptoms introduction screen I go back to the test result screen, from where sharing fails as it has happened already. Can you check?

Just popping the back stack on the thank you screen is not sufficient. the back stack needs to be cleared when navigating to the thank you screen

I've found the issue and pushed a fix. I've also found a missing dialog which I've added now.

@mtwalli mtwalli modified the milestones: 2.26.x, 2.27.x Aug 11, 2022
@mtwalli mtwalli changed the base branch from release/2.26.x to release/2.27.x August 11, 2022 12:19
chiljamgossow
chiljamgossow previously approved these changes Aug 15, 2022
Copy link
Contributor

@mtwalli mtwalli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mtwalli mtwalli self-assigned this Aug 15, 2022
chiljamgossow
chiljamgossow previously approved these changes Aug 16, 2022
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

7.5% 7.5% Coverage
0.0% 0.0% Duplication

@mtwalli mtwalli merged commit eccc675 into release/2.27.x Aug 16, 2022
@mtwalli mtwalli deleted the fix/12985-navigation-after-test-registration branch August 16, 2022 17:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working maintainers Tag pull requests created by maintainers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants