This is a subset of compatibility testing, however product (hardware, Software, OS, Browser, etc) will be certified as fit to use.
Clear Box Testing:
This is an alias for White box testing. Refer to White-Box Testing for more details.
Unit Testing (Black/White Box) performed using frameworks like JUnit, nUnit, xUnit, TestNG, DBUnit, HTTPUnit, etc. See Unit Testing, White-Box Testing and Black-Box Unit Testing also.
This is an analysis method that determines which parts of the software have been executed (covered) by the test cases and which parts are not executed that may require additional test cases for it.
The software is tested for comparison of features, pros and cons against the competitors’ products or different versions of the same product. This helps the Business Intelligence Team and Product Marketing Teams. See Benchmark Testing also.
This checks whether the software can be run on different hardware, operating systems, databases, webservers, application servers, bandwidth, hardware peripherals, emulators, processors, configurations and browsers (including different versions). Mostly, it is difficult to test on various combinations of H/W, OS, DBs and Browsers etc. To get the optimal coverage of different topologies, the Orthogonal Array Method is used. See Forward Compatibility Testing and Backward Compatibility Testing also.
This is a part of usability testing that ensures the software meets the required standards, government laws and regulations, company policies, etc. This is generally performed and certified by the external standards body or agencies. Sometimes testers also perform the testing and get certified from the external agencies. See Accessibility Testing also.
This is also a type of Unit Testing. This is carried out after completing unit testing. This test involves a group of units together as a whole rather. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.
This is a part of performance testing. Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
This is also called Condition/Decision coverage testing. This is a Unit Testing technique used to test all the condition and decision statements like if-then, if-then-else, switch-case, While, Do-While, For-Next, etc.
This is used as a part of performance testing for performance tuning by finding the optimal configuration settings that makes the software perform at its best for the given hardware / OS.
The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.
Context Driven Testing:
The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.
Testing of programs or procedures used to convert data from existing systems for use in replacement systems.