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.

Sign up for GitHub

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

Jump to bottom

In Bunit.bsh, instead of System.exit(-1) to fail, figure out a more elegant solution so after() and afterClass() are guarenteed to be called #4

Open

sfloess opened this issue May 13, 2017 · 0 comments

Assignees

Labels

Backlog enhancement

Member

sfloess commented May 13, 2017

We have some corner cases where System.exit(-1) is called:

Duplicate test methods
Exceptions denoted as expected but are not raised.

Need a more elegant solution so that we can cease execution of tests but ensure all after() and afterClass() methods are called.

The text was updated successfully, but these errors were encountered:

sfloess added the enhancement label

sfloess self-assigned this

sfloess changed the title ~~In Bunit.bsh, instead of System.exit(-1) to fail, figure out a more elegant solution so after() and afterClass() can be gaurenteed to be called~~ In Bunit.bsh, instead of System.exit(-1) to fail, figure out a more elegant solution so after() and afterClass() can be guarenteed to be called

sfloess changed the title ~~In Bunit.bsh, instead of System.exit(-1) to fail, figure out a more elegant solution so after() and afterClass() can be guarenteed to be called~~ In Bunit.bsh, instead of System.exit(-1) to fail, figure out a more elegant solution so after() and afterClass() are guarenteed to be called

sfloess added the Backlog label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment