Issue#58 - Added TestSuiteResultsWriter with exported write function … #61
Conversation
…as a way to override how the results are output. Also made an allowance for the filename to be passed into the facts function, and updated the examples.jl with supporting examples
| end | ||
|
|
||
| function FactCheck.write(dummyWriter::DummyWriter, io::IO, suite::TestSuite) | ||
| n_succ = length(suite.successes) |
There was a problem hiding this comment.
These things should be removed as they are not used. I will remove them
|
How has the worked out for you locally? Were you able to implement your custom writer? |
|
Funny you mention that, I got pulled off onto something else. If I demonstrate a custom writer that fits our needs would that help move this forward in proving the concept out? If so I will certainly implement a NunitOutputWriter and send you the code. That exercise would be a lot of fun actually. Blessings |
|
Its just that I'm busy too, and working on a lot of other stuff (like my day job!). |
|
I totally get it and understand. I will work on the NUnit renderer and will either send you sample code or I can add it to a samples folder for reference in the next pull request. Thanks, |
…as a way to override how the results are output. Also made an allowance for the filename to be passed into the facts function, and updated the examples.jl with supporting examples