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

Closed (moved)
Open
Opened Jan 20, 2014 by kpdyer@kpdyer

Run unit tests for pluggable transports when building Tor Browser Bundle

dcf and I were recently discussing the dependencies between pluggable transports in the Tor Browser Bundle. As an example obfsproxy, flashproxy, and fteproxy all rely on pyptlib.

In these cases it is important that we have sanity checks to ensure that when one of these components is upgraded, it doesn't break any of the pluggable transports. It's tedious to manually verify that each pluggable transport works.

It appears that nearly all of the pluggable transports have unit tests. A simple sanity check, running all unit tests for all PTs during the build, is probably a good idea.

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#10677