editor/libeditor/html/tests/browserscope/lib/richtext/README.Mozilla@7e26c7da4463 (annotated)
editor/libeditor/html/tests/browserscope/lib/richtext/README.Mozilla
Wed, 31 Dec 2014 06:55:50 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Wed, 31 Dec 2014 06:55:50 +0100
- changeset 2
- 7e26c7da4463
- permissions
- -rw-r--r--
Added tag UPSTREAM_283F7C6 for changeset ca08bd8f51b2
| michael@0 | 1 | The BrowserScope project provides a set of cross-browser HTML editor tests, |
| michael@0 | 2 | which we import in our test suite in order to run them as part of our |
| michael@0 | 3 | continuous integration system. |
| michael@0 | 4 | |
| michael@0 | 5 | We pull tests occasionally from their Subversion repository using the pull |
| michael@0 | 6 | script which can be found in this directory. We also record the revision ID |
| michael@0 | 7 | which we've used in the current_revision file inside this directory. |
| michael@0 | 8 | |
| michael@0 | 9 | Using the pull script is quite easy, just switch to this directory, and say: |
| michael@0 | 10 | |
| michael@0 | 11 | sh update_from_upstream |
| michael@0 | 12 | |
| michael@0 | 13 | There are tests which we're currently failing on, and there will probably be |
| michael@0 | 14 | more of those in the future. We should maintain a list of the failing tests |
| michael@0 | 15 | manually in currentStatus.js (which can also be found in this directory), to |
| michael@0 | 16 | make sure that the suite passes entirely, with failing tests marked as todo |
| michael@0 | 17 | items. |
