Skip to content

End-to-end should quit for Node JS when executor missing #459

@echeran

Description

@echeran

At the time of leaving this comment, the PR was passing CI checks even though the executor code in question for Node JS had not yet been added to the PR.

We should make sure that if the executor code doesn't exist, then either the executor code should report all errors, or else the pipeline should catastrophically quit early.

I want to use the word "quit" or "exit" to indicate behavior that our pipeline should take as a last resort, so that we make noise loudly and early. We should avoid succeeding silently, as we currently are, because it means we never know when we have problems.

Metadata

Metadata

Labels

bugSomething isn't working related to CI or the framework as a whole

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions