blink_tests
(see Linux-specific build instructions).gclient
file that includes “web_tests”, you may need to comment it out and sync.src/third_party/blink/web_tests/
. For example, third_party/blink/tools/run_web_tests.py fast
will only run the tests under src/third_party/blink/web_tests/fast/
.See Web Tests for full documentation about set up and available options.
The pixel test results were generated on Ubuntu 10.4 (Lucid). If you're running a newer version of Ubuntu, you will get some pixel test failures due to changes in freetype or fonts. In this case, you can create a Lucid 64 chroot using build/install-chroot.sh
to compile and run tests.
build/install-build-deps.sh
ls third_party/test_fonts/test_fonts/
is not empty and lists the fonts downloaded through the test_fonts
hook in the top level DEPS
file.
If fast/dom/object-plugin-hides-properties.html
and plugins/embed-attributes-style.html
are failing, try uninstalling totem-mozilla
from your system:
sudo apt-get remove totem-mozilla
Use an optimized content_shell
when rebaselining or running a lot of tests. (bug 8475 is about how the debug output differs from the optimized output.)
ninja -C out/Release content_shell
Make sure you have wdiff installed: sudo apt-get install wdiff
to get prettier diff output.
Some pixel tests may fail due to processor-specific rounding errors. Build using a chroot jail with Lucid 64-bit user space to be sure that your system matches the checked in baselines. You can use build/install-chroot.sh
to set up a Lucid 64 chroot. Learn more about using a linux chroot.
There are two ways:
content_shell
directly rather than using run_web_tests.py
. You will need to pass some options:--no-timeout
to give you plenty of time to debugblink/web_tests
).--additional-drt-flag=--renderer-startup-dialog --additional-drt-flag=--no-timeout --timeout-ms=86400000
flags. The first one makes content_shell bring up a dialog before running, which then would let you attach to the process via gdb -p PID_OF_DUMPRENDERTREE
. The others help avoid the test shell and DumpRenderTree timeouts during the debug session.If you try to use your computer while the tests are running, you may get annoyed as windows are opened and closed automatically. To get around this, you can create a separate X server for running the tests.
sudo apt-get install xserver-xephyr
)Xephyr :4 -screen 1024x768x24
DISPLAY=:4 run_web_tests.py
Xephyr supports debugging repainting. See the Xephyr README for details. In brief:
XEPHYR_PAUSE=$((500*1000)) Xephyr ...etc... # 500 ms repaint flash
kill -USR1 $(pidof Xephyr)
If you don't want to see anything at all, you can use Xvfb (should already be installed).
Xvfb :4 -screen 0 1024x768x24
DISPLAY=:4 run_web_tests.py
The web tests want to run with the window at a particular size down to the pixel level. This means if your window manager resizes the window it'll cause test failures. This is another good reason to use an embedded X server.
In your .xmonad/xmonad.hs
, change your config to include a manageHook along these lines:
test_shell_manage = className =? "Test_shell" --> doFloat main = xmonad $ defaultConfig { manageHook = test_shell_manage <+> manageHook defaultConfig ...