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

Set up coveralls #61

Open
starsplatter opened this issue Mar 2, 2017 · 7 comments
Open

Set up coveralls #61

starsplatter opened this issue Mar 2, 2017 · 7 comments
Assignees

Comments

@starsplatter
Copy link
Member

No description provided.

@cappadona
Copy link
Contributor

cappadona commented May 5, 2017

  • add repo to coveralls
  • add coveralls gem
  • add status check for dev branch

@starsplatter starsplatter added this to the June 1 Release milestone May 30, 2017
@cappadona
Copy link
Contributor

Deployed to dev.

@JesiBuell79
Copy link

@chrisrlc done? What does coveralls do? Still needed?

@chrisrlc
Copy link
Collaborator

@JesiBuell79 Coveralls generates a code coverage report that shows how much of your code is actually covered by automatic tests. It looks like we have this set up for spotlight, but our billing info for coveralls expired in early 2020... That said, I'd prefer to use consistent tooling across our apps where possible, so I'm going to do some digging to figure out what code coverage tool other apps use.

@JesiBuell79
Copy link

@chrisrlc - Great thank you - and yes, I agree in terms of consistency!

@philiprobinson
Copy link
Collaborator

philiprobinson commented Feb 24, 2023 via email

@chrisrlc
Copy link
Collaborator

Thanks @philiprobinson! I talked to Jim a couple days ago to find out what d&a and dcp are using. Sounds like they're trying to use simplecov, but they need cleanup. He's got a ticket for the upcoming sprint to fix code coverage setup for DCP that I'm keeping an eye on in case we can replicate for exhibits/spotlight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants