On Friday, 7 September 2018 at 19:15:21 UTC, Jonathan M Davis
wrote:
Honestly, I wouldn't rely on anything beyond dub build working
in a consistent manner across projects. As far as I can tell,
you can't actually do anything properly custom with dub test,
and I'm inclined to think that how it approaches things is
outright wrong.
For Dcompute I define a unittest configuration that has a main
that runs tests, and the (default) library configuration excludes
source files in the test directory. It seems to work fine.
Admittedly it is a little different to you usual package, and
there are no test specific symbols and no unit tests, and I
haven't tested anything that has dcompute as a dependancy.
Are you suggesting this will break users of Dcompute that run dub
test in their code? If so that truly does suck, because regular
unittests will not cut the mustard.
