I need to explain the testing terminology to others because I want everyone to be on the same page; have the same understanding. After continuous study of the testing world for over more than a month, I am coming to the conclusion that terminology in the testing world is nothing more than the wild west; do what you want to do and make up whatever testing terminology you desire. This is, to put it mildly, is frustrating.
I thought I finally figured out a way to understand all testing terminology ... successfully fit all the pieces of the puzzle together. Using a matrix. An analogy to this matrix would be a matrix of dog breeds; where x-axis (or y-axis) represents the name of the dog breed and the other axis lists characteristics which define that dog breed. So for example, Smoke test is a dog breed ... a characteristic would be that it is a type of functional testing, and by it's definition, it is also of type regression ... smoke test can be done on UI, API, or back-end area, it can either be testing acceptance or system requirements.
I want this way of understanding the different testing to be correct. This is the best way I have found to understand the testing world. The matrix helps you to ensure that you have covered every combination of testing.
How Correct is this matrix? The amount of testing terminology in the testing world is mind boggling, overwhelming. It seems like the testing world is being made more complex than it needs to be because of lack of agreement on terminology making newcomers life worse than it needs to be. Collaboration would be greatly greatly appreciated.
[Testing classification matrix]: The header row for this table (smoke , sanity, security ...) are just a few examples of what could be on the top row. The Blue columns is supposed to successfully cover any imaginable type of test possible under the sun (nothing is left out ... everything falls under one or more of the blue categories).
REASON FOR TRYING TO ORGANIZE TESTING TYPES:
Ensure full gamut of testing is carried out to ensure full coverage. My initial thought/hope was that research within the testing world had been done on how to arrive at best testing process which best covers and protects the code and was hoping that a starting place would be by ensuring you are not leaving out any type of testing and to ensure the proper team is conducting the testing.
After putting together this matrix, I did find other documentation attempting to show a comprehensive understanding of the testing types very similar to the matrix which I put together.