Solution for browser tests outside of //chrome?

[Avi Drissman]

For browser tests outside of //chrome, we basically have them reuse the content browsertest classes. Specifically, the content API has https://source.chromium.org/chromium/chromium/src/+/main:content/public/test/content_browser_test.h.

However, that uses things like Shell, which means that just about every non-trivial browsertest has to specially DEPS in //content/shell.

https://source.chromium.org/search?q=file:components%20content::Shell&ss=chromium

Running this by you folks, but if we want to expose content::ContentBrowserTest in the content API, we should also expose enough of the pieces to let it be fully used without having to bypass the API.

Avi

[Avi Drissman]

Filed as https://crbug.com/383513680.

[Avi Drissman]

The other aspect that's weird is that Content Shell is an embedder of content/. content/'s API is content/public, and Content Shell's API is content/public/test, so even content, in its tests, should be accessing Content Shell via content/public/test.

Avi

[Avi Drissman]

Does anyone have context on content/web_test? That seems to be very intimately familiar with content shell, and I suppose it needs to go through content/public/test too.

[Avi Drissman]

I'm trying to get my head around the dependencies. My CL is https://crrev.com/c/6105882 wherein I'm trying to put shell.h into the testing public API and have a shell_impl.h implementing it, but looking at content/BUILD.gn is giving me a headache. Does anyone have advice here?

Avi