Re:Observations on the testing culture of test-driven develo...
by malkia on Wednesday August 15, 2018 @02:16AM
(#17764080)
My understandings are:
Unit test: tests single function/class, uses fake or mocked data to test for expectations. Test coverage can be used to find spots missed in testing.
Integration test: test two or more things in isolation - interaction between two classes, functions, etc. OR more than one system (say micro-service) communicating with another. The rest of the systems are fake/mock or fetch/replay golden data.
Unit test should take milliseconds to execute.
I'm not actually sure what acceptance test would be?
Unit test: tests single function/class, uses fake or mocked data to test for expectations. Test coverage can be used to find spots missed in testing.
Integration test: test two or more things in isolation - interaction between two classes, functions, etc. OR more than one system (say micro-service) communicating with another. The rest of the systems are fake/mock or fetch/replay golden data.
Unit test should take milliseconds to execute.
I'm not actually sure what acceptance test would be?