Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 # Running layout tests on Linux | 1 # Running layout tests on Linux |
| 2 | 2 |
| 3 1. Build `blink_tests` (see [Linux-specific build instructions](https://chromiu m.googlesource.com/chromium/src/+/master/docs/linux_build_instructions.md)) | 3 1. Build `blink_tests` (see [Linux-specific build instructions](https://chromiu m.googlesource.com/chromium/src/+/master/docs/linux_build_instructions.md)) |
| 4 1. Checkout the layout tests | 4 1. Checkout the layout tests |
| 5 * If you have an entry in your `.gclient` file that includes | 5 * If you have an entry in your `.gclient` file that includes |
| 6 "LayoutTests", you may need to comment it out and sync. | 6 "LayoutTests", you may need to comment it out and sync. |
| 7 * You can run a subset of the tests by passing in a path relative to | 7 * You can run a subset of the tests by passing in a path relative to |
| 8 `src/third_party/WebKit/LayoutTests/`. For example, | 8 `src/third_party/WebKit/LayoutTests/`. For example, |
| 9 `run_layout_tests.py fast` will only run the tests under | 9 `run_layout_tests.py fast` will only run the tests under |
| 10 `src/third_party/WebKit/LayoutTests/fast/`. | 10 `src/third_party/WebKit/LayoutTests/fast/`. |
| 11 1. When the tests finish, any unexpected results should be displayed. | 11 1. When the tests finish, any unexpected results should be displayed. |
| 12 | 12 |
| 13 See | 13 See |
| 14 [Running WebKit Layout Tests](http://dev.chromium.org/developers/testing/webkit- layout-tests) | 14 [Running Layout Tests](https://chromium.googlesource.com/chromium/src/+/master/d ocs/testing/layout_tests.md) |
|
Dirk Pranke
2016/11/15 22:24:55
same.
| |
| 15 for full documentation about set up and available options. | 15 for full documentation about set up and available options. |
| 16 | 16 |
| 17 ## Pixel Tests | 17 ## Pixel Tests |
| 18 | 18 |
| 19 The pixel test results were generated on Ubuntu 10.4 (Lucid). If you're running | 19 The pixel test results were generated on Ubuntu 10.4 (Lucid). If you're running |
| 20 a newer version of Ubuntu, you will get some pixel test failures due to changes | 20 a newer version of Ubuntu, you will get some pixel test failures due to changes |
| 21 in freetype or fonts. In this case, you can create a Lucid 64 chroot using | 21 in freetype or fonts. In this case, you can create a Lucid 64 chroot using |
| 22 `build/install-chroot.sh` to compile and run tests. | 22 `build/install-chroot.sh` to compile and run tests. |
| 23 | 23 |
| 24 ## Fonts | 24 ## Fonts |
| (...skipping 104 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 129 In your `.xmonad/xmonad.hs`, change your config to include a manageHook along | 129 In your `.xmonad/xmonad.hs`, change your config to include a manageHook along |
| 130 these lines: | 130 these lines: |
| 131 | 131 |
| 132 ``` | 132 ``` |
| 133 test_shell_manage = className =? "Test_shell" --> doFloat | 133 test_shell_manage = className =? "Test_shell" --> doFloat |
| 134 main = xmonad $ | 134 main = xmonad $ |
| 135 defaultConfig | 135 defaultConfig |
| 136 { manageHook = test_shell_manage <+> manageHook defaultConfig | 136 { manageHook = test_shell_manage <+> manageHook defaultConfig |
| 137 ... | 137 ... |
| 138 ``` | 138 ``` |
| OLD | NEW |