Updated Test reports (markdown)

Lemmo Lavonen 2021-12-07 00:04:05 +02:00
parent 3f7e515f08
commit fed6157fcc

@ -18,4 +18,8 @@
|---|---|**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 test app.|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 test app.|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|
|---|---|**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|
### Non-functional requirements measurements
1. USN9 - the application opens in under a second
1. USN10 - the website receives the token in well under 15 seconds