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
  • #1825

Closed (moved)
Open
Opened Aug 12, 2010 by Karsten Loesing@karsten

Add unit tests for statistics code

We still lack unit tests for most of the statistics code in Tor. The recent changes in the course of allowing *Statistics options to be enabled or disabled while Tor is running are a first step in writing good unit tests. We should further refactor the statistics code, e.g., so that it doesn't depend on get_options() and separates generating statistics output from writing it to disk.

Branch stats-tests in my public repository has the refactorings and unit tests for exit port statistics.

I'd like to know if the refactorings are correct and if the tests make sense. If so, let's merge these, and I'll do the same for the other statistics code.

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