Showdown of the Asserts
summary
Compares plain JUnit and TestNG asserts with richer libraries and a Groovy alternative, finds AssertJ / Hamcrest for rich collection checks much clearer for nested maps and complex predicates, notes Truth is simpler but less chainable, flags Fest as effectively dead, and recommends Spock for data‑driven specs and table tests when Groovy is acceptable. Recommends sticking to one assertion style to avoid mixed argument orders, and using Tempus Fugit for concurrency and timing constraints in integration tests rather than ad‑hoc sleeps.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 4:00Running tests
- 8:25Test frameworks
- 11:50The original code
- 16:20The differences
- 18:00TesterG
- 18:40Impress
- 19:50Complex tests
- 22:30Shortchain
- 23:10Truth
- 25:45Spot
- 27:00Conclusion
- 29:10No maybe in tests
