mirror of
https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC.git
synced 2024-11-22 05:41:00 +02:00
More active voice
parent
88425a6be5
commit
ed958ed85f
@ -15,38 +15,38 @@ ___
|
||||
 3. The user puts the ID card against the smartphone.
|
||||
|
||||
**Expected results:**
|
||||
 Personal information is retrieved from the ID card.
|
||||
 The system notifies the user that the data has been retrieved from the ID card.
|
||||
 The full name and the personal identification number of the card’s owner is displayed.
|
||||
 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 card’s owner.
|
||||
___
|
||||
**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 was not able to establish connection with an ID card.
|
||||
 The system notifies that ID card was not detected.
|
||||
 The user is back on the home screen of the application.
|
||||
 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 application’s home screen.
|
||||
___
|
||||
**Extension test:** Invalid CAN entered
|
||||
 1. ...
|
||||
 2. The user enters an invalid CAN (for example 000000).
|
||||
 3. The user puts the ID card against the smartphone.
|
||||
 2. User enters an 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 system notifies the user that the CAN was invalid.
|
||||
 The user is returned to the application’s home screen.
|
||||
 The application notifies the user that the CAN was invalid.
|
||||
 The application returns the user to the application’s home screen.
|
||||
___
|
||||
_Currently not working! More details in release notes._
|
||||
_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.
|
||||
|
||||
**Expected results:**
|
||||
 The connection between the ID card and smart card was lost.
|
||||
 Connection between the ID card and device is lost.
|
||||
 The system notifies the user that connection to the ID card was lost.
|
||||
 The user is returned to the application’s home screen.
|
||||
 The application returns the user to the application’s home screen.
|
||||
|
||||
# **Test Case #2**
|
||||
**Use Case being tested:**
|
||||
@ -61,16 +61,16 @@ ___
|
||||
 2. The user enters the valid CAN.
|
||||
|
||||
**Expected results:**
|
||||
 The system notifies the user that the CAN has been saved.
|
||||
 The CAN is saved and displayed to the user.
|
||||
 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 an invalid CAN (for example 000000).
|
||||
|
||||
**Expected results:**
|
||||
 The system notifies the user that the CAN was invalid.
|
||||
 The user is returned to the application’s home screen.
|
||||
 The application notifies the user that the CAN was invalid.
|
||||
 The application returns the user to the application’s home screen.
|
||||
|
||||
# **Test Case #3**
|
||||
**Use Case being tested:**
|
||||
@ -86,20 +86,20 @@ ___
|
||||
 1. The user touches a fingerprint sensor on the device.
|
||||
|
||||
**Expected results:**
|
||||
 The fingerprint is detected and the application enters PIN1 for the user automatically.
|
||||
 The system detects the fingerprint and the application enters PIN1 for the user automatically.
|
||||
___
|
||||
**Extension test:** Device's biometric authentication functionality is inaccessible
|
||||
|
||||
**Expected results:**
|
||||
 The system notifies the user that biometric authentication is currently unavailable.
|
||||
 The user is asked to enter PIN1 manually.
|
||||
 The application asks to enter PIN1 manually.
|
||||
___
|
||||
**Extension test:** Invalid fingerprint
|
||||
 1. ...
|
||||
|
||||
**Expected results:**
|
||||
 The system notifies the user that biometric authentication has failed due to a non-matching fingerprint.
|
||||
 The user is asked to enter PIN1 manually.
|
||||
 The application asks to enter PIN1 manually.
|
||||
___
|
||||
**Extension test:** Invalid PIN1
|
||||
**Initial system state:**
|
||||
@ -108,9 +108,9 @@ The user has saved an invalid PIN1 to the biometric authentication method.
|
||||
 1. ...
|
||||
|
||||
**Expected results:**
|
||||
 The system notifies the user that biometric authentication has failed, because the saved PIN1 is invalid.
|
||||
 The authentication process is cancelled.
|
||||
 Biometric authentication mode is automatically turned off by the application 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.
|
||||
 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:**
|
||||
@ -125,7 +125,7 @@ ___
|
||||
 1. The user does nothing.
|
||||
|
||||
**Expected results:**
|
||||
 The authentication application is closed.
|
||||
 The authentication application closes.
|
||||
___
|
||||
**Extension test:** The authentication application fails to close
|
||||
 1. ...
|
||||
@ -143,7 +143,7 @@ The PIN1 of an ID card
|
||||
A valid Estonian ID card with an NFC interface
|
||||
**Initial system state:**
|
||||
The user has the authentication application installed on the mobile phone.
|
||||
NFC technology is enabled on the user’s device and the user has given the authentication application permission to use the NFC adapter.
|
||||
NFC technology is enabled on the user’s device and user has given the authentication application permission to use the NFC adapter.
|
||||
A website that supports logging in with the authentication application is active in the device’s web browser.
|
||||
___
|
||||
**Main success scenario test:**
|
||||
@ -153,14 +153,14 @@ ___
|
||||
 4. User puts the ID card against the device in the 90 second time window.
|
||||
|
||||
**Expected results:**
|
||||
 The authentication application is closed.
|
||||
 The authentication application closes.
|
||||
 The website should inform the user that it has received the necessary information.
|
||||
___
|
||||
**Extension test:** The authentication application is not found
|
||||
 1. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user should be informed that the authentication app could not be found.
|
||||
 The system should inform the user that the authentication app could not be found.
|
||||
___
|
||||
**Extension test:** User fails to put the ID card against the device in time
|
||||
 3. ...
|
||||
@ -174,7 +174,7 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The authentication process is cancelled and the user is directed back to the website.
|
||||
 The application cancels the authentication process and directs the user back to the website.
