Extending unittests [proposal] [Proof Of Concept]
Johannes Pfau
nospam at example.com
Thu Sep 20 10:37:22 PDT 2012
Am Thu, 20 Sep 2012 19:27:00 +0200
schrieb "Jesse Phillips" <Jessekphillips+D at gmail.com>:
>
> I didn't read everything in your post, where does the FAILURE
> show up. If it is intermixed with the SUCCESS, then I could see
> that as a problem.
>
> While I can't say I've hated/liked the lack of output for
> unittest success, I believe my feeling would be the same with
> this.
That's just an example output. We could leave the druntime
test runner as is and don't change the output at all. We could only
print the failure messages. Or we could collect all failures and print
them at the end. All that can easily be changed in druntime (and
I'd argue we should enhance the druntime interface, so everyone could
implement a custom test runner), but we need the compiler changes to
allow this.
In the end, you have an array of UnitTests (ordered as they appear in
the source file). A UnitTest has a filename, line number and a function
member(the actual unittest function). What you do with this is
completely up to you.
More information about the Digitalmars-d
mailing list