Manual QA Testing Types

Image ©2025 ux-qa.com

Manual QA Testing Types

In manual QA testing, the types refer to what is being tested, like functional, non-functional, or user acceptance testing, while the levels focus on where the testing occurs within the overall software development process, such as unit, integration, or system testing.

Both types and levels are essential for ensuring that the application functions as expected, is free of defects, and provides an optimal user experience.

Manual QA testing involves human testers executing test cases without the use of automation tools. It’s often performed in the early stages of development or in cases where automation isn’t feasible. 

Functional Testing

Ensure that the application works according to the specified requirements.

Types

Smoke Testing

A basic, preliminary check to determine whether the most critical features of the application are working. If the smoke test passes, more detailed testing can proceed.

Sanity Testing

A more focused testing approach performed after receiving a new build or after changes are made, ensuring that the functionality is working as expected.

Regression Testing

Testing previously working functionality to ensure new changes (e.g., bug fixes, new features) haven’t broken anything.

Non-Functional Testing

Assess the application’s non-functional aspects, such as performance, usability, and security.

Types

Usability Testing

Evaluating the application from a user’s perspective, ensuring that it is intuitive, easy to navigate, and delivers a positive user experience.

Performance Testing

This measures the application's responsiveness, speed, stability, and scalability under different conditions (often using performance testing tools, though manual testing can be used to observe behaviors at lower scales).

Security Testing

Ensures that the application is free from vulnerabilities and is secure against potential security threats.

Exploratory Testing

Objective

Allows the tester to explore the application freely and learn about its behavior, while simultaneously identifying defects.

Details

This is less structured and more spontaneous. Testers are encouraged to think outside the box, perform ad-hoc testing, and test areas of the application that may not be covered by predefined test cases.

User Acceptance Testing (UAT)

Objective

Ensures that the software meets user requirements and is ready for deployment.

Details

UAT is performed by the client or end users to verify that the system satisfies business needs. 

The testing involves checking whether the system meets the specific use cases it was designed for.

Compatibility Testing

Checks how well the application works across different environments.

Types

Browser Compatibility Testing

Verifies that the application works across different web browsers (Chrome, Firefox, Safari, Edge).

Device Compatibility Testing

Checks how well the application performs on different devices (smartphones, tablets, etc.).

OS Compatibility Testing

Ensures the app functions properly on various operating systems (Windows, macOS, Linux).

Manual QA Testing Levels

Unit Testing

Objective

Validates the functionality of individual components or units of the software.

Details

Unit tests are automated by developers, but testers may also review or perform manual checks on individual functions or methods.

Integration Testing

Objective

Verifies that different components or systems work together correctly.

Details

After unit testing, integration testing ensures that the modules, once integrated, work as expected.

Manual integration testing typically involves checking interactions between different parts of the system.

System Testing

Objective

Ensures that the entire system works together as a whole.

Details

System testing is a complete end-to-end test of the application.

Testers validate that the entire system is functioning as intended and meeting the requirements defined in the specifications.

End-to-End Testing

Objective

Verifies that the flow of an application from start to finish behaves as expected, simulating real user scenarios.

Details

This type of testing ensures that the system’s components work together as expected.

Testers simulate the real user experience by performing tests that cover the entire application workflow.

Acceptance Testing

Objective

Validates whether the application meets the business requirements and if it is ready for release.

Details

Acceptance testing is typically performed at the client or user level.

The focus is on ensuring that the software behaves according to the requirements and that any issues identified are resolved before the product goes live.