Opened 4 years ago

Last modified 16 months ago

#11083 new task

TBB Test suite: check that tor-launcher is working

Reported by: boklm Owned by: boklm
Priority: Medium Milestone:
Component: Applications/Quality Assurance and Testing Version:
Severity: Normal Keywords: tbb-testcase
Cc: mcs, brade Actual Points:
Parent ID: #11024 Points:
Reviewer: Sponsor:


The TBB Test suite should use tor-launcher to run tor.

Child Tickets

Change History (7)

comment:1 Changed 4 years ago by boklm

Current status on this task:
Because I didn't figure out yet a way to automate the start of tor with tor-launcher and check that it worked, the test suite currently starts tor without using tor-launcher. It then disable tor-launcher with the TOR_SKIP_LAUNCH environment variable, and sets TOR_SOCKS_PORT, TOR_CONTROL_PORT, TOR_CONTROL_HOST and TOR_CONTROL_COOKIE_AUTH_FILE environment variables before running the tests:

comment:2 Changed 4 years ago by mcs

Cc: mcs brade added

comment:3 Changed 4 years ago by gk

Why not writing a Mozmill test and check for the TorProcessStatus? Or listening to the various observer notifications?

comment:4 Changed 4 years ago by gk

Scratch the notifications idea. They are (I guess) fired way earlier than the Mozmill test is running...

comment:5 Changed 4 years ago by mcs

In addition to TorProcessStatus, you may also find it useful to access the TorIsBootstrapDone property. Both are part of the tl-process component, e.g.,

var svc = Cc[";1"]
var torProcessService = svc.wrappedJSObject;
if (torProcessService.TorIsBootstrapDone)
  // do something here

comment:6 Changed 4 years ago by erinn

Keywords: needs-triage added

comment:7 Changed 16 months ago by boklm

Component: Applications/Tor bundles/installationApplications/Quality Assurance and Testing
Keywords: tbb-testcase added; needs-triage removed
Severity: Normal
Note: See TracTickets for help on using tickets.