Open fatuhoku opened 11 years ago
Much of the existing test runner/reporter lives in Run.hs. We must tear apart logic that creates Doc
from putDoc
(which outputs it directly onto standard output). This would provide several extension points where Doc
s can be output. The need for this is most evident in the amount of functions in the IO monad
in that source file.
Is there more to this than alternative runners? test-framework already supports XML output as an alternative runner, for example.
The default output format is great; but it's not suitable for consumption by build management, reporting, or CI systems.
To make
test-framework
become a viable part of a software development pipleine, it's useful to support other formats of test result outputs.For instance, Mocha supports a vast range of variably useful reporters:
For instance, Mocha's![Mocha's spec reporter](http://visionmedia.github.com/mocha/images/reporter-spec-duration.png)
spec
reporter looks like this:This issue requires refactoring that would abstract from the way test progress and information is printed onto standard out at the moment into something more versatile.
Test reporters can have
test-framework
's current one, orprogress
bar): more suitable for development use in the terminalSome part of this is necessary for #38 to be implemented. It's questionnable whether this issue can become a part of the #38 altogether.