GitLab

This should fix a problem with esr31 when the browser gets killed for
trying to use the mprotect system call.

After changes in commit 0d36f05505208e8c46ece532c9cb455cde31c417 in
tor-browser-bundle.git.

This is not really needed as only the browser require this, but Tor in
the bundle is also run with this LD_LIBRARY_PATH too, so we should test
the same.

This is needed after commit 0d36f05505208e8c46ece532c9cb455cde31c417 on
tor-browser-bundle.git.

Rather than only checking that no test is failed.

We're going to scan a lot of older releases, so we don't need to send
mails to tor-qa for that.

Replace the symlink by a copy.

Install 7z to extract files from the Windows installer.

Conflicts:
	TBBTestSuite/BrowserBundleTests.pm

This Mozmill test checks if it is possible to get resources with either
of the three available methods (getEntriesByType(), getEntriesByName()
and getEntries()). If so, it fails as this is a clear sign resource
timing has not been disabled properly and may still be active instead.

Patch on ticket #12998 has been merged, so we can uncomment this.

The check works on the en_US bundle, but not on the localized bundles
which have something like this in this setting:
{"langpack-nl@firefox.mozilla.org":{"version":"24.8.0","type":"locale",
"descriptor":"/home/testtestsuite/tbb-testsuite/tmp/ie0y0RPLZp/
tor-browser_nl/Data/Browser/profile.default/extensions/langpack-nl@firefox
.mozilla.org.xpi"}}

While running the test suite, we are bootstrapping tor on a non
default port, so we changing the value of this setting (using the
TOR_SOCKS_PORT environment variable), which makes the test fail.

Sometimes $bad_connections{'127.0.0.1:9150'} can be undefined.

dclone strips code refs and replaces them by a ref to a string, which
encode_json doesn't like. So we now replace those scalar refs with the
scalar itself.

When exporting test options to json on mozmill tests.

This mozmill test can be used to test a page. It uses infos from the
test and options to find which page to load.

The test page should set a test_result element on the page with OK if
the test was successful, or an error otherwise.

The following test options are used:

- the name of the test is the name of the page that will be loaded (with
  .html appended)

- if remote is set to true, it is loaded remotely, using the
  test_data_url option, otherwise it is loaded from the local test-data
  directory.

- timeout is the time in milliseconds to wait for the test_result
  element to appear. The default is 50000.

- interval is how often we should check if the test_result element
  appeared. The default is 100.

Set "OK" in a test_result element when the test finished.

This will allow us to use the same mozmill file for multiple tests.

A page playing a list of videos. This page is going to be used in a
mozmill test.