To verify that users can successfully log into the application with various sets of credentials and handle different scenarios, such as valid and invalid inputs.
Steps to reproduce
Step 1
Action: Open the web browser and navigate to the login page of the application using the specified URL
Expected Result: The login page is displayed, showing fields for username, password, and a login button.
Step 2
Action: Input the provided username and password into the respective fields.
Expected Result: The credentials are entered correctly into the respective fields.
Step 3
Action: Click the “Login” button to submit the credentials
Expected Result: The application processes the login request.
Step 4
Action: Check if the user is redirected to the dashboard or the main page of the application
Expected Result: The user is successfully logged in and redirected to the correct page.
Step 5
Action: Record the outcome of the test case, noting whether the actual result matched the expected result.
Document any discrepancies or issues encountered
Expected Result: The test results are accurately logged, including any differences between the expected and actual outcomes.
Actual result
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Description
To verify that users can successfully log into the application with various sets of credentials and handle different scenarios, such as valid and invalid inputs.
Steps to reproduce
Step 1 Action: Open the web browser and navigate to the login page of the application using the specified URL Expected Result: The login page is displayed, showing fields for username, password, and a login button.
Step 2 Action: Input the provided username and password into the respective fields. Expected Result: The credentials are entered correctly into the respective fields.
Step 3 Action: Click the “Login” button to submit the credentials Expected Result: The application processes the login request.
Step 4 Action: Check if the user is redirected to the dashboard or the main page of the application Expected Result: The user is successfully logged in and redirected to the correct page.
Step 5 Action: Record the outcome of the test case, noting whether the actual result matched the expected result.
Document any discrepancies or issues encountered Expected Result: The test results are accurately logged, including any differences between the expected and actual outcomes.
Actual result
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Qase.io defect: Verify if the user is able to login to all app domains Found in test run: Express run 2024/09/05