by Javatpoint
Manual testing is the process of testing software manually to identify defects. In this presentation, we'll cover the basics of manual testing, its advantages, challenges, types, test cases, reporting bugs, and conclusion.
1
Manual testing is the process of testing software manually without any automation tools to check if it meets the requirements and specifications.
2
Manual testing helps to ensure software quality by identifying defects that might have been missed during automated testing. It also enables testers to gain domain knowledge and understand the end-user perspective.
3
Manual testing can be timeconsuming, expensive, and prone to errors. It also requires skilled testers with a thorough understanding of the software and testing techniques.
Flexibility
Manual testing allows testers to use their creativity and intuition to identify defects that automated tools might miss.
Economical
Manual testing is more cost-effective compared to automated testing as it doesn't require additional tools or scripts to test the software.
User-Friendly
Manual testing is more user-friendly as it can identify defects that could affect the end-user experience. It also allows testers to provide feedback on the software's usability.
Comprehensive
Manual testing allows for ad-hoc and exploratory testing, which can identify defects that were not considered in the initial test plan.
Manual testing can be time-consuming and requires testers to manage their time efficiently to meet deadlines.
Manual testing requires testers to have a thorough understanding of the software and testing techniques to identify defects.
Manual testing involves communication between testers, developers, and stakeholders to ensure all requirements are met.
This type of testing ensures that the software functions according to the requirements specified in the functional specification document.
This type of testing ensures that changes made to the software do not adversely affect existing software functionalities.
This type of testing ensures that the software meets the end-user's expectations and requirements.
This type of testing ensures that the different modules or components of the software are integrated correctly and function correctly together.
Test Case Title
• Test Case Steps:
• Expected Result:
• Actual Result:
• Pass/Fail:
Sample Test Case 1
• Test Case Steps: Open the application and verify the login screen.
• Expected Result: The login screen should open without any errors.
• Actual Result: The login screen opened successfully.
• Pass/Fail: Pass
Sample Test Case 2
• Test Case Steps: Enter an invalid username and password and click on the login button.
• Expected Result: The user should be prompted to enter valid credentials.
• Actual Result: The user was prompted to enter valid credentials.
• Pass/Fail: Pass
1 Identify the Bug
2 Describe the Bug
The second step is to describe the bug in detail, including the steps to reproduce it, the expected and actual results, the severity, and any additional information.
The first step is to identify the bug and reproduce it on the software.
3 Report the Bug
The final step is to report the bug to the relevant team or stakeholders via an issue tracking platform or email.
Manual testing is an important part of software testing that ensures software quality and user satisfaction. It comes with its advantages and challenges, and it requires skilled testers to identify defects that automated tools might miss.
Thank You!
We hope this presentation was informative and engaging.
Please feel free to ask any questions or provide your feedback.