arti/Estonian-ID-card-mobile-authenticator-POC
1
0
Fork 0
mirror of https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC.git synced 2024-11-22 13:51:00 +02:00
Code Packages Releases Wiki Activity

Updated Test reports (markdown)

Lemmo Lavonen 2021-12-06 23:33:13 +02:00
parent 532d4cac41
commit d9c346ee87
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Test-reports.md

@ -8,14 +8,14 @@
|TC #5|UC #8|**Success scenario test:** The user launches the application from the website. The user provides the required inputs and holds their ID card against the phone when requested.|After the app finishes reading the card and closes, the user is taken back to the website where the successful login attempt is confirmed.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user tries to launch the application when it's not installed.|Nothing happens.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the website. The user lets the 90 second period for placing the ID card against the phone expire.|The application closes and user is returned to the website|Application did not close, returned to the home screen instead.|No|Can not reproduce.|
|---|---|**Extension test:** The user performs all the same steps as in the main success scenario, except for removing the card from the phone as soon as it's detected.|Application notifies the user of the issue and returns them to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the website. The application does not have the CAN saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns them to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the website. The application does not have the PIN1 saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns them to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user performs all the same steps as in the main success scenario, except for removing the card from the phone as soon as it's detected.|Application notifies the user of the issue and returns to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the website. The application does not have the CAN saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the website. The application does not have the PIN1 saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns to the website.|Expected result|No|Fixing not needed|
|TC #7|UC #10|**Success scenario test:** The user launches the application from the test app. The user provides the required inputs and holds their ID card against the phone when requested.|After the app finishes reading the card and closes, the user is taken back to the test app, where the successful login attempt is confirmed.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user tries to launch the application when it's not installed.|Nothing happens.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the website. The user lets the 90 second period for placing the ID card against the phone expire.|The application closes and user is returned to the website|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user performs all the same steps as in the main success scenario, except for removing the card from the phone as soon as it's detected.|Application notifies the user of the issue and returns them to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the test app. The application does not have the CAN saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns them to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the test app. The application does not have the PIN1 saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns them to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user performs all the same steps as in the main success scenario, except for removing the card from the phone as soon as it's detected.|Application notifies the user of the issue and returns to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the test app. The application does not have the CAN saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns to the website.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user launches the application from the test app. The application does not have the PIN1 saved, and when it requests it, the user enters an invalid one.|Application notifies the user of the issue and returns to the website.|Expected result|No|Fixing not needed|
|TC #9|UC #12|**Success scenario test:** The user launches the application and goes to the settings screen. The user opts to add PIN1, enters a number between 4 and 12 digits long, and chooses to continue.|The application notifies the user that PIN1 was saved.|Expected result|No|Fixing not needed|
|---|---|**Extension test:** The user follows the same steps as in the success scenario, but enters a number that's either less than 4 or more than 12 digits long.|The user is notified of the incorrect length and is unable to save the PIN.|Expected result|No|Fixing not needed|