1 White box testing - In white box testing tests Are based on coverage of code statements, branches, paths, and conditions, it is purely based on knowledge of the internal logic of an application’s code.
2 Unit testing – Unit testing is typically done by the programmers and not by testers, as it requires detailed knowledge of the internal program design and code. It is the most ‘micro’ scale of testing; to test particular functions or code modules. It is not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
3 Incremental integration testing - It is done by programmers or by testers, continuous testing of an application as new functionality is added; requires that various aspects of an application’s functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed.
4 Integration testing – This type of testing is especially relevant to client/server and distributed systems, it involves testing of combined parts of an application to determine if they function together correctly. The ‘parts’ can be code modules, individual applications, client and server applications on a network, etc.
5 Functional testing – This is black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn’t mean that the programmers shouldn’t check that their code works before releasing it (which of course applies to any stage of testing.)
6 System testing – It covers all combined parts of a system, it is black-box type testing that is based on overall requirements specifications.
7 End-to-end testing - This type of testing is similar to system testing, IT is the ‘macro’ end of the test scale which involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
8 Sanity testing – It is typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort.
For example, if the new software is crashing systems every 10 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a ‘sane’ enough condition to warrant further testing in its current state.
9 Regression testing – Automated testing tools can be especially useful for this type of testing re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle..
10 Acceptance testing – final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.
11 Load testing – This involves testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.
12 Stress testing – Stress testing term is often used interchangeably with ‘load’ and ‘performance’ testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
13 Performance testing - Ideally ‘performance’ testing (and any other ‘type’ of testing) is defined in requirements documentation or QA or Test Plans, Performance testing term often used interchangeably with ‘stress’ and ‘load’ testing
14 Usability testing – This type of testing is done for ‘user-friendliness’. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.
15 Install/uninstall testing – testing of full, partial, or upgrade install/uninstall processes.
16 Recovery testing –This testing is done to check how well a system recovers from hardware failures, crashes, or other catastrophic problems.
17 Security testing – security testing is done to know how well the system protects against unauthorized internal or external access, willful damage, etc this may require sophisticated testing techniques.
18 Compatibility testing – This method is used for testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
19 Exploratory testing – often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
20 Ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.
21 User acceptance testing – This testing is done for determining if software is satisfactory to an end-user or customer.
22 Comparison testing – comparing software weaknesses and strengths to
23 Alpha testing – It is typically done by end-users or others, not by programmers or testers.It involves testing of an application when development is nearing completion, Minor design changes may still be made as a result of such testing.
24 Beta testing – testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.
25 Mutation testing – a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes (‘bugs’) and retesting with the original test data/cases to determine if the ‘bugs’ are detected. Proper implementation requires large computational resources.