Made with by giki

OLD-Extending-JUnit’s-Standard-Behaviour

There are numerous aspects of JUnit’s core behavior that could be extensible via a first-class plugin or extension model.

Please note that there is considerable overlap between this page and API for Running and Reporting Tests.

Test Method Invocation Wrapping

Wrapping single tests or groups of tests with some set-up and/or tear-down, like the ExternalResource rule in JUnit 4.

Test Collection

Have a different way of collecting tests (like in ClasspathSuite).

Test File Format

Parse a different file format to specify tests (eg. Fit tests, cucumber tests).

Extension Points to Replace Runners

Provide extension points that enable behavior that currently requires a runner, thereby completely eliminating the need for custom runners. - @kcooney & @sbrannen

Lifecycle Events

Allowing an extension to have a long-lived service that stops when it is notified that the test run is ending.

First-class Support for Integration Tests

Provide first-class support for executing integration tests in contrast to JUnit’s historical focus on unit tests (i.e., test instance state is not shared across test method invocations).

Conditional Test Discovery and Execution

What if the discovery and execution of individual tests were conditional at run-time, with subsequent tests executed or ignored based on programmatic logic instead of a predetermined list of test methods per test class?

What if the decision about what next test to instantiate and execute could be based on factors such as the outcome of the previous test?