Skip to content

Recommendations for test and coverage reports #43

@bpancras

Description

@bpancras

The best practices do not make any recommendation on where to store the test and coverage reports. It would be nice to have some guidelines/ recommendations.

During local development, we want a folder to store the test and coverage reports, there is not much value in adding these reports to the source control system since these reports tend to change with every test execution, On a CI system, these reports have to be read by the system itself to create an overview of the pipeline execution.

Here is a proposal:

  1. Create the reports folder under the repo root
  2. Do not add the contents of the reports folder to the source control system

I also want to tie this conversation with the issue we have for badges: #20

I'm not a fan of committing changes from the CI system.

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