Manual Testing Process-Cleartrip
1. Requirement Analysis
Objective: Test the login functionality of the application to ensure users can log in with valid
credentials and are prevented from logging in with invalid credentials.
Requirements:
Users must be able to log in with a valid username and password.
Invalid credentials should show an error message.
The login page should have fields for username, password, and a login button.
2. Test Planning
Test Plan:
Test Objectives: Verify that users can log in with valid credentials and receive
appropriate error messages for invalid credentials.
Scope: This will include testing valid login, invalid login, and the error message display.
Resources: Testers, web browser (Chrome/Firefox), test environment (development or
staging server).
Schedule: 1 day for test planning and execution.
Test Strategy:
Test Types: Functional Testing
Test Levels: System Testing
3. Test Design
Test Cases:
1. Test Case 1: Valid Login
Test Case ID: TC001
Description: Verify that a user can log in with a valid username and password.
Preconditions: User has a valid username and password.
Test Steps:
1. Open the web application login page.
2. Enter the valid username.
3. Enter the valid password.
4. Click on the login button.
Expected Results: User is redirected to the homepage/dashboard.
2. Test Case 2: Invalid Login
Test Case ID: TC002
Description: Verify that an error message is displayed when an invalid username or
password is entered.
Preconditions: User has an invalid username or password.
Test Steps:
1. Open the web application login page.
2. Enter an invalid username.
3. Enter an invalid password.
4. Click on the login button.
Expected Results: An error message is displayed indicating invalid credentials.
Test Data:
Valid username: testuser
Valid password: password123
Invalid username: wronguser
Invalid password: wrongpass
4. Test Execution
Execution:
1. Test Case TC001:
Open the browser and navigate to the login page.
Enter testuser in the username field and password123 in the password field.
Click the login button.
Actual Results: Verify if you are redirected to the homepage/dashboard.
Status: Pass/Fail (Document any discrepancies).
2. Test Case TC002:
Open the browser and navigate to the login page.
Enter wronguser in the username field and wrongpass in the password field.
Click the login button.
Actual Results: Verify if an error message is displayed.
Status: Pass/Fail (Document any discrepancies).
Logging Defects:
If you encounter an issue where the application does not redirect correctly or fails to
display an error message, log a defect in your defect tracking system (e.g., JIRA). Include
details such as steps to reproduce, screenshots, and severity.
5. Test Reporting
Test Summary Report:
Test Cases Executed: 2
Test Cases Passed: 2
Test Cases Failed: 0
Defects Logged: 0
Defects Summary:
No defects found during this testing cycle.
Review and Sign-Off:
Present the test results to stakeholders and obtain their sign-off.
6. Post-Testing Activities
Conduct Retrospective:
What Worked Well: Clear steps and expected results made it easy to test and verify
functionality.
What Could Be Improved: Ensure test data is up-to-date and reflective of real-world
scenarios.
Update Test Artifacts:
Update test cases or data if there are any changes to the login functionality.
Perform Regression Testing:
If any new features or fixes are applied, re-run these tests to ensure no new issues are
introduced.
7. Closure
Finalize Documentation:
Ensure all test cases, defect logs, and reports are complete and archived.
Handoff:
Transition any relevant information to the development or deployment teams if
necessary.
