Skip to content

Documentation on generating test coverage is outdated #28867

@bvobart

Description

@bvobart

The TESTING documentation states that test coverage can be generated with a Maven command. However, Elasticsearch currently uses Gradle. Issue #13930 describes the migration from Maven to Gradle and states that the documentation for building and testing was completely updated except for the documentation on JaCoCo reports.

So is it currently possible to create a test coverage report? And if so, how? I'd gladly open a PR with updated documentation once I get it working.

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