Much of the LayoutTest harness was in WebKit so it is used through abstractions that are no longer needed with it all being in content/ now.
content_shell is a testonly=true target because it always builds in layout test code, and content/test/ which allows it to circumvent the content/public/ APIs, so we can't have confidence that content public APIs are truly sufficient for content_shell.
We should
1) Avoid unneeded abstractions within the layout test code. Inject into production directly with interface overrides where needed.
2) Be able to build content_shell without include content/test/ or content/shell/.../layout_test/.
Comment 1 by bugdroid1@chromium.org
, Jul 27