Skip to content

Improve ErrorReportingRunner, make it support Filterable, accept a class name and support better test names #1253

Closed as not planned
@paulduffin

Description

@paulduffin

ErrorReportingRunner does not support Filterable which means it doesn't play well with Filters that are trying to remove known issues. Filters often ignore descriptions that have children so that they do not filter out whole suites of tests and instead rely on a Runner that has children to support Filterable. ErrorReportingRunner has children but doesn't support Filterable so it is impossible to exclude specific problems.

All its children (in its Description) are called initializationError, that makes it impossible to filter out specific error messages.

It expects a Class<?> as its parameter which means that it cannot be used to handle exceptions resulting from a failure to load a class. It should also take a String parameter.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions