1. Manual Testing: Manual testing incorporates testing programming physically, i.e., without utilizing any computerization apparatus or any content. In this sort, the analyzer assumes control over the job of an end-client and tests the product to distinguish any startling way of behaving or bug. There are various stages for manual testing, for example, unit testing, coordination testing, framework testing, and client acknowledgment testing.
Analyzers use test plans, experiments, or test situations to test programming to guarantee the fulfillment of testing. Manual testing likewise incorporates exploratory testing, as analyzers investigate the product to distinguish mistakes in it.
2. Mechanization Testing: Computerization testing, which is otherwise called Test Robotization, is the point at which the analyzer composes scripts and uses one more programming to test the item. This interaction includes the computerization of a manual cycle. Robotization Testing is utilized to re-run the test situations rapidly and over and over, that were performed physically in manual testing.
- Functional testing: This type of testing is focused on verifying the software's functionality against the requirements or specifications to ensure that it meets the end user's expectations.
- Performance testing: Performance testing is focused on evaluating the system's performance under a specific workload or stress level to determine how well it can handle various types of loads.
- Security testing: Security testing is focused on identifying and mitigating potential security vulnerabilities in the software or system to ensure that it is secure and resistant to attacks.
- Usability testing: Usability testing is focused on evaluating the software's user interface and user experience to determine how easy it is for users to use and navigate the software.
- Integration testing: Integration testing is focused on verifying the interactions between different components or modules of the software to ensure that they work together seamlessly.
- Regression testing: Regression testing is focused on testing the software after changes or updates to ensure that the changes have not introduced any new defects or issues.
- Acceptance testing: Acceptance testing is focused on verifying that the software meets the end user's requirements and is ready for deployment.
- Compatibility testing: Compatibility testing is focused on ensuring that the software works correctly on different platforms, browsers, and operating systems.
- Exploratory testing: Exploratory testing is a type of testing where testers explore the software without any specific plan to uncover any unexpected issues or defects.