= Running Tests for WebKitGTK+ = == Dependencies == Ensure that you've followed [wiki:BuildingGtk all dependency installation instructions]. If you try to run tests without installing and updating both system and JHBuild (update-webkitgtk-libs) dependencies, it's likely that not all tests will pass. == Running the Tests == Simply run the `run-webkit-tests` script from the Tools directory. `run-webkit-tests` also supports the `--debug` argument to run the tests with the debug build of WebKitGTK+. {{{ ./Tools/Scripts/run-webkit-tests --gtk [--debug] }}} If you wish to run a single test you can do: {{{ ./Tools/Scripts/run-webkit-tests --gtk fast/forms/plaintext-mode-1.html }}} === Unit Tests === The GTK+ port includes unit tests. To run the suite: {{{ ./Tools/Scripts/run-gtk-tests [--debug] [--verbose] }}} If you wish to run a single test you can do: {{{ ./Tools/Scripts/run-gtk-tests WebKitBuild/Release/Programs/WebKit2APITests/TestContextMenu }}} === Pixel Tests === WebKitGTK+ supports running pixel tests, but they are not enabled by default. To run them simply pass the `-p` argument to `run-webkit-tests`: {{{ ./Tools/Scripts/run-webkit-tests --gtk -p }}} === Running Tests in GDB === For debugging a test it may be useful to run it directly in DumpRenderTree (with gdb): {{{ WebKitBuild/Debug/Programs/DumpRenderTree -v LayoutTests/fast/forms/plaintext-mode-1.html }}} == Common Problems == === chroot derived problems === There are some instructions to avoid common problems derived from having a [wiki:WebKitGTK/Chroot#Runningpythonbasedtestwithmultiprocesssupport chroot based working environment].