Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #16710

Closed (moved)
Open
Opened Aug 03, 2015 by Roger Dingledine@arma

Graph or plot test coverage over time?

In reading our Sponsor S quarterly report draft, I found a section about how our unit test coverage is up to 37%, and our stem+chutney test coverage is up to 62%.

Great. What were they before, and what is their rate of change?

Is this the sort of thing where we have the numbers somewhere? Is it easy to automate over time?

Ideally we should even arrange things so the graphs can help us in some way too -- first by e.g. giving somebody a sense of satisfaction when a big branch gets merged and the coverage line shoots up a lot, but then next by helping us notice when some other big branch gets merged that suddenly undermines coverage in a way we didn't expect? Let's not do this to satisfy a funder -- let's figure out a way where tracking and visualizing our progress helps us make progress better.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#16710