You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
$ mocha --reporters
dot - dot matrix
doc - html documentation
spec - hierarchical spec list
json - single json object
progress - progress bar
list - spec-style listing
tap - test-anything-protocol
landing - unicode landing strip
xunit - xunit reportert
teamcity - teamcity ci support ***
html-cov - HTML test coverage
json-cov - JSON test coverage
min - minimal reporter (great with --watch)
json-stream - newline delimited json events
markdown - markdown documentation (github flavour)
nyan - nyan cat!
For instance, Mocha's 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
streaming output (like test-framework's current one, or progress bar): more suitable for development use in the terminal
holistic (like the single JSON object that gets spit out right at the end): more suitable for consumption by other build processes.
Some part of this is necessary for #38 to be implemented. It's questionnable whether this issue can become a part of the #38 altogether.
The text was updated successfully, but these errors were encountered:
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 Docs can be output. The need for this is most evident in the amount of functions in the IO monad in that source file.
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
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.
The text was updated successfully, but these errors were encountered: