But if I invoke it directly from the command line arguments:
$ pact-5 broken-script.repl
Load failed
$
I have got no information about what's wrong... only Load failed
Expected Behavior
I would expect to have the same level of debug and error reporting when invoking the script from the command line. It's important, since I have some tests suites split in several repl files, batch called by a shell/make script, or GH actions.
From my point of view, it's critical to be able to identify quickly errors when running the test suite.
Issue description
When starting a REPL file from the command line, Pact 5.0 doesn't show errors. It only shows
Load failed
Steps to reproduce
Let's consider the file
broken-script.repl
. It contains:If I load it inside the repl:
Good ... Pact gives me useful information.
But if I invoke it directly from the command line arguments:
I have got no information about what's wrong... only
Load failed
Expected Behavior
I would expect to have the same level of debug and error reporting when invoking the script from the command line. It's important, since I have some tests suites split in several repl files, batch called by a shell/make script, or GH actions.
From my point of view, it's critical to be able to identify quickly errors when running the test suite.