Moved to using unit-threaded for unit testing - Githubissues

BenjaminSchaaf / daffodil

A image processing library for D

MIT License

12 stars 3 forks source link

Moved to using unit-threaded for unit testing #26

Closed BenjaminSchaaf closed 8 years ago

BenjaminSchaaf commented 8 years ago

These changes replace the currently used micro-framework with unit-threaded, the popular D unit testing framework.

Benefits:

Uses standard unittest blocks with automatic discovery, so tests can still run without the framework
Once the number of tests starts growing, the threaded aspect of unit-threaded will improve performance (opt-out exists)
Specific tests can be run by themselves
Allows parameterized tests (though this requires using a function instead of a unittest block)
Allows marking tests as should fail
It means we're not also maintaining a testing framework

Downsides:

Adds a dependency (the first one), but only for development (and dub handles dependencies, so in development its a non-issue anyway)
Doesn't run templated tests, so some tests need to be converted (though I don't think they were running properly before either)
error reporting seems a little thin for unit-threaded atm
unit-threaded currently has a bug that stops it from compiling with this library (PR pending)