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
We have a need to write out out results in nunit format for reporting purposes. I could overwrite the Base.print function and hide the current function, but I would rather reach out to see if there are plans to include this in the architecture of the project or if you would be willing to add a hook for this behavior as in:
function Base.print(io::IO, suite::TestSuite, writer::TestSuiteResultsWriter=nothing)
if writer ==nothing
writer =DefaultTestSuiteResultsWriter()
end
writer.write(io, suite)
end
This would mean that as a part of the facts function we would need a way of providing the writer, which could be an argument following the description.
The text was updated successfully, but these errors were encountered:
Another thing I found that I would like to address is the filename of the TestSuite is never set based on what I can see. I would like for this to be an optional argument to the facts function as well. This way the TestSuiteResultsWriter could do something with it if it desired and the print_header function would print this. My thoughts are the print_header function should be delegated to the writer so the writer has total control of the writing process. Thoughts??
We have a need to write out out results in nunit format for reporting purposes. I could overwrite the Base.print function and hide the current function, but I would rather reach out to see if there are plans to include this in the architecture of the project or if you would be willing to add a hook for this behavior as in:
This would mean that as a part of the facts function we would need a way of providing the writer, which could be an argument following the description.
The text was updated successfully, but these errors were encountered: