Skip to content

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

@sfloess

Description

@sfloess

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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions