QuestionQ3
VerifiedTest Analysis and Test DesignYou are designing test cases based on this use case:
Use case: logging in to the online banking system
- The user opens the banking application.
- The system displays the login page.
- The user enters their username and password.
- The user clicks the “Login” button.
- The system verifies the username and password in the database.
- The system starts the multi-factor authentication (MFA) procedure.
- The user undergoes MFA verification.
- The system logs the user in and redirects them to the welcome screen.
Alternative flows:
- 3A: The user clicks the “Forgot Password” button. The system sends an e-mail containing a link to reset the password and returns to step 2.
- 5A: Incorrect password. The system displays the message “Incorrect password”, and, after the user closes the message window, returns to step 3.
Exceptions:
- 2A: The system is unavailable because of maintenance work. The system displays the message “Maintenance work in progress; try later” and the login process ends.
- 7A: MFA verification error. The system displays the message “MFA verification failed” and the login process ends.
The test strategy requires coverage of the main scenario, alternative flows, and exceptions for each use case. The strategy permits testing multiple alternative flows in one test case. Each exception must be tested in a separate test case, although a test case can contain alternative flows.
What is the MINIMUM number of test cases that achieves this coverage?
Community Discussion