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.

Taken from firefox sources in directory content/media/test.

Those files are going to be used in a test page loading videos.

Downloaded from:
http://v2v.cc/~j/theora_testsuite/320x240.ogg
http://v2v.cc/~j/theora_testsuite/320x240.skeleton+cmml.ogv

Before running each mozmill test, export testsuite and test options as
json to a file that can be included by the test.

For some unknown reason, those tests are blocking and never finish.

We set this in xorg.conf instead of resizing using xrandr, to avoid
fonts resize problems.

This does not remove the problem for resolution defined in each test
(currently not used). To fix that, we may need to start a specific X
server for the test.

Add an --no-xdummy option to avoid doing this.

We are now starting an X server with the dummy driver, and a window
manager, to run the tests, instead of xvfb.

Some mochitests are failing when they are running inside xvfb instead of
a real window manager.

This will be used to start an X server with a dummy driver, and a window
manager, to run the tests in.

The Xdummy script and the xorg.conf files have been taken from xpra.org.

This test enumerates all DOM objects exposed in the global namespace
and produce an error if one of them is not in the expected list.

This test has been suggested in the iSEC partners' report:
https://blog.torproject.org/blog/isec-partners-conducts-tor-browser-hardening-study

This allows us to retest everything when we update the testsuite.

YAML::Syck is much faster

Old reports may have 'tbbfile' as report type.