[chromium] move dumpAsText and friends to the TestRunner library
Created attachment 181511 [details] Patch
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Comment on attachment 181511 [details] Patch LGTM
I guess I don't understand all the pieces at play here. Are we building some c++ x-platform library "TestRunner" to share code between content_shell and test_shell? Or to share between all DRT ports? or?
(In reply to comment #4) > I guess I don't understand all the pieces at play here. > > Are we building some c++ x-platform library "TestRunner" to share code between content_shell and test_shell? Or to share between all DRT ports? or? It's a chromium only thing. First, we move all the testrunner objects into the TestRunner library which is already now used by DRT and content_shell. Assuming that's all done, and we have all tests covered, we can remove DRT and just keep the TestRunner library.
> Are we building some c++ x-platform library "TestRunner" to share code between content_shell and test_shell? Or to share between all DRT ports? or? I would love to build a cross-port lib for TestRunner, but unfortunately most of what the TestRunner lib does is interact with the port-specific WebKit API. As jochen says, the goal of these patches is to share code between DumpRenderTree and ContentShell so that we have only one implementation of TestRunner. Eventually we want to remove DumpRenderTree and a bunch of test-only code from Chromium.
Comment on attachment 181511 [details] Patch Clearing flags on attachment: 181511 Committed r138980: <http://trac.webkit.org/changeset/138980>
All reviewed patches have been landed. Closing bug.