Updated Use Case Tests (markdown)

Henrik Lepson 2021-12-06 19:55:27 +02:00
parent 23a66c4686
commit 68fc8b52d1

@ -10,35 +10,25 @@ The applications home screen is active.
The NFC connection is enabled on the device and the system has permission to use it.
___
**Main success scenario test:**
 1. The user starts the process to read information from the ID card.
 2. The user enters the valid CAN.
 3. The user puts the ID card against the smartphone.
 1. The user saves CAN if it is not saved already.
 2. The user puts the ID card against the smartphone.
**Expected results:**
 The system retrieves personal information from the ID card.
 The application notifies the user that data has been retrieved from the ID card.
 The application displays the full name and personal identification number of the cards owner.
 The application displays the full name, personal identification number, gender, expiration date of the ID card and citizenship of the card holder.
___
**Extension test:** ID card not detected
 2. ...
 3. The user does not put the ID card against the phone during the next 90 seconds.
**Expected results:**
 The system is not able to establish connection with an ID card.
 The application notifies the user that ID card was not detected.
 The application returns the user to the applications home screen.
___
**Extension test:** Invalid CAN entered
**Extension test:** Invalid CAN used
 1. ...
 2. User enters an invalid CAN (for example 000000).
 2. User saves invalid CAN (for example 000000).
 3. User puts the ID card against the smartphone.
**Expected results:**
 The system is unable to retrieve information from the ID card.
 The application notifies the user that the CAN was invalid.
 The application returns the user to the applications home screen.
 The application notifies the user that the saved CAN was invalid.
 The application deletes the saved CAN.
___
_A corresponding error message is currently not displayed, is implemented in branch MOB-24._
**Extension test:** ID card removed from the smartphone before allowed
 2. ...
 3. The user puts the ID card against the smartphone and removes it immediately.
@ -46,7 +36,7 @@ _A corresponding error message is currently not displayed, is implemented in bra
**Expected results:**
 Connection between the ID card and device is lost.
 The system notifies the user that connection to the ID card was lost.
 The application returns the user to the applications home screen.
 The application allows the user to try again.
# **Test Case #2**
**Use Case being tested:**
@ -64,52 +54,47 @@ ___
 The application notifies the user that the CAN has been saved and displays it.
 The CAN is saved.
___
**Extension test:** Invalid CAN entered
 1. ...
 2. The user enters a CAN that has an invalid length (for example 00000).
**No extensions**
**Expected results:**
 The application notifies the user that the entered CAN is invalid.
# **Test Case #3**
**Use Case being tested:**
[Use Case #6](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-6) : Use biometric authentication to enter PIN1 during the authentication process
**Inputs:**
A fine finger
**Initial system state:**
The user has enabled biometric authentication in the applications settings.
The user has saved a valid PIN1 to the biometric authentication method.
The application has launched to authenticate the user and the user is shown a biometric authentication dialog.
# **~~Test Case #3~~**
**~~Use Case being tested:~~**
~~[Use Case #6](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-6) : Use biometric authentication to enter PIN1 during the authentication process~~
~~**Inputs:**~~
~~A fine finger~~
~~**Initial system state:**~~
~~The user has enabled biometric authentication in the applications settings.~~
~~The user has saved a valid PIN1 to the biometric authentication method.~~
~~The application has launched to authenticate the user and the user is shown a biometric authentication dialog.~~
___
**Main success scenario test:**
 1. The user touches a fingerprint sensor on the device.
~~**Main success scenario test:**~~
~~ 1. The user touches a fingerprint sensor on the device.~~
**Expected results:**
 The system detects the fingerprint and the application enters PIN1 for the user automatically.
~~**Expected results:**~~
~~ The system detects the fingerprint and the application enters PIN1 for the user automatically.~~
___
**Extension test:** Device's biometric authentication functionality is inaccessible
~~**Extension test:** Device's biometric authentication functionality is inaccessible~~
**Expected results:**
 The system notifies the user that biometric authentication is currently unavailable.
 The application asks to enter PIN1 manually.
~~**Expected results:**~~
~~ The system notifies the user that biometric authentication is currently unavailable.~~
~~ The application asks to enter PIN1 manually.~~
___
**Extension test:** Invalid fingerprint
 1. ...
~~**Extension test:** Invalid fingerprint~~
~~ 1. ...~~
**Expected results:**
 The system notifies the user that biometric authentication has failed due to a non-matching fingerprint.
 The application asks to enter PIN1 manually.
~~**Expected results:**~~
~~ The system notifies the user that biometric authentication has failed due to a non-matching fingerprint.~~
~~ The application asks to enter PIN1 manually.~~
___
**Extension test:** Invalid PIN1
**Initial system state:**
The user has saved an invalid PIN1 to the biometric authentication method.
~~**Extension test:** Invalid PIN1~~
~~**Initial system state:**~~
~~The user has saved an invalid PIN1 to the biometric authentication method.~~
 1. ...
~~ 1. ...~~
**Expected results:**
 The application notifies the user that biometric authentication has failed, because the saved PIN1 is invalid.
 The application cancels the authentication process.
 The application turns off biometric authentication mode in the settings until a new PIN1 is saved to this feature in order to avoid future use of this feature with an invalid PIN1.
~~**Expected results:**~~
~~ The application notifies the user that biometric authentication has failed, because the saved PIN1 is invalid.~~
~~ The application cancels the authentication process.~~
~~ The application turns off biometric authentication mode in the settings until a new PIN1 is saved to this feature in order to avoid future use of this feature with an invalid PIN1.~~
# **Test Case #4**
**Use Case being tested:**