|
||||
___
|
||||
**Extension test:** Non-matching CAN
|
||||
 1. ...
|
||||
@ -182,8 +182,8 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user is notified that the CAN provided was incorrect.
|
||||
 The authentication process is cancelled and the user is directed back to the website.
|
||||
 The application notifies the user that the CAN provided was incorrect.
|
||||
 The application cancels the authentication process and directs the user back to the website.
|
||||
___
|
||||
**Extension test:** Invalid PIN1
|
||||
 2. ...
|
||||
@ -191,8 +191,8 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user is notified that the PIN1 provided was incorrect.
|
||||
 The authentication process is cancelled and the user is directed back to the website.
|
||||
 The application notifies the user that the PIN1 provided was incorrect.
|
||||
 The application cancels the authentication process and directs the user back to the website.
|
||||
|
||||
# **Test Case #6**
|
||||
**Use Case being tested:**
|
||||
@ -210,14 +210,14 @@ ___
|
||||
 4. User puts the ID card against the device.
|
||||
|
||||
**Expected results:**
|
||||
 The authentication application is closed.
|
||||
 The authentication application closes.
|
||||
 The website should inform the user that it has received the necessary information.
|
||||
___
|
||||
**Extension test:** The authentication application is not found
|
||||
 1. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user should be informed that the authentication app could not be found.
|
||||
 The system should inform the user that the authentication app could not be found.
|
||||
___
|
||||
**Extension test:** User fails to put the ID card against the device in time
|
||||
 3. ...
|
||||
@ -231,7 +231,7 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The authentication process is cancelled and the user is directed back to the website.
|
||||
 The application cancels the authentication process and directs the user back to the website.
|
||||
___
|
||||
**Extension test:** Invalid PIN2
|
||||
 2. ...
|
||||
@ -239,8 +239,8 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user is notified that the PIN2 provided was incorrect.
|
||||
 The authentication process is cancelled and the user is directed back to the website.
|
||||
 The application notifies the user that the PIN2 provided was incorrect.
|
||||
 The application cancels the authentication process and directs the user back to the website.
|
||||
|
||||
# **Test Case #7**
|
||||
**Use Case being tested:**
|
||||
@ -258,10 +258,10 @@ ___
|
||||
 1. The user selects the authentication application as a means for logging in.
|
||||
 2. The authentication application opens and the user enters the CAN of the ID card if prompted.
|
||||
 3. User enters PIN1 of the ID card.
|
||||
 4. The user puts the ID card against the smartphone.
|
||||
 4. User puts the ID card against the smartphone.
|
||||
|
||||
**Expected results:**
|
||||
 The authentication application is closed.
|
||||
 The authentication application closes.
|
||||
 The requesting application should inform the user that it has received the necessary information.
|
||||
___
|
||||
**Extension test:** The authentication application is not found
|
||||
@ -282,7 +282,7 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The authentication process is cancelled and the user is directed back to the requesting application.
|
||||
 The application cancels the authentication process and directs the user back to the requesting application.
|
||||
___
|
||||
**Extension test:** Non-matching CAN
|
||||
 1. ...
|
||||
@ -290,8 +290,8 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user is notified that the CAN provided was incorrect.
|
||||
 The authentication process is cancelled and the user is returned to the requesting application.
|
||||
 The application notifies the user that the CAN provided was incorrect.
|
||||
 The application cancels the authentication process and directs the user back to the requesting application.
|
||||
___
|
||||
**Extension test:** Invalid PIN1
|
||||
 2. ...
|
||||
@ -299,8 +299,8 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user is notified that the PIN1 provided was incorrect.
|
||||
 The authentication process is cancelled and the user is directed back to the requesting application.
|
||||
 The application notifies the user that the PIN1 provided was incorrect.
|
||||
 The application cancels the authentication process and directs the user back to the requesting application.
|
||||
|
||||
# **Test Case #8**
|
||||
**Use Case being tested:**
|
||||
@ -317,14 +317,14 @@ ___
|
||||
 4. User puts the ID card against the device.
|
||||
|
||||
**Expected results:**
|
||||
 The authentication application is closed.
|
||||
 The authentication application closes.
|
||||
 The requesting application should inform the user that it has received the necessary information.
|
||||
___
|
||||
**Extension test:** The authentication application is not found
|
||||
 1. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user should be informed that the authentication app could not be found.
|
||||
 The system should inform the user that the authentication app could not be found.
|
||||
___
|
||||
**Extension test:** User fails to put the ID card against the device in time
|
||||
 3. ...
|
||||
@ -332,13 +332,13 @@ ___
|
||||
|
||||
**Expected results:**
|
||||
 The authentication application cancels the authentication process and closes.
|
||||
 The user is returned to the requesting application.
|
||||
 The system returns the user to the requesting application.
|
||||
___
|
||||
**Extension test:** Information exchange between the device and ID card fails
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The authentication process is cancelled and the user is directed back to the requesting application.
|
||||
 The application cancels the authentication process and directs the user back to the requesting application.
|
||||
___
|
||||
**Extension test:** Invalid PIN2
|
||||
 2. ...
|
||||
@ -346,5 +346,5 @@ ___
|
||||
 4. ...
|
||||
|
||||
**Expected results:**
|
||||
 The user is notified that the PIN2 provided was incorrect.
|
||||
 The authentication process is cancelled and the user is directed back to the requesting application.
|
||||
 The application notifies the user that the PIN2 provided was incorrect.
|
||||
 The application cancels the authentication process and directs the user back to the requesting application.
|
||||
|
Loading…
Reference in New Issue
Block a user