Changes between Version 37 and Version 38 of Writing Layout Tests for DumpRenderTree
- Timestamp:
- Jun 19, 2012, 1:17:30 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Writing Layout Tests for DumpRenderTree
v37 v38 19 19 {{{ 20 20 <script> 21 layoutTestController.dumpAsText();21 testRunner.dumpAsText(); 22 22 </script> 23 23 }}} … … 29 29 {{{ 30 30 <script> 31 if (window. layoutTestController)32 layoutTestController.dumpAsText()31 if (window.testRunner) 32 testRunner.dumpAsText() 33 33 </script> 34 34 }}} … … 111 111 </style> 112 112 <script> 113 if (window. layoutTestController)114 layoutTestController.dumpAsText();113 if (window.testRunner) 114 testRunner.dumpAsText(); 115 115 116 116 function log(message) … … 197 197 198 198 {{{ 199 if (window. layoutTestController)200 layoutTestController.dumpAsText(true);199 if (window.testRunner) 200 testRunner.dumpAsText(true); 201 201 }}} 202 202 … … 221 221 These can be used to perform additional debugging-related tasks. 222 222 223 == `window. layoutTestController` ==223 == `window.testRunner` == 224 224 225 225 === `dumpAsText()` === … … 229 229 === `waitUntilDone()` and `notifyDone()` === 230 230 231 By default, DumpRenderTree dumps each test file immediately after the document has loaded and the load event handlers have executed. If your test needs to do further processing after loading -- for example, waiting for a timer to fire -- call ` layoutTestController.waitUntilDone()` to tell DumpRenderTree to delay its dump, and then call `notifyDone` when your results are ready.231 By default, DumpRenderTree dumps each test file immediately after the document has loaded and the load event handlers have executed. If your test needs to do further processing after loading -- for example, waiting for a timer to fire -- call `testRunner.waitUntilDone()` to tell DumpRenderTree to delay its dump, and then call `notifyDone` when your results are ready. 232 232 233 233 === `overridePreference(key, value)` ===