Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P pluggable transports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • pluggable transports
  • Issues
  • #10677
Closed
Open
Issue created 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.

Assignee
Assign to
Time tracking