Black box testing: This is the testing in which the application or the ‘test object’ is tested for its reliability, robustness and performance to specifications. The person(s) testing the software program need not be conversant with programming in general or with the programming language used for the software development. Not only at the system and the unit levels of software, but this testing can also be done at the level of functional, integration and acceptance levels. Both functional and non functional coding is performed to assess the stability and the responsiveness of the program. Both valid and invalid bits of input are used to determine whether the output that is being generated is correct or not. The internal structure of the application is not the subject of the testing in the black box testing and the tester(s) need not be concerned with the internal structure or quality of the program. The black box testing takes on various forms like decision table testing, state transition tables, boundary value analysis well as equivalence partitioning.
White box testing: This kind of testing is also known as clear box testing or structural testing. Unlike the black box testing, the object of this testing is not concerned with the functional aspect of software. The main focus of white box testing is the quality of the software programming. It is frequently carried out at the unit level of software although it can also be carried out at the system and integration levels. This testing might take the form of path testing, data flow testing, branch testing and control flow testing. Programming standards and best practices need to be followed when developing software and white box testing tries to discover whether these aspects have been taken care of. It is usually carried out as part of SDLC.
Manual testing: This is a testing technique in which all aspects of the software interface need to be examined and checked for performance and stability by a person. It needs a human tester working without the aid of any testing tools. It is the most cumbersome and time consuming process, especially if the application is complex and involves checking of many buttons, tabs, links and windows. However, it is the best testing technique that gives an understanding of a software interface from the perspective of the end user. Different groups of individuals might manually test different modules of a program to check the quality of application development.
Regression Testing: This kind of testing checks whether the performance or other issues reported during one version of a software are resolved in a subsequent version. Although this testing technique can be carried out manually, it is recommended that testers choose an automated testing solution or package for easy and quick testing.
Stress Testing: Stress testing examines the performance of a system for its stability at or outside its limits or processing capacity. The primary objective of stress testing is to check whether the software development team has ensured that it will systematically and swiftly scale down its active state and preserve all vital links to its environment and cease; ready to be re-invoked afresh, without terminating unstably or collapsing.