As somebody who tests their packages with both std/unittest (for snorlogue, nimword and tinypool) and testament I agree that some TLC is needed, mostly on the docs front for testament in my eyes.
However, I'd note that the docs are present and understandable and I'm saying my statement more in the sense that testament could use an expansive tutorial that dives into every feature in detail as it packs quite a punch in what it can do. Honestly, std/unittest (I assume unittest2 acts identical) was pretty trivial to get going though. Just 2 examples: <https://github.com/PhilippMDoerner/TinyPool/blob/master/tests/tSqlitePool.nim> <https://github.com/PhilippMDoerner/nimword/blob/main/tests/t_pbkdf2_sha256.nim> And you can run however many examples you want with this simply via running `nimble test` (<https://github.com/nim-lang/nimble#tests>) . Glimpsing through unittest2 though, they also have it in their docs on how to run all your tests: <https://github.com/status-im/nim-unittest2/#testing-unittest2> So while on the rest I'll agree, at least the unittest part is pretty covered.
