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-25 15:20:59 +02:00
Code Packages Releases Wiki Activity

Document UC tests for UC7-11

Kevin 2021-10-17 15:41:20 +03:00
parent f72883e0bd
commit 4240837c4c
1 changed files with 297 additions and 61 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

344
Use-Case-Tests.md

@ -1,53 +1,52 @@
_NB! Notation info: ... in the extension test cases means that the steps up to this point are same as in the main success scenario test case._
_NB! Notation info: ... in the extension test cases means that steps up to this point are same as in the main success scenario test._
# **Test Case #1**
**Use Case being tested:**
[Use Case #5](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-5) : Displaying the public information of the ID card in the authentication application
**Inputs:**
A valid Estonian ID card with a NFC interface
A valid Estonian ID card with an NFC interface
The CAN (Card Authentication Number) of the ID card
**Initial system state:**
The application’s home screen is opened.
The NFC connection is enabled on the smartphone and the system has permission to use it.
The application’s 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.
4. The user clicks to see the results.
 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.
**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.
 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.
___
**Extension test: ID card not detected**
    2. ...
    3. The user does not put the ID card against the phone during the next 90 seconds.
**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 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.
___
**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.
**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.
**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 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.
___
_Currently not working! More details in release notes._
**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.
**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.
    The system notifies the user that connection to the ID card was lost.
    The user is returned to the application’s home screen.
 The connection between the ID card and smart card was lost.
 The system notifies the user that connection to the ID card was lost.
 The user is returned to the application’s home screen.
# **Test Case #2**
**Use Case being tested:**
@ -55,23 +54,23 @@ _Currently not working! More details in release notes._
**Inputs:**
The CAN (Card Authentication Number) of an ID card
**Initial system state:**
The application’s home screen is opened.
The application’s home screen is active.
___
**Main success scenario test:**
1. The user opens the app's settings and chooses to save the CAN of the ID card.
2. The user enters the valid CAN.
 1. The user opens the app's settings and chooses to save the CAN of the ID card.
 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 system notifies the user that the CAN has been saved.
 The CAN is saved and displayed to the user.
___
**Extension test: Invalid CAN entered**
1. ...
2. The user enters an invalid CAN (for example 000000).
**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 system notifies the user that the CAN was invalid.
 The user is returned to the application’s home screen.
# **Test Case #3**
**Use Case being tested:**
@ -84,31 +83,268 @@ The user has saved a valid PIN 1 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.
 1. The user touches a fingerprint sensor on the device.
**Expected results:**
    The fingerprint is detected and the application enters PIN 1 for the user automatically.
 The fingerprint is detected 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 user is asked to enter PIN 1 manually.
 The system notifies the user that biometric authentication is currently unavailable.
 The user is asked 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 user is asked to enter PIN 1 manually.
 The system notifies the user that biometric authentication has failed due to a non-matching fingerprint.
 The user is asked to enter PIN1 manually.
___
**Extension test: Invalid PIN 1**
**Extension test:** Invalid PIN1
**Initial system state:**
The user has saved an invalid PIN1 to the biometric authentication method.
1. ...
 1. ...
**Expected results:**
    The system notifies the user that biometric authentication has failed, because the saved PIN 1 is invalid.
    The authentication process is cancelled.
    Biometric authentication mode is automatically turned off by the application in the settings until a new PIN 1 is saved to this feature in order to avoid future use of this feature with an invalid PIN 1.
 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.
# **Test Case #4**
**Use Case being tested:**
[Use Case #7](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-7) : Application automatically closes itself at the end of the authentication process
**Inputs:**
\-
**Initial system state:**
The authentication application has been started by an intent coming from another application.
Necessary information has already been retrieved from the ID card.
___
**Main success scenario test:**
 1. The user does nothing.
**Expected results:**
 The authentication application is closed.
___
**Extension test:** The authentication application fails to close
 1. ...
**Expected results:**
 The application remains active.
 The user can click on a button to exit the app.
# **Test Case #5**
**Use Case being tested:**
[Use Case #8](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-8) : Using the authentication application to log into a website
**Inputs:**
The CAN (Card Authentication Number) of an ID card
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.
A website that supports logging in with the authentication application is active in the device’s web browser.
___
**Main success scenario test:**
 1. The user selects the authentication application option as a method 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. User puts the ID card against the device in the 90 second time window.
**Expected results:**
 The authentication application is closed.
 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.
___
**Extension test:** User fails to put the ID card against the device in time
 3. ...
 4. The user does nothing.
**Expected results:**
 The authentication application cancels the authentication process and closes.
 The user is returned to the website.
___
**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 website.
___
**Extension test:** Non-matching CAN
 1. ...
 2. The authentication application opens and the user enters a CAN that does not match the CAN of the ID card.
 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.
___
**Extension test:** Invalid PIN1
 2. ...
 3. User enters a PIN that does not match the PIN1 of the ID card.
 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.
# **Test Case #6**
**Use Case being tested:**
[Use Case #9](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-9) : Using the authentication application to give a signature on a website
**Inputs:**
The PIN2 of an ID card
A valid Estonian ID card with an NFC interface
**Initial system state:**
The user is logged in to a website using the authentication application.
___
**Main success scenario test:**
 1. The user starts a process that requires a signature on the website.
 2. The authentication application opens and the user enters the CAN of the ID card if prompted.
 3. User enters a valid PIN2.
 4. User puts the ID card against the device.
**Expected results:**
 The authentication application is closed.
 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.
___
**Extension test:** User fails to put the ID card against the device in time
 3. ...
 4. The user does nothing.
**Expected results:**
 The authentication application cancels the authentication process and closes.
 The user is returned to the website.
___
**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 website.
___
**Extension test:** Invalid PIN2
 2. ...
 3. User enters a PIN that does not match the PIN2 of the ID card.
 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.
# **Test Case #7**
**Use Case being tested:**
[Use Case #10](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-10) : Using the authentication application to log into an application running on the same device
**Inputs:**
The PIN1 of an ID card
The CAN (Card Authentication Number) of the ID card
A valid Estonian ID card with an NFC interface
**Initial system state:**
The user has the authentication application installed on the device.
NFC technology is enabled on the user’s device and the user has given the authentication application permission to use the NFC adapter.
An application that supports logging in with the authentication application is active.
___
**Main success scenario test:**
 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.
**Expected results:**
 The authentication application is closed.
 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.
___
**Extension test:** User fails to put the ID card against the device in time
 3. ...
 4. The user does nothing.
**Expected results:**
 The authentication application cancels the authentication process and closes.
 The user is returned 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.
___
**Extension test:** Non-matching CAN
 1. ...
 2. The authentication application opens and the user enters a CAN that does not match the CAN of the ID card.
 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.
___
**Extension test:** Invalid PIN1
 2. ...
 3. User enters a PIN that does not match the PIN1 of the ID card.
 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.
# **Test Case #8**
**Use Case being tested:**
[Use Case #11](https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC/wiki/Use-Cases#use-case-11) : Using the authentication application to provide a signature to another application
**Inputs:**
The PIN2 of an ID card
**Initial system state:**
The requesting application is active.
___
**Main success scenario test:**
 1. The user starts a process that requires a signature in the requesting application.
 2. The authentication application opens and the user enters the CAN of the ID card if prompted.
 3. User enters a valid PIN2.
 4. User puts the ID card against the device.
**Expected results:**
 The authentication application is closed.
 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.
___
**Extension test:** User fails to put the ID card against the device in time
 3. ...
 4. The user does nothing.
**Expected results:**
 The authentication application cancels the authentication process and closes.
 The user is returned 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.
___
**Extension test:** Invalid PIN2
 2. ...
 3. User enters a PIN that does not match the PIN2 of the ID card.
 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.