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
When the test runner encounters an error, the details (stack trace, message, script name) are saved and displayed as part of the report string once all test files have been executed. However, if a setup or teardown function encounters the error, only the message itself will be displayed.
This is because of the early exit here. Since the error details are available, they should be output to ease troubleshooting.
Example:
before(function()
error("You'll see me, but not the error details! :3", 0)
end)
In this case, the test runner should likely count this as an error in the test suite (test file) and make the current section fail.
The text was updated successfully, but these errors were encountered:
When the test runner encounters an error, the details (stack trace, message, script name) are saved and displayed as part of the report string once all test files have been executed. However, if a setup or teardown function encounters the error, only the message itself will be displayed.
This is because of the early exit here. Since the error details are available, they should be output to ease troubleshooting.
Example:
In this case, the test runner should likely count this as an error in the test suite (test file) and make the current section fail.
The text was updated successfully, but these errors were encountered: