summaryrefslogtreecommitdiffstats
path: root/build
diff options
context:
space:
mode:
authorsky <sky@chromium.org>2016-03-21 09:38:30 -0700
committerCommit bot <commit-bot@chromium.org>2016-03-21 16:39:48 +0000
commit6e47685c9153b1d26ce5d2f955ebd6aea67e09d3 (patch)
tree241778bc6054cecdaf714078fdc76b853bc20ae2 /build
parentae7184b6f12adfa37ecca0fbae511aa68fa080e6 (diff)
downloadchromium_src-6e47685c9153b1d26ce5d2f955ebd6aea67e09d3.zip
chromium_src-6e47685c9153b1d26ce5d2f955ebd6aea67e09d3.tar.gz
chromium_src-6e47685c9153b1d26ce5d2f955ebd6aea67e09d3.tar.bz2
Adds option to run browser tests in mash
At a high level this is what the code does: . The test launcher creates MojoTestConnector. . MojoTestConnector creates a BackgroundShell (initially I wanted to run the shell on the same thread, but that is problematic because I need to run a nested message loop at times, which the IO thread doesn't support (the test launcher uses an io thread)). . A connection is established to mojo:mash_shell. . MojoTestConnector sets up the state for each test. The connect is not done with Mojo's child process connection. The base test launching code handles the actual process launching. Other random notes: . --single_process is a slightly different flow. . The test never finishes. This is because apps that are started don't all exit when the shell exits. I'm going to look at that next. R=ben@chromium.org, jam@chromium.org BUG=581733 Review URL: https://codereview.chromium.org/1806353003 Cr-Commit-Position: refs/heads/master@{#382305}
Diffstat (limited to 'build')
0 files changed, 0 insertions, 0 deletions