Let us take an example of testing the login functionality in a product. A new login page has been introduced for the product and before releasing the feature, the team wants to test all the aspects of the feature and ensure smooth transition for the users. In such cases, the QA team needs to curate a proper test plan so that the new login page works as intended and the users do not undergo any struggle in accessing the product. The QA team can create a set of test cases within a folder.
Test Case: Login page
Objective: User should login to the product without any issues.
Preconditions: The user is on the login page.
Steps1: Navigate to the login page.
Expected result: The login page should open without throwing any error or UI issues
Step 2: Enter the user name.
Expected result: Check if the user name is valid and if invalid, the user should be prompted to enter a valid user name. If the valid user name is entered, prompt the user to enter a password.
Step 3: Enter a valid password.
Expected result: Check if the user entered a valid password. If the user has entered an invalid password, throw an error prompting the user to enter the right password. If the user has entered the right password, allow the user to click the 'Login' button.
Step 4: Click the Login button.
Expected result: When the user clicks the login button, the user should successfully log in and be redirected to their dashboard or landing page.
Test case: Invalid login attempt
Objective: Check how the system responds to incorrect login credentials
Preconditions: The user is on the login page.
Step 1: Navigate to the login page.
Expected result: Login page should load without any glitch or error.
Step 2: Enter a valid user name.
Expected result: User should be prompted to enter the password.
Step 3: Enter an incorrect password
Expected result: An error should throw up prompting user to enter the correct password and the user stays on the login page.
Test case: Password reset
Objective: Check if the password reset functionality doesn't break the login functionality.
Preconditions: The user is on the login page.
Step 1: Click the "Forgot Password" link
Expected result: Forgot Password button should be clickable. Another page should load asking for secondary level information to update a new password.
Step 2: Follow the instructions to reset the password
Expected result: Set of instructions should appear on-screen. User should be able to use any of the methods provided to retrieve the account.
Step 3: Log out of the account
Expected result: Once the user reset the password, the user will be logged in to the application. The user should now be able to log out of the account.
Step 4: Log back in using the original password
Expected Result: User should be able to login with the recently updated password through the password reset option.
Test Suite: All these test cases related to LOGIN can be added to a test suite, so that when a QA picks up the login related cases for test run, this suite can be chosen.