A few things about where this guy is wrong on the definitions. For testing there are: Unit Tests - This is usually per method and on a disconnected basis (you

A few things about where this guy is wrong on the definitions. For testing there are: Unit Tests - This is usually per method and on a disconnected basis (you don't have a direct call to a resource on this) Integrations - this is a combination of other unit tests. May use stubs and or mocks to isolate the external resources involved. Functional/feature- This is where you get embedded services involved Product acceptance test - This tends to test the individual application from deployment to running. This tends to verify outward features with live resources behind it. (Pipeline - it's one piece of the pipeline running live) System test - this is where you can get live test environments setup and prepped for it. This tends to test the system as a whole (Pipeline- it's the entire pipeline in a test environment) Usual definitions are: Smoke test - a briefer test of the System test.. but meant to prove out things work. Doesn't verify