Browse

Manual Software Testing
Manual testing is carried out by a tester manually without the use of any kind of automation tool. It can identify visible and hidden defects. This kind of software testing often involves the testers trying the software from the perspective of the end-users. It is among the most fundamental testing processes, and the strategies can range from being fully scripted test cases to high-level guides for exploratory testing sessions.
For newly developed software, manual testing is mandatory before automated testing. Manual testing may require great effort and time, but the result will be bug-free software. Manual testers will require an understanding of manual testing techniques and need not have any automated testing skills. Several sophisticated tools are available but a simple and flexible one to try out is Testpad.
Are you preparing for job interviews? Check out the top Software Testing Interview Questions.
 
Automation Software Testing
Automation testing involves the use of special automation tools and requires a huge investment of money and resources. It is among the types of testing that aim to minimize manual test cases. Here, testers handle test scripts and return the result automatically. Test suites are recorded by using tools, and these can be played again by the testers as per the requirement. No human intervention is required for automation testing. Some popular automation tools are QTP/UFT and Selenium.
Check out the key differences between Manual Testing and Software Testing in our comparison guide, Manual Testing vs Automation testing.
 
Types of Manual Testing
There are three types of testing approaches:

White-box Testing
Black-box Testing
Grey-box Testing

White-box Testing
White-box testing is also known as structural testing, glass-box testing, transparent-box testing, or clear-box testing. This kind of testing is executed at the unit level and is based on the internal code structure. The test cases are designed based on the internal perspective of the system and programming skills such as code statements, conditions, branches, paths, etc.

Get 100% Hike!
Master Most in Demand Skills Now !





 






 



 

 

Black-box Testing
Black-box testing is also known as behavioral testing, specification-based testing, or input-output testing. It is a testing method where testers, without looking at the internal code structure, test the functionality of the software. The tests are based on the requirements and functionality alone. The internal system design is not taken into consideration.
Black-box testing is again divided into two different types of testing: Functional Testing and Non-Functional Testing.
Functional Testing
Functional testing focuses only on the output to verify the functionality of the software and how it fares against the specified requirements. This testing does not involve looking at the actual code. Each function is given a value, and then, the output is determined and verified with the expected value.
Types of Functional Testing
Function Testing has three types of testing viz- unit testing, integration testing, and system testing.

Unit Testing

Unit testing involves a developer separately testing each and every unit of an application. Each source code module is tested in the developer’s environment. This testing is also known as module testing or component testing. Unit testing reduces the cost of bug fixes since the diagnosis is done at an early phase of the development life cycle.

Integration Testing

Integration testing, also known as I&T testing or string testing, involves the testing of the connectivity or transfer of data between unit-tested modules. This type of testing includes the top-down approach, the bottom-up approach, and the sandwich approach.
Integration testing is divided into Incremental Integration Testing and Non-Incremental Integration Testing.

Incremental Integration Testing: Incremental integration testing is a form of testing in which a module is tested before being merged with another module. The integration is then tested before adding another module or component.
Non-Incremental Integration Testing/ Big Bang Method: For integrated testing, this non-incremental technique is referred to as a big band approach. Non-incremental integration, in which all components are merged ahead of time and the complete programme is tested, is sometimes attempted.


System Testing

Also known as end-to-end system testing (E2E testing) is a type of black-box testing that is done on a fully integrated application. Every input in the application is thoroughly verified for the desired output. System testing is the testing of a user’s experiences with the application.
Invest in your dream to become a professional tester, and take up this Selenium Certification by Intellipaat.
Non-functional Testing
Every organization has a separate team for this kind of testing called the non-functional testing (NFT) team or the performance team. Here, the testing is done for non-functional parameters such as stress testing, load testing, recovery testing, volume, security, accountability, etc. These parameters are, however, never tested without first executing functional testing. The main objective is to know whether the software’s response time is as per the requirement as it plays a crucial role in customer satisfaction.
Non-functional Testing Types
1. Performance Testing: Performance testing examines the functionality of software components. These tests uncover flaws in software architecture and design.
2. Usability Testing: Non-functional testing includes usability testing as one of the testing methods. Usability testing is all about ensuring that the software is simple to use for consumers.
3. Compatibility Testing: Customer satisfaction is ensured by compatibility testing, which is also non-functional testing. Its purpose is to see if your software program or product can run in a variety of browsers, databases, hardware, operating systems, mobile devices, and networks.
Grey-box Testing
Grey-box testing, as you may have already guessed, is the combination of both white-box and black-box testing. The testers will have access to design documents and internal coding for the purpose of designing test cases. The testing process here is executed at a functionality level.
Grey-box testing is good at diagnosing context-specific errors of web systems and pays attention to all the layers of any complex system. This helps increase testing coverage. Grey-box testing is primarily implemented in penetration testing and integration testing.