michael@0: The BrowserScope project provides a set of cross-browser HTML editor tests,
michael@0: which we import in our test suite in order to run them as part of our
michael@0: continuous integration system.
michael@0: 
michael@0: We pull tests occasionally from their Subversion repository using the pull
michael@0: script which can be found in this directory.  We also record the revision ID
michael@0: which we've used in the current_revision file inside this directory.
michael@0: 
michael@0: Using the pull script is quite easy, just switch to this directory, and say:
michael@0: 
michael@0: sh update_from_upstream
michael@0: 
michael@0: There are tests which we're currently failing on, and there will probably be
michael@0: more of those in the future.  We should maintain a list of the failing tests
michael@0: manually in currentStatus.js (which can also be found in this directory), to
michael@0: make sure that the suite passes entirely, with failing tests marked as todo
michael@0: items.
michael@0: 
michael@0: The current status of the test suite needs to be updated whenever an editor
michael@0: bug gets fixed, which makes us pass one of the tests.  When that happens,
michael@0: you should set the UPDATE_TEST_RESULTS constant to true in test_richtext2.html,
michael@0: run the test suite, paste the result JSON string in a JSON beautifier (such
michael@0: as http://jsbeautifier.org/), and use the result to update currentStatus.js.