XR tests currently use testharness.js's async_test for all of its asserts. This makes it so the user has to wrap any asserts in a <test variable>.step() in order to work properly, which is both non-obvious to new users and adds bloat to the code.
I believe that testharness.js at some point added a way to specify that only one test would be run on a page, which removes the requirement of creating an async_test and wrapping asserts.
This bug is to track double checking that such functionality exists, and if so, whether it works correctly for XR tests.
Comment 1 by bugdroid1@chromium.org
, Nov 30