Where do integration or system tests go in TDD?

Sometimes, it’s good to create a test that brings together multiple components and confirms that the overall system being built works as expected. These are called integration tests because they integrate multiple components to make sure they work well together. Or, the tests can be called system tests because they test the entire system. The two names are mostly interchangeable with each other.

For our microservice developer who is the target customer of the logging library, there will likely be unit tests for an individual service, and even unit tests for various classes and functions inside the service. Some of the tests for a particular service might even be called integration tests, but usually, an integration test will be working with multiple services. The services should work together to accomplish something bigger. So, having tests that make sure the overall results can be reached will help improve the reliability and...