gecko-dev/dom/imptests
Ryan VanderMeulen 6d6c4efbab Backout the bug 754202 backout due to orange. 2012-06-10 19:37:47 -04:00
..
editing Bug 748310 - Return false for invalid createLink/insertImage values instead of throwing; r=ehsan 2012-05-22 12:37:17 +03:00
failures Backout the bug 754202 backout due to orange. 2012-06-10 19:37:47 -04:00
html/tests/submission Bug 591467 - Add tests for microdata 2012-06-04 16:49:57 -07:00
webapps
Makefile.in Bug 591467 - Add tests for microdata 2012-06-04 16:49:57 -07:00
README Bug 751842 part 5 - Put testharness.js expected fails in one file per test; r=jhammel 2012-05-15 09:35:31 +03:00
WebIDLParser.js
editing.mk Bug 756808 - Fix build error due to a trailing slash in the |DIRS| makefile variable; r=AryehGregor 2012-05-20 13:12:41 +02:00
editing.txt Bug 751842 part 6 - Import editing spec tests; r=Ms2ger 2012-05-07 08:54:55 +03:00
html.mk Bug 591467 - Add tests for microdata 2012-06-04 16:49:57 -07:00
html.txt Bug 591467 - Add tests for microdata 2012-06-04 16:49:57 -07:00
idlharness.js
importTestsuite.py Bug 756808 - Fix build error due to a trailing slash in the |DIRS| makefile variable; r=AryehGregor 2012-05-20 13:12:41 +02:00
parseManifest.py
testharness.css
testharness.js
testharnessreport.js Bug 590640 part 4 - Print out testharness.js test name on fails as well as passes; r=jhammel 2012-05-09 12:46:23 +03:00
updateTestharness.py
webapps.mk
webapps.txt

README

This directory contains tests imported from W3C test suites. In order to make it
as easy as possible to update these tests, no changes are made to the imported
files (names for scripted tests do get a test_ prefix to integrate with the test
runner, however). The scripts to update tests are provided.


=======================
Files in this directory
=======================

Source;  Usage and purpose;  License

* testharness.js / testharness.css
  Directly imported from the W3C repository (<http://dvcs.w3.org/hg/resources>),
  with the updateTestharness.py script.
  Provide the test harness.
  W3C Test Suite License / W3C 3-clause BSD License

* idlharness.js
  Directly imported from the W3C repository (<http://dvcs.w3.org/hg/resources>),
  with the updateTestharness.py script.
  Used to test WebIDL.
  W3C Test Suite License / W3C 3-clause BSD License

* WebIDLParser.js
  Directly imported from the W3C repository (<http://dvcs.w3.org/hg/resources>),
  with the updateTestharness.py script.
  Used by idlharness.js to parse IDL blocks.
  MIT License

* updateTestharness.py
  Used to update the above files.
  MPL

* parseManifest.py
  Imported from <https://bitbucket.org/ms2ger/test-runner>. Parses MANIFEST
  files (provided in the W3C repository) as documented at
  <https://bitbucket.org/ms2ger/test-runner/raw/tip/manifests.txt>.
  MIT License

* testharnessreport.js
  Glue between testharness.js and our Mochitest runner.
  MPL

* importTestsuite.py
  Imports a test suite from a remote repository. Takes one argument, a file in
  the format described under webapps.txt.
  Note: removes both source and destination directory before starting. Do not
        use with outstanding changes in either directory.
  MPL

* Makefile.in
  Integration with our build system. Installs support files into /resources and
  includes a .mk file for each repository.
  MPL

* failures/
  Expected failures for tests in each repository.  Each test's failures, if
  any, are in a file with the same path and name with .json appended.  New
  expected fail files currently needed to be added manually to makefiles.

* html.mk / webapps.mk / ...
  Generated by importTestsuite.py from webapps.txt.
  Contains a list of the directories with tests. To be included in Makefile.in.

* html.txt / webapps.txt / ...
  Input to importTestsuite.py.
  Lists the URL of the repository and the destination directory (separated by a
  vertical bar), followed by a list of directories within the repository
  (separated by line feeds).

* html / webapps / ...
  Actual tests.
  W3C Test Suite License / W3C 3-clause BSD License


=====================================================================
Importing an additional directory from an already-imported repository
=====================================================================

Add a line to the relevant data file (e.g. webapps.txt), with the path to the
additional directory relative to the root of the remote repository, and then run
the importTestsuite.py script, passing the data file as its argument.


==========================
Importing a new test suite
==========================

Create a data file in the format documented above, and run the
importTestsuite.py script, passing the data file as its argument.  Add any
necessary files in failures/.