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

[Releng] Evaluate tools for test coverage #3665

Open
Guite opened this issue Jul 16, 2017 · 3 comments
Open

[Releng] Evaluate tools for test coverage #3665

Guite opened this issue Jul 16, 2017 · 3 comments
Milestone

Comments

@Guite
Copy link
Member

Guite commented Jul 16, 2017

@Guite Guite added this to the 2.1.0 milestone Jul 16, 2017
@Guite Guite self-assigned this Jul 16, 2017
@craigh
Copy link
Member

craigh commented Jul 16, 2017

dup #2927

@Guite
Copy link
Member Author

Guite commented Jul 16, 2017

not a dup; I splitted them and assigned them to different milestones.

@Guite
Copy link
Member Author

Guite commented Jul 31, 2017

It seems that most tools can be combined with Travis for processing the coverage information:

@javiereguiluz said:

calculating the coverage is incredibly slow, so given that it’s not important for us to know the coverage for each pull request, we use Travis cron jobs for that (https://docs.travis-ci.com/user/cron-jobs/)

@Guite Guite removed their assignment Sep 5, 2017
@Guite Guite modified the milestones: Future Ideas, 2.1.0 Sep 6, 2017
@Guite Guite changed the title Evaluate tools for test coverage [General] Evaluate tools for test coverage Jul 15, 2020
@Guite Guite changed the title [General] Evaluate tools for test coverage [Releng] Evaluate tools for test coverage Jul 15, 2020
@Guite Guite modified the milestones: Future Ideas, 4.0.0 Nov 30, 2023
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

2 participants