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

Investigate using a code coverage tool #446

Open
dakrone opened this issue Apr 19, 2018 · 1 comment
Open

Investigate using a code coverage tool #446

dakrone opened this issue Apr 19, 2018 · 1 comment
Labels

Comments

@dakrone
Copy link
Owner

@dakrone dakrone commented Apr 19, 2018

clj-http has a lot of tests, but it would be good to know exactly what's not being exercised.

There are some automated tools out there that can show coverage, it'd be great to hook one of those up.

dakrone added a commit that referenced this issue Apr 25, 2018
This bumps clojure library deps that have a new versions, as well as adding
exclusions/explicit dependencies on some libraries in order to satisfy the
National Vulnerability Database

Semi-related to #446
@dakrone

This comment has been minimized.

Copy link
Owner Author

@dakrone dakrone commented Apr 25, 2018

As a note, I have tried https://github.com/cloverage/cloverage but I have not been able to get it to run yet.

dakrone added a commit that referenced this issue Apr 25, 2018
This bumps clojure library deps that have a new versions, as well as adding
exclusions/explicit dependencies on some libraries in order to satisfy the
National Vulnerability Database

Semi-related to #446
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.