Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify error status #462

Merged
merged 5 commits into from
Sep 21, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion building/tooling/test-runners/interface.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,11 @@ The following overall statuses are valid:

- `pass`: All tests passed
- `fail`: At least one test has the status `fail` or `error`
- `error`: No test was executed correctly (this usually means e.g. a compile error, or a syntax error)
- `error`: No test was executed (this usually means e.g. a compile error, or a syntax error)
ErikSchierboom marked this conversation as resolved.
Show resolved Hide resolved

To clarify, `error` should _only_ be used if **none of the tests were run**.
ErikSchierboom marked this conversation as resolved.
Show resolved Hide resolved
Usually, this only happens for compiled languages, as not being able to compile the code will prevent the tests from being run.
ErikSchierboom marked this conversation as resolved.
Show resolved Hide resolved
In most interpreted languages, the tests will run even with syntax errors in the source, as they'll only find that out at run time.
ErikSchierboom marked this conversation as resolved.
Show resolved Hide resolved

#### Message

Expand Down