In the process of Device Service development, while we're removing some browsertests for device features(battery, vibration etc.), we noticed that some end-to-end tests are still necessary. Although we have blink layout tests to verify JS API behavior inside renderer and service tests to verify mojo interfaces implemented correctly inside Device Service, there is still a gap:
We're lack of verifying those mojo interfaces are really registered/exposed to their clients correctly in a real browser environment, that is to say, whether clients can always connect to those mojo interfaces well even if sometimes service manager infra would change. And of course, such end-to-end test should not depend on any internal implementations of Device Service.
We need an infra to support such end-to-end test, not only for Device Service, but for other services in general.
Discussions detail: https://groups.google.com/a/chromium.org/forum/#!topic/services-dev/lJCKAElWz-E
Comment 1 by leon....@intel.com
, May 2 2017