Combine unit, integration, and performance tests so Clojure database code remains correct and operable.
This section bridges the chapter overview and the detailed lessons below. For Java engineers, the practical question is how to handle testing strategy for Clojure NoSQL work in Clojure code at the database boundary.
| Review focus | What to check |
|---|---|
| Unit tests | Prove pure data transformations cheaply. |
| Integration tests | Exercise real database assumptions where mocks are weak. |
| Performance tests | Catch query and serialization costs before release. |
Use the child lessons to move from concept to implementation. The section goal is to make the trade-off visible before the code hardens around a database assumption.