[tor-bugs] #13053 [Quality Assurance and Testing]: Write regression tests for new NoScript options
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Mar 24 10:21:59 UTC 2015
#13053: Write regression tests for new NoScript options
-------------------------------------+-------------------------------------
Reporter: mikeperry | Owner: boklm
Type: task | Status: closed
Priority: normal | Milestone:
Component: Quality Assurance | Version:
and Testing | Keywords: tbb-testcase,
Resolution: fixed | tbb-4.5-alpha
Actual Points: | Parent ID: #9387
Points: |
-------------------------------------+-------------------------------------
Changes (by gk):
* status: needs_information => closed
* resolution: => fixed
Comment:
Replying to [comment:27 boklm]:
> Replying to [comment:26 gk]:
> >
> > I am on commit 7c9eb3c52b009de4625cacd7a4a832b56fc919c3. If I take a
default en-US bundle and start the test with `./tbb-testsuite --enable-
tests=noscript tor-browser-linux64-4.5a4_en-US.tar.xz` I get:
>
> This test requires a working tor daemon, so you might want to add
"--tor-control-port=9151 --tor-socks-port=9150" to the command line to use
an existing tor daemon.
Ok. But why are the other tests not failing then if the test requires a
working tor daemon? Should not all tests (even outside of noscript.js)
that require tor fail if it is not working in order to be sure that we
have a proper test environment at all in order to do the tests we want?
> Or use "--enable-tests=tor_bootstrap,noscript" to start one before the
noscript test.
That is not working for me. Just the first test is running and that's it.
Anyway, this ticket seems fixed then.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13053#comment:28>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list