This one is for those who like to follow the project more closely. Since v0.8.0 we’ve made a significant improvement to how D2TM is developed and delivered: automated testing. This allows us to further strengthen the codebase going forward 🚀
Automated unit tests
D2TM now has a unit testing framework in place, using Catch2. Tests run automatically after every build — locally and in CI — so regressions get caught early rather than discovered during play.
The first tests cover map geometry and a full suite of unit timers — the internal timers that drive unit behaviour like movement, attacking, harvesting, and idling. These are the kind of low-level things that are easy to break silently during refactoring, so having them covered matters.
This is just the beginning. The goal is to grow test coverage steadily as the codebase evolves.
Contributors
Mira established the testing policy and wrote the timer test suite. I set up the Catch2 framework, wired tests into the CI pipelines, and built the bleeding edge release system on GitHub Releases. We also used Claude Code to help track down issues and implement parts of this infrastructure.
No responses yet