jstests: licensing, templates, gTestfile, gczeal, test coverage

[Bob Clary-2]

js tests licensing:

Hey all. In response to the increased overhead of the license headers in
the jstests, we are going to be releasing as many of the tests under the
public domain as we can get permission from the listed contributors to
do so.

Essentially, the license boiler plate will be replaced by:

/*
  * Any copyright is dedicated to the Public Domain.
  * http://creativecommons.org/licenses/publicdomain/
  * Contributor:
  */

If you are listed as the sole contributor on a js test, please either
replace the license boiler plate with the above pd with your name added
or go to https://bugzilla.mozilla.org/show_bug.cgi?id=512247 and give me
explicit permission to relicense the file.

Considering the potential number of test files that need to be edited, I
would appreciate it if you would do your own if you have time and check
in rights. If not, I'll do them in batches over a period of time.

js tests templates:

The test templates have been updated to contain the pd language so that
if you use the templates, the licensing will not be an issue going forward.

gTestfile:

Many of you don't like to use the templates and prefer the most minimal
test possible. I've mentioned the use of reportCompare and friends
before, but I would also like to mention setting gTestfile at the
beginning of your tests. This allows the user defined setter in the top
level shell.js to output a begin test: suite/subsuite/test.js before the
body of the test begins executing and is used in the jsreftest style
reporting to create the full "test id" suite/subsuite/test.js for
reporting results.

gczeal:

Now that the js tests run in the browser in a single invocation, it is
important that if you use gczeal or other javascript options during a
test, that you make sure to clean up after yourself and leave the
browser with unchanged options when a test is completed. Otherwise you
may inadvertently break subsequent tests.

Tinderbox coverage:

We finally have the js tests running in the browser for optimized builds
on the TraceMonkey repo. We won't have debug coverage until
https://bugzilla.mozilla.org/show_bug.cgi?id=524176 is fixed (which is
marked future). So, until then, you _must_ take responsibility for
running the jsreftests in a debug build before checking into tracemonkey.

/your friendly testmonkey
_______________________________________________
dev-tech-js-engine mailing list
dev-tech-js-engine@...
https://lists.mozilla.org/listinfo/dev-tech-js-engine