8000 JUnit should have an exhaustive listener framework · Issue #444 · junit-team/junit4 · GitHub
[go: up one dir, main page]

Skip to content
JUnit should have an exhaustive listener framework #444
@brolund

Description

@brolund

JUnit should have a listener model that provides all the events from test execution (run starting, suite starting, test case starting, test starting, failed, error, success, timeout, theories data, assumption failed etc etc), including a reference to the test/suite class and a Method object for the method at hand.

It should also allow for hooking in the listeners in a single place for an entire set of tests in an unobtrusive way, like a properties file (or possibly as an annotation on a suite, or a specific class in the execution tree).

Rules are sort of listeners, but they require more detailed manipulations of tests. RunListener provides only a fragment of the available information. If the listener framework can also change the test execution (AOP-style), the Rule implementation, as well as the RunListener, could be build on top of this framework.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0