This content originally appeared on DEV Community and was authored by Ashika kandasamy
MANUAL TESTING
In manual testing a tester tests the software application and give final report about that application. In this testing, testers create test cases and test the software application to make sure functions and features of an application are working as expected (as per the requirement).
TYPES OF MANUAL TESTING
WHITE BOX TESTING
White box testing is also known as Glass box testing, Transparent testing. This testing is done by the development team and they review the coding line by line to check whether the functionalities are working and meet the specific requirements.
It verifies the internal workings of a software application. It checks that every aspect of the code is tested, basically is focusing on the logic, structure, and flow of the software.
UNIT TESTING
Unit testing is performed by the developers themselves. They test individual functions or components to ensure they work as expected. Developers use junit, pytest, nunit or testing to perform unit testing.
WHITE BOX TESTING TECHNIQUES
To achieve complete code coverage, white box testing uses the following techniques.
Statement coverage – It covers each and every statement in the code. It helps to determine the faulty section of the code. Every node must be traversed at least once
Branch coverage – In this approach all the branch from every decision point in the source code is covered and tested.
Condition coverage – It covers all the conditions in the source code.
Multiple Condition coverage – In this technique, all the possible combinations of the possible outcomes are tested at least once.
Path coverage (Cyclomatic complexity) – It checks all the possible execution paths in the program to ensure that the functions are behaving as expected.
Input and output coverage – This help to confirm that the software produces the required results under different input condition.
Loop testing – Loops are widely used and they need to be tested to ensure all the loops are working as expected.
Advantages/pros
• Transparency of the internal coding structure which is helpful in deriving the type of input data needed to test an application effectively.
• Test cases can be easily automated.
• It helps in identification of defects in early stage.
Disadvantages/cons
• updated test scripts required when the implementation is changing too often.
• It becomes complex for large size project.
• Necessity to create full range of inputs to test each path and condition make the white box testing method time-consuming.
BLACK BOX TESTING
In this testing tester is unaware of internal working of the software and focuses mainly on verifying if its features and functionalities are working as per user requirements.
Note: Tester does not know internal knowledge or implementation details.
TYPES OF BLACK BOX TESTING
FUNCTIONAL TESTING
Functional testing ensures that the requirements and specifications are properly satisfied by the application. It focuses on the simulation of actual system usage but does not develop any system structure assumptions.
TYPES OF FUNCTIONAL TESTING
SMOKE TESTING
Smoke testing determines whether the employed build is stable or not. It acts as a configuration of whether the quality assurance team can proceed with further testing. They are also known as confidence testing or build verification testing.
SANITY TESTING
Sanity testing is performed to ensure that the code changes that are made are working properly. This testing process is to validate the functionality of the application and not detailed testing.
REGRESSION TESTING
Regression testing involves re-executing a previously created test cases to verify that recent code changes haven’t caused new issues. This verifies that updates, bug fixes or enhancements do not break the functionality of the application.
Regression testing can be performed in different ways, such as:
Retesting – Checking the entire application or specific features that were affected by the changes.
Re-execution – Running previously tested cases to make sure everything still functions properly.
Comparison – Comparing the latest version of the software with an older version to ensure no features are broken.
RE-TESTING
Retesting is a procedure where we need to check that particular test cases that are found with some bugs during the execution time. retesting also occurs when the product is already tested and due to some problems, it needs to be tested again.
INTEGRATION TESTING
Integration testing focuses on verifying the interactions and data exchange between different components or modules of a software application. The main purpose is to identify any problems or bugs that raise when different components are combined and interacted with each other. Once all the modules have been unit-tested, integration testing is performed.
Big-Bang Integration testing – It is the simplest integration testing approach, all the modules of the system are simply put together and tested.
Bottom-Up Integration testing – In bottom-up testing, each module at the lower levels are tested with higher modules until all the modules are tested.
Top-Down Integration testing – Testing takes place from top to bottom. First high-level modules are tested and then low-level modules and finally integrating the low-level modules to a high level to ensure the system is working as expected.
Mixed Integration testing – Mixed integration testing is also known as sandwiched integration testing. It is a combination of top down and bottom up testing approaches.
SYSTEM TESTING (end to end testing)
It involves a tester with internal knowledge of the software to inspect code, architecture and integrations to ensure the entire system functions correctly and effectively.
LOCALIZATION TESTING
In globalized world, businesses need to make sure their software, websites and apps are suitable for users in different regions and cultures.
GLOBALIZATION TESTING
Globalization testing is a type of software testing that is performed to ensure the system or software application can function independently of geographical and cultural environment.
EXPLORATORY TESTING
In exploratory testing tester use their learning, knowledge, skills and abilities to test the software developed by themselves. It combines the experience of testers with a structured approach to testing.
USER ACCEPTANCE TESTING(UAT)
Software is tested in a real-world scenario by end to end to ensure it meets their requirements and functionalities as expected. UAT focus on validating the software’s user-friendliness, functionality and performance from the user’s perspective.
Acceptance criteria
• Completeness
• Accuracy
• User-friendliness
• Performance
• Reliability
• Security
• Scalability
• Compatibility
Advantages
• Functional testing ensures the delivery of a bug free and high quality of product.
• It ensures that all the requirements are met and ensures that the customer is satisfied.
• Functional testing ensures proper working of application.
Disadvantages
• Limited scope – it does not cover performance, security and usability testing.
• Incomplete code path coverage.
• Inability to guarantee readiness
NON-FUNCTIONAL TESTING
Non-functional testing helps to verify the non-functional requirements of the application. It verifies the behavior of the application is as per the requirement or not.
Here are the non-functional types
PERORMANCE TESTING
It is a testing technique carried to determine system performance in terms of sensitivity, reactivity and stability under a particular workload. It aims to measure system performance under various loads and conditions and ensure that the system can handle the expected number of users or transactions.
Load testing
It helps to determine the maximum number of users or transactions the system can handle. It checks the ability to perform under anticipated user loads.
Stress testing
It is a type of load testing that tests the system’s ability to handle high load above normal usage levels. It helps to identify the breaking point of the system and any potential issues that may occur under heavy load conditions.
Volume testing
A large number of data is saved in a database and the overall software system’s behavior is observed.
Endurance testing
It focuses on the long-term behavior of the system under a constant load. It is performed to ensure the software can handle the expected load over a long period.
Scalability testing
It helps in planning capacity additions to software application.
SECUGRITY TESTING
It uncovers vulnerability in the system and determine that the data and resources of the application are protected from possible intruders.
USABILITY TESTING
This testing is done from an end user to determine that the applicatio6 is easily usable. usability testing involves evaluating the functionality of a website, app or digital product by observing real user as they navigate through it.
Advantages
• Less time consuming in comparison to other testing process.
• Improves user experience.
• More secured since it includes security testing.
Disadvantages
• Non-functional tests are performed repeatedly.it is more resource intensive.
• Not cost effective.
GRAY BOX TESTING
It combines elements of black box and white box testing techniques.
To improve over all product quality and also to reduce the overhead of longer process of functional and non-functional
BOUNDAGRY VALUE ANALYSIS
BVA is a black box testing technique where test cases are designed using boundary values. It checks for the input values near the boundary that have a higher chance of error. Every partition has its maximum and minimum values.
• Minimum value
• Just above the minimum value
• Nominal value
• Just below max value
• Max value
Example:
91-100 -> S grade
81-90 -> A grade
71-80 -> B grade
61-70 -> C grade
51-60 -> D grade
45-50 -> E grade
0-44 -> U grade
Final values are
91-100 -> S grade (92)
81-90 -> A grade (89)
71-80 -> B grade (72)
61-70 -> C grade (69)
51-60 -> D grade (51)
45-50 -> E grade (45)
0-44 -> U grade (0)
Negative scenario
91-100 -> S grade (101)
0-44 -> U grade (-1)
DECISION TABLE TESTING
Decision tables are used in various fields to represent complex logical relationships. The output may be dependent on many input conditions and decision tables combinations of input conditions and they are in form of true or false.
Example:
The Future of Manual testing in the age of AI
AI quality assurance have made great progress, they can analyze vast amount of data, identify pattern and generate test cases much faster and very accurate. This eventually reduces testers effort reduce the timing and improve performance. Even though AI tools excel in handling structured and predictable scenarios but may struggle with complex, ambiguous or subjective aspects of testing.
Manual testing remains crucial even in the age of AI
• Manual testing brings different perspective and skill set.
• They possess domain knowledge, critical thinking abilities and problem-solving skills.
• Testers can also validate the output of AI driven testing.
To thrive the age of AI driven quality assurance, manual testers must adapt and expand their skills. Continuous learning with AI technologies and also need to have better knowledge on its pros and cons.
This content originally appeared on DEV Community and was authored by Ashika kandasamy
Ashika kandasamy | Sciencx (2025-09-16T13:35:33+00:00) The future of manual testing in the age of AI. Retrieved from https://www.scien.cx/2025/09/16/the-future-of-manual-testing-in-the-age-of-ai/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.