-
Notifications
You must be signed in to change notification settings - Fork 472
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
Separate exit code for test parsing errors? #317
Comments
I was looking for documentation/code that would explain the different possible error values... and this proves that's no specific policy. |
Agree, this would be useful for scripting. |
It is. E.g., FreeBSD documents it in sysexits man page, Linux has So, for incorrect yaml the proper exit code would probably be |
I'm also affected by this. I maintain the degoss Ansible role (which installs, runs, and removes Goss and test cases on a machine), and I have to write some very interesting logic to catch these kinds of errors. Goss returns My workaround is to set |
I would say that this is also importnat for check over HTTP?
|
Thanks for all the hard work on this utility, I've found it really easy to use.
I use a simple bash script to run tests depending on different facter facts on hosts. However, I'd like to be able to tell failing tests from synctactically incorrect tests, e.g.:
I believe having a separate exit code for YAML parsing/template rendering would make scripting easier.
The text was updated successfully, but these errors were encountered: