1020555 - Allow running mochitest.ini tests with a wrapper

Status: RESOLVED DUPLICATE of bug 1052240

(Core :: Graphics: CanvasWebGL, defect)

Description

[Kelsey Gilbert [:jgilbert]]

Right now, we have a harness built around the WebGL conformance test runner file, so the whole suite runs as a single mochitest file.

We should move towards making each conformance test file run as its own mochitest file. This should help a lot with timeouts, and also give us the ability to more easily run only certain directories. It would also allow us to use the mochitest manifest files to handle test failures, etc., instead of having our own bespoke method for it.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

given the fact that many of these existing and incoming new tests are in directories and files, we should be able to create a manifest (or set of manifests) which define each test.

The problem is we need to create a shim around these tests so they can interface with the mochitest harness.  There are probably a few ways to do this.  

one method could be to edit every file and include the shim (wrapper.js) which could then drive the test.

another option would be to edit the manifests to support a wrapper:
[default]
support-files = ...
wrapper = wrapper.html

[test1.html]
skip-if = os == "android"
[test2.html]
...

In this case we can then run each file as part of the wrapper.html (i.e. wrapper.html?test=test1.html)


These are some ideas.  I really like the idea of splitting this up into >1 "test file" for better visibility, less hacky manifests in the tree, and ideally an easier process for keeping our tests synchronized from the original source.

Comment 2

[Kelsey Gilbert [:jgilbert]]

In bug 1052240, we handle this by using a python file to generate the static wrapper files for use by mochitest.ini.