1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/editor/libeditor/html/tests/browserscope/lib/richtext2/README.Mozilla Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,23 @@
1.4 +The BrowserScope project provides a set of cross-browser HTML editor tests,
1.5 +which we import in our test suite in order to run them as part of our
1.6 +continuous integration system.
1.7 +
1.8 +We pull tests occasionally from their Subversion repository using the pull
1.9 +script which can be found in this directory. We also record the revision ID
1.10 +which we've used in the current_revision file inside this directory.
1.11 +
1.12 +Using the pull script is quite easy, just switch to this directory, and say:
1.13 +
1.14 +sh update_from_upstream
1.15 +
1.16 +There are tests which we're currently failing on, and there will probably be
1.17 +more of those in the future. We should maintain a list of the failing tests
1.18 +manually in currentStatus.js (which can also be found in this directory), to
1.19 +make sure that the suite passes entirely, with failing tests marked as todo
1.20 +items.
1.21 +
1.22 +The current status of the test suite needs to be updated whenever an editor
1.23 +bug gets fixed, which makes us pass one of the tests. When that happens,
1.24 +you should set the UPDATE_TEST_RESULTS constant to true in test_richtext2.html,
1.25 +run the test suite, paste the result JSON string in a JSON beautifier (such
1.26 +as http://jsbeautifier.org/), and use the result to update currentStatus.js.
