OLD | NEW |
1 # Layout Test Expectations and Baselines | 1 # Layout Test Expectations and Baselines |
2 | 2 |
3 | 3 |
4 The primary function of the LayoutTests is as a regression test suite; this | 4 The primary function of the LayoutTests is as a regression test suite; this |
5 means that, while we care about whether a page is being rendered correctly, we | 5 means that, while we care about whether a page is being rendered correctly, we |
6 care more about whether the page is being rendered the way we expect it to. In | 6 care more about whether the page is being rendered the way we expect it to. In |
7 other words, we look more for changes in behavior than we do for correctness. | 7 other words, we look more for changes in behavior than we do for correctness. |
8 | 8 |
9 [TOC] | 9 [TOC] |
10 | 10 |
(...skipping 145 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
156 longer than the usual timeout to run. Slow tests are given 5x the usual | 156 longer than the usual timeout to run. Slow tests are given 5x the usual |
157 timeout. | 157 timeout. |
158 * [SmokeTests](../../third_party/WebKit/LayoutTests/SmokeTests): A small subset | 158 * [SmokeTests](../../third_party/WebKit/LayoutTests/SmokeTests): A small subset |
159 of tests that we run on the Android bot. | 159 of tests that we run on the Android bot. |
160 * [StaleTestExpectations](../../third_party/WebKit/LayoutTests/StaleTestExpectat
ions): | 160 * [StaleTestExpectations](../../third_party/WebKit/LayoutTests/StaleTestExpectat
ions): |
161 Platform-specific lines that have been in TestExpectations for many months. | 161 Platform-specific lines that have been in TestExpectations for many months. |
162 They're moved here to get them out of the way of people doing rebaselines | 162 They're moved here to get them out of the way of people doing rebaselines |
163 since they're clearly not getting fixed anytime soon. | 163 since they're clearly not getting fixed anytime soon. |
164 * [W3CImportExpectations](../../third_party/WebKit/LayoutTests/W3CImportExpectat
ions): | 164 * [W3CImportExpectations](../../third_party/WebKit/LayoutTests/W3CImportExpectat
ions): |
165 A record of which W3C tests should be imported or skipped. | 165 A record of which W3C tests should be imported or skipped. |
166 * [WPTServeExpectations](../../third_party/WebKit/LayoutTests/WPTServeExpectatio
ns): | |
167 Expectations for tests that fail differently when run under the W3C's wptserve | |
168 HTTP server with the `--enable-wptserve flag`. This is an experimental feature | |
169 at this time. | |
170 | |
171 | 166 |
172 ### Flag-specific expectations files | 167 ### Flag-specific expectations files |
173 | 168 |
174 It is possible to handle tests that only fail when run with a particular flag | 169 It is possible to handle tests that only fail when run with a particular flag |
175 being passed to `content_shell`. See | 170 being passed to `content_shell`. See |
176 [LayoutTests/FlagExpectations/README.txt](../../third_party/WebKit/LayoutTests/F
lagExpectations/README.txt) | 171 [LayoutTests/FlagExpectations/README.txt](../../third_party/WebKit/LayoutTests/F
lagExpectations/README.txt) |
177 for more. | 172 for more. |
178 | 173 |
179 ## Updating the expectations files | 174 ## Updating the expectations files |
180 | 175 |
(...skipping 108 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
289 | 284 |
290 You can verify that any changes you've made to an expectations file are correct | 285 You can verify that any changes you've made to an expectations file are correct |
291 by running: | 286 by running: |
292 | 287 |
293 ```bash | 288 ```bash |
294 third_party/WebKit/Tools/Scripts/lint-test-expectations | 289 third_party/WebKit/Tools/Scripts/lint-test-expectations |
295 ``` | 290 ``` |
296 | 291 |
297 which will cycle through all of the possible combinations of configurations | 292 which will cycle through all of the possible combinations of configurations |
298 looking for problems. | 293 looking for problems. |
OLD | NEW |