An integration test checks whether multiple software components work together as expected. It covers more code than a unit test and may use real dependencies, making it slower but providing broader confidence. section 6.6
Integration tests are useful when:
- Communication with databases, services, or other outside parties needs verification. section 6.5
- A macro-generated component must be checked from the outside rather than through implementation details. section 6.5
- Unit tests leave uncertainty about whether the connected parts behave correctly together. section 6.5
Testing a builder macro
A builder macro can be tested through its externally visible behavior, while integration-level tests check communication with external systems. Black-box tests are less sensitive to rearranged implementation details, though failures may require more investigation. section 6.9 section 6.5
