Here are some common types of manual testing without the use of automated tools or programming skills:
- Unit Testing:
- Description: Testing individual components or modules of a system to ensure they function correctly.
- Description: Testing individual components or modules of a system to ensure they function correctly.
- Integration Testing:
- Description: Testing the combination of different components or systems to ensure they work together seamlessly.
- Description: Testing the combination of different components or systems to ensure they work together seamlessly.
- System Testing:
- Description: Evaluating the complete and integrated software system to ensure it meets specified requirements.
- Description: Evaluating the complete and integrated software system to ensure it meets specified requirements.
- Acceptance Testing:
- Description: Verifying if the system meets the acceptance criteria and is ready for release.
- Types:
- User Acceptance Testing (UAT): Testing performed by end-users to validate if the system meets their requirements.
- Business Acceptance Testing (BAT): Ensuring that the software meets business objectives.
- Regression Testing:
- Description: Verifying that new changes to the software haven’t negatively impacted existing functionality.
- Description: Verifying that new changes to the software haven’t negatively impacted existing functionality.
- Smoke Testing:
- Description: A preliminary test to check if the major functionalities of the software work without detailed testing.
- Description: A preliminary test to check if the major functionalities of the software work without detailed testing.
- Exploratory Testing:
- Description: Simultaneous learning, test design, and execution. Testers explore the application, learn its features, and design test cases on the fly.
- Description: Simultaneous learning, test design, and execution. Testers explore the application, learn its features, and design test cases on the fly.
- Ad Hoc Testing:
- Description: Informal testing without predefined test cases. Identifying defects that might not be found in scripted testing.
- Description: Informal testing without predefined test cases. Identifying defects that might not be found in scripted testing.
- Usability Testing:
- Description: Evaluating the user-friendliness and overall user experience of the software. Assessing the interface, navigation, and overall usability.
- Description: Evaluating the user-friendliness and overall user experience of the software. Assessing the interface, navigation, and overall usability.
- Security Testing:
- Description: Evaluating the system to identify vulnerabilities and ensure data protection.
- Description: Evaluating the system to identify vulnerabilities and ensure data protection.
- Compatibility Testing:
- Description: Verifying if the software is compatible with different environments, devices, and browsers.
- Description: Verifying if the software is compatible with different environments, devices, and browsers.
- Performance Testing:
- Description: Assessing how well the system performs under different conditions, such as high loads or stress. Analyzing response times, throughput, and resource usage.
- Description: Assessing how well the system performs under different conditions, such as high loads or stress. Analyzing response times, throughput, and resource usage.
- Accessibility Testing and 508 compliance:
- Description: A type of testing that evaluates a software application’s usability by individuals with disabilities, ensuring that it can be used and accessed by people of all abilities. Examining the application’s compatibility with assistive technologies, verifying the use of alternative text for images, ensuring keyboard navigation, and validating the overall adherence to accessibility standards and guidelines (e.g., WCAG – Web Content Accessibility Guidelines).