Changes between Version 11 and Version 12 of Creating and Submitting Layout Tests and Patches
- Timestamp:
- Jun 19, 2012, 1:16:37 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Creating and Submitting Layout Tests and Patches
v11 v12 20 20 * Otherwise, create a new testcase. 21 21 * Many tests are HTML files containing !JavaScript that exercises a single feature or sub-feature and produces a reliable, easily recognizable result. For example, see {{{fast/events/event-creation.html}}} or {{{fast/dom/HTMLSelectElement/listbox-select-reset.html}}}. 22 * It's also possible to create a testcase that produces a PNG file and checksum to be compared with an expected result, if you're testing things like colors. For example, see {{{fast/dom/css-rule-functions.html}}}. For that, be sure ''not'' to use {{{ layoutTestController.dumpAsText()}}}.22 * It's also possible to create a testcase that produces a PNG file and checksum to be compared with an expected result, if you're testing things like colors. For example, see {{{fast/dom/css-rule-functions.html}}}. For that, be sure ''not'' to use {{{testRunner.dumpAsText()}}}. 23 23 * Create the expected result file(s). 24 24 * If your fix fixes an existing test (or breaks one, but you're certain it's correct), delete the existing expected result(s) for that test so a new expected result can be generated.