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
{{ message }}
Repository navigation
Test runner interface docs error condition could be clarified #586
It says "tests were run" but I think it means "tests were completed", because I thought "the tests ran but they errored", but of course you could say they didn't run because they errored.
I also find the example for interpreted languages a little distracting. Are you saying that syntax errors that prevent a file from parsing should be treated differently to other kinds of runtime errors, or are you just using that an example of a runtime error?
I suggest:
"The error status should only be used if all of the tests errored. For compiled languages this is generally a result of the code not being able to compile. For interpreted languages this is a runtime error, such as a syntax error that stops the file from parsing."
"The error status should only be used if all of the tests errored. For compiled languages this is generally a result of the code not being able to compile. For interpreted languages this is a runtime error, such as a syntax error that stops the file from parsing."
I think this wording is a good improvement, so go for it.
Activity
IsaacG commentedon Sep 25, 2025
Please use the forum to report website issues :)
rikedyp commentedon Sep 25, 2025
@IsaacG I was requested to open a PR by @ErikSchierboom in exercism/dyalog-apl-test-runner#7 (comment). As a habit I open issues to link to PRs in GitHub projects, sorry if that isn't the norm here.
ErikSchierboom commentedon Sep 26, 2025
I did ask for a PR
SleeplessByte commentedon Sep 27, 2025
I think this wording is a good improvement, so go for it.