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 [Layout Tests](testing/layout_tests.md) | 13 See [Layout Tests](testing/layout_tests.md) |
14 for full documentation about set up and available options. | 14 for full documentation about set up and available options. |
15 | 15 |
16 ## Pixel Tests | 16 ## Pixel Tests |
17 | 17 |
18 The pixel test results were generated on Ubuntu 10.4 (Lucid). If you're running | 18 The pixel test results were generated on Ubuntu 10.4 (Lucid). If you're running |
19 a newer version of Ubuntu, you will get some pixel test failures due to changes | 19 a newer version of Ubuntu, you will get some pixel test failures due to changes |
20 in freetype or fonts. In this case, you can create a Lucid 64 chroot using | 20 in freetype or fonts. In this case, you can create a Lucid 64 chroot using |
21 `build/install-chroot.sh` to compile and run tests. | 21 `build/install-chroot.sh` to compile and run tests. |
22 | 22 |
23 ## Fonts | 23 ## Fonts |
24 | 24 |
25 Make sure you have all the necessary fonts installed. | 25 Make sure you have all the necessary fonts installed. |
26 | 26 |
27 ```shell | 27 ```shell |
28 sudo apt-get install apache2 wdiff php5-cgi ttf-indic-fonts \ | 28 sudo apt-get install apache2 wdiff php5-cgi ttf-indic-fonts \ |
29 msttcorefonts ttf-dejavu-core ttf-kochi-gothic ttf-kochi-mincho \ | 29 msttcorefonts ttf-dejavu-core fonts-ipafont \ |
30 ttf-thai-tlwg | 30 ttf-thai-tlwg |
31 ``` | 31 ``` |
32 | 32 |
33 You can also just run `build/install-build-deps.sh` again. | 33 You can also just run `build/install-build-deps.sh` again. |
34 | 34 |
35 ## Plugins | 35 ## Plugins |
36 | 36 |
37 If `fast/dom/object-plugin-hides-properties.html` and | 37 If `fast/dom/object-plugin-hides-properties.html` and |
38 `plugins/embed-attributes-style.html` are failing, try uninstalling | 38 `plugins/embed-attributes-style.html` are failing, try uninstalling |
39 `totem-mozilla` from your system: | 39 `totem-mozilla` from your system: |
(...skipping 88 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
128 In your `.xmonad/xmonad.hs`, change your config to include a manageHook along | 128 In your `.xmonad/xmonad.hs`, change your config to include a manageHook along |
129 these lines: | 129 these lines: |
130 | 130 |
131 ``` | 131 ``` |
132 test_shell_manage = className =? "Test_shell" --> doFloat | 132 test_shell_manage = className =? "Test_shell" --> doFloat |
133 main = xmonad $ | 133 main = xmonad $ |
134 defaultConfig | 134 defaultConfig |
135 { manageHook = test_shell_manage <+> manageHook defaultConfig | 135 { manageHook = test_shell_manage <+> manageHook defaultConfig |
136 ... | 136 ... |
137 ``` | 137 ``` |
OLD | NEW |