Ping on this (although sync up with Peter to see if we have something reasonable)

We don't have an integration test which uses WebappLauncherActivity. This request still stands

It looks like ChromeActivityTestRule#startActivityCompletely() waits till a ChromeActivity gets created. I think that you can call that method with an intent to WebappLauncherActivity and things will "just work"

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ddbc1a049317170cd1e2477e0dd002ba5b6f00cb

commit ddbc1a049317170cd1e2477e0dd002ba5b6f00cb
Author: Ran Ji <ranj@chromium.org>
Date: Mon Jan 15 20:46:42 2018

Write WebAPK integration test which uses WebappLauncherActivity

Bug:  735772 
Change-Id: Ie4d2d4ac27de9ff3cbfd2058dcb1eeb09d975d44
Reviewed-on: https://chromium-review.googlesource.com/851138
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Commit-Queue: Ran Ji <ranj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#529327}
[modify] https://crrev.com/ddbc1a049317170cd1e2477e0dd002ba5b6f00cb/chrome/android/javatests/src/org/chromium/chrome/browser/webapps/WebApkIntegrationTest.java