On Thursday, 1 May 2014 at 12:17:56 UTC, Ary Borenszweig wrote:
On 5/1/14, 6:58 AM, Jacob Carlborg wrote:
On 2014-04-30 22:11, Russel Winder via Digitalmars-d wrote:
This cannot be a good idea. If the block says unittest then
it contains
unit tests, not integration tests or system tests, just unit
tests.
Then we need to come up with a separate framework for doing
all other
kinds of tests.
Yes. And then you need two different commands to check if the
system works. And if you want, for example, coverage analysis I
wonder how you'd do that... That can't be good.
Two commands effectively. `rdmd -unittest` for development cycle
of single module and `make test` to verify everything after
feature/bugfix is completed. This is what I tend to do with
existing tools (by splitting higher level tests in separate
applications), adding some in-language support will just make
intention a bit more clear.
