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

spike: experiment with codecov's "merge reports" #553

Open
1 task
vanderhoop opened this issue Nov 25, 2019 · 0 comments
Open
1 task

spike: experiment with codecov's "merge reports" #553

vanderhoop opened this issue Nov 25, 2019 · 0 comments

Comments

@vanderhoop
Copy link
Contributor

vanderhoop commented Nov 25, 2019

As a developer,
I want to have our front-end and backend code coverage merged into a single report
So that I and pull-request submitters have a holistic view of their coverage.

By Way Of Explanation: at the moment, our Coveralls integration is only tracking coverage for Elixir (backend code), as Coveralls doesn't support multiple reports (or merging multiple reports) for a given build. While our frontend coverage is solid, folks who submit pull requests aren't automatically notified if their coverage goes down in the front-end, because we have yet to set this up. And this results in a delay between submission and feedback.

Acceptance Criteria:

  • open branch with codecov integration, surfacing coverage/deficiencies across both the backend AND frontend

Helpful Links:

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