Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(220)

Side by Side Diff: docs/layout_tests_linux.md

Issue 2505683002: Update links to layout test documentation. (Closed)
Patch Set: Use relative paths in markdown, and src-relative paths elsewhere. Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « docs/how_to_extend_layout_test_framework.md ('k') | media/tools/layout_tests/bug.py » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
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 [Layout Tests](testing/layout_tests.md)
14 [Running WebKit Layout Tests](http://dev.chromium.org/developers/testing/webkit- layout-tests)
15 for full documentation about set up and available options. 14 for full documentation about set up and available options.
16 15
17 ## Pixel Tests 16 ## Pixel Tests
18 17
19 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
20 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
21 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
22 `build/install-chroot.sh` to compile and run tests. 21 `build/install-chroot.sh` to compile and run tests.
23 22
24 ## Fonts 23 ## Fonts
(...skipping 104 matching lines...) Expand 10 before | Expand all | Expand 10 after
129 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
130 these lines: 129 these lines:
131 130
132 ``` 131 ```
133 test_shell_manage = className =? "Test_shell" --> doFloat 132 test_shell_manage = className =? "Test_shell" --> doFloat
134 main = xmonad $ 133 main = xmonad $
135 defaultConfig 134 defaultConfig
136 { manageHook = test_shell_manage <+> manageHook defaultConfig 135 { manageHook = test_shell_manage <+> manageHook defaultConfig
137 ... 136 ...
138 ``` 137 ```
OLDNEW
« no previous file with comments | « docs/how_to_extend_layout_test_framework.md ('k') | media/tools/layout_tests/bug.py » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698