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
Going along with one of the stated goals of marbles
write richer tests that expose more information on test failure to help you debug failing tests faster
The audience for reading such test results can be expanded by adding HTML reporting as an option in addition to current stdout reporting.
What I have in mind is something along the lines of report formatting provided by the HtmlTestRunner project which uses Jinja2 and Bootstrap under the hood.
HTML unittest reports can be saved to disk for historical auditing, or written to /tmp for one time or temporary viewing (default setting).
Basic HTML output screenshot
The text was updated successfully, but these errors were encountered:
Going along with one of the stated goals of marbles
write richer tests that expose more information on test failure to help you debug failing tests faster
The audience for reading such test results can be expanded by adding HTML reporting as an option in addition to current stdout reporting.
What I have in mind is something along the lines of report formatting provided by the HtmlTestRunner project which uses Jinja2 and Bootstrap under the hood.
HTML unittest reports can be saved to disk for historical auditing, or written to /tmp for one time or temporary viewing (default setting).
Basic HTML output screenshot
The text was updated successfully, but these errors were encountered: