There are many other testing terms and types that have not been covered in the 21 previous slides. This includes areas such as Gorilla testing, which is testing that has multiple people pound on (work on) the same testing area in an exhaustive manner. There is also Agile testing, which simply integrates the testing as part of the overall integrated process of building a solution.
There is also paired testing, which is the process of having two people work together when testing. Paired testing can be two developers, a developer and a business person, or any other combination of two people. The idea of paired testing is that two people looking and testing together can better identify issues better than one.
Black box testing focuses on testing the functionality of an area of a solution without worrying about the internals of how the unit is accomplishing a task. White box testing, on the other hand focuses on the inner workings of an application rather than the overall functionality that black box tests cover. White box testing can include testing code coverage, data flow, branching, decision trees, statements, and more. Then, there is gray box testing, which combines the black and white testing approaches.
Other testing methods not mentioned include boundary testing, sanity testing, smoke testing, and more. Many of these have similarities to what has already been covered.
Clearly, there are a lot of testing approaches as well as types of tests. Developers need to make sure they are applying the right testing to the solutions they are doing. On that note, how many of these testing strategies do you use regularly?