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
Usually a test runner that has failing test will have an exit code of non-zero (like 1) when exiting. This does not, meaning that when it fails one is unable to inspect the error code to determine if there were failing tests.
The text was updated successfully, but these errors were encountered:
@rpgeeganage I am no longer able to modify the code at this point 😿 I am not even able to find out where the test runner starts. Some sprinkled comments here and there would have helped 😸
After trying to analyze this, I am guessing the reporter could keep some internal failure counter and then when Processor#task is finally finished it can ask the reporter for the failure count and exit with process.exit(1) if it is > 0?
Usually a test runner that has failing test will have an exit code of non-zero (like 1) when exiting. This does not, meaning that when it fails one is unable to inspect the error code to determine if there were failing tests.
The text was updated successfully, but these errors were encountered: