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
This is a laundry list of improvements I'd like to make to our spec package. We can extract a few of these bullet points into issues of their own, but so far I'm listing them here so we don't lose track of them.
Print the absolute path of the file where a failure happens.
Print messages in color.
When an example ends report OK, SKIP or FAIL depending on the state. Right now it will print OK even with failures.
Print F when reporting a single failure, and then print all failures (with the print_failure function) when calling @reporter.spec_ended, after everything runs.
Clean up spec.savi and specs.savi from code we don't need anymore.
The text was updated successfully, but these errors were encountered:
When an example ends report OK, SKIP or FAIL depending on the state. Right now it will print OK even with failures.
Print F when reporting a single failure, and then print all failures (with the print_failure function) when calling @reporter.spec_ended, after everything runs
This is a laundry list of improvements I'd like to make to our
spec
package. We can extract a few of these bullet points into issues of their own, but so far I'm listing them here so we don't lose track of them.print_failure
function) when calling@reporter.spec_ended
, after everything runs.spec.savi
andspecs.savi
from code we don't need anymore.The text was updated successfully, but these errors were encountered: