Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
pdurbin opened this issue Sep 3, 2019 · 0 comments
Open

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

pdurbin opened this issue Sep 3, 2019 · 0 comments

Comments

@pdurbin
Copy link
Member

pdurbin commented Sep 3, 2019

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

@pdurbin pdurbin added this to To do for poikilotherm in pdurbin Sep 3, 2019
@poikilotherm poikilotherm removed this from To do for poikilotherm in pdurbin Sep 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant