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

Standardize exit statuses #104

Open
dag opened this issue May 4, 2011 · 1 comment
Open

Standardize exit statuses #104

dag opened this issue May 4, 2011 · 1 comment
Labels
Milestone

Comments

@dag
Copy link
Owner

dag commented May 4, 2011

run() should do something more programmatic such as raise different exceptions depending on the outcome of the test run, if it had failures. It should not explicitly exit or raise SystemExit.

main() should be sensitive to the API of run() and translate to SystemExits.

Reporters should not handle exiting, but may need the ability to suppress exits for e.g. GUI reporters.

@dag
Copy link
Owner Author

dag commented Sep 6, 2011

  • KeyboardInterrupt should probably exit with 130
  • If tests failed (but nothing else did) exit status 1 is probably most compatible with existing Attest and other similar projects
  • Exiting with status 2 seems de facto standard with optparse/argparse
  • There's also sysexits.h with some conventions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant