It is possible to run basic layout tests using the content shell. The advantage over the test shell based DumpRenderTree is that content shell will exercise the multi-processing code paths used by chromium.
To just dump the render tree, as when calling DumpRenderTree directly, use the --dump-render-tree flag, as in:
If you want to run layout tests just build the content_shell target.
You can run layout tests using RWT
or execute the shell directly:
This allows you see how your changes look in Chromium, and even connect with the devtools (by going to http://127.0.0.1:9222 from another window) to inspect your freshly compiled Blink.
(Note: on the Mac, use "Content Shell", not "content_shell").
To debug a renderer crash, ask Content Shell to wait for you to attach a debugger once it spawns a renderer process by adding the --renderer-startup-dialog flag:
Debugging workers and other subprocesses is simpler with --wait-for-debugger-children, which can have one of two values: "plugin" or "renderer".
To avoid writing (and maintaining!) yet another test controller, it is desirable to reuse an existing test controller. A possible solution would be to change DRT's test controller to not depend on DRT's implementation of the Blink objects, but rather on the Blink interfaces. In addition, we would need to extract an interface from the test shell object that can be implemented by content shell. This would allow for directly using DRT's test controller in content shell.