The Tor Browser / file comparison
comparison: editor/libeditor/html/tests/browserscope/lib/richtext2/README.Mozilla
editor/libeditor/html/tests/browserscope/lib/richtext2/README.Mozilla
- branch
- TOR_BUG_3246
- changeset 7
- 129ffea94266
equal
deleted
inserted
replaced
| -1:000000000000 | 0:9630ceaddc99 |
|---|---|
| 1 The BrowserScope project provides a set of cross-browser HTML editor tests, | |
| 2 which we import in our test suite in order to run them as part of our | |
| 3 continuous integration system. | |
| 4 | |
| 5 We pull tests occasionally from their Subversion repository using the pull | |
| 6 script which can be found in this directory. We also record the revision ID | |
| 7 which we've used in the current_revision file inside this directory. | |
| 8 | |
| 9 Using the pull script is quite easy, just switch to this directory, and say: | |
| 10 | |
| 11 sh update_from_upstream | |
| 12 | |
| 13 There are tests which we're currently failing on, and there will probably be | |
| 14 more of those in the future. We should maintain a list of the failing tests | |
| 15 manually in currentStatus.js (which can also be found in this directory), to | |
| 16 make sure that the suite passes entirely, with failing tests marked as todo | |
| 17 items. | |
| 18 | |
| 19 The current status of the test suite needs to be updated whenever an editor | |
| 20 bug gets fixed, which makes us pass one of the tests. When that happens, | |
| 21 you should set the UPDATE_TEST_RESULTS constant to true in test_richtext2.html, | |
| 22 run the test suite, paste the result JSON string in a JSON beautifier (such | |
| 23 as http://jsbeautifier.org/), and use the result to update currentStatus.js. |
