Currently, the WebVR tests us vr_test, which is a wrapper around async_test. Since WebVR uses promises heavily, we should use the promise_test mechanism. This should simplify the tests since we don't need to catch every rejection.
When we first implemented WebVR tests for the 1.1 API, there was a problem where promise tests could unintentionally pass. We should check whether this is still the case, and if so, how we can mitigate this.
Comment 1 by ddorwin@chromium.org
, Nov 17 2017