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

Automate test coverage #450

Closed
stevelinton opened this issue Jan 14, 2016 · 2 comments
Closed

Automate test coverage #450

stevelinton opened this issue Jan 14, 2016 · 2 comments
Labels
gapsagedays2016 Issues and PRs that arose at https://www.gapdays.de/gap-sage-days2016 kind: enhancement Label for issues suggesting enhancements; and for pull requests implementing enhancements topic: tests issues or PRs related to tests

Comments

@stevelinton
Copy link
Contributor

A very nice enhancement in the Continuous Integration framework would be to automatically check what proportion of the changed lines in a pull request get tested by the standard tests and to report on which ones.

It probably needs too many tests run to be done as part of the automatic testing on every commit that we have now, but maybe it could be done nightly or weekly, so that long-standing pull requests have this information.

It won't catch all problems, of course, but knowing that all the new code had been tested would add some confidence when deciding whether a commit is ready to merge.

@stevelinton stevelinton added kind: enhancement Label for issues suggesting enhancements; and for pull requests implementing enhancements gapsagedays2016 Issues and PRs that arose at https://www.gapdays.de/gap-sage-days2016 topic: tests issues or PRs related to tests labels Jan 14, 2016
@fingolfin
Copy link
Member

That would be really nice, of course!

But for starters, it would already be nice if we had a clear, easily accessible and ideally very simple HOWTO somewhere which tells you how to obtain coverage infomration on your own computer! That way, people who are willing to make the effort at least have a chance. And we could point people making pull requests to it, too... To this end, I just filed a bunch of issues at https://github.com/gap-packages/profiling

@olexandr-konovalov
Copy link
Member

We have now https://codecov.io/gh/gap-system/gap which does this, so this issue may be closed. I have posted some screenshots below. See also related #545, #546, #547.

screen shot 2016-08-04 at 15 56 00
screen shot 2016-08-04 at 15 53 31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gapsagedays2016 Issues and PRs that arose at https://www.gapdays.de/gap-sage-days2016 kind: enhancement Label for issues suggesting enhancements; and for pull requests implementing enhancements topic: tests issues or PRs related to tests
Projects
None yet
Development

No branches or pull requests

3 participants