Skip to content

Measure code coverage of integration tests (API tests) over time #84

@pdurbin

Description

@pdurbin

Over at IQSS/dataverse#6124 I'm planning on attempting to automate the instrumentation of the Dataverse war file that @pameyer documented at http://guides.dataverse.org/en/4.16/developers/testing.html#measuring-coverage-of-integration-tests

I'll probably spin up an installation of Dataverse on EC2 using ec2-create-instance.sh script mentioned in the README at https://github.com/IQSS/dataverse-sample-data

It would be nice to also report code coverage of integration tests here for the dataverse-kubernetes repo. I have less of an idea of how to get started here but I'm sure @poikilotherm will help explain.

One thing I'd like to make clear is that my focus is on code coverage of integration tests rather than unit tests. We already have code coverage of unit tests and a button for this that I added in IQSS/dataverse@7319fb1

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