Can you elaborate a little more on the issue?

The original issue was that GPU benchmarking was queueing some tasks and then test would say done and then GPU benchmarking tasks were causing leaks. So we had to wait until GPU benchmarking instructions are done as well. Also some of pointerevent tests have a notion of running the same test multiple times. So we have a series of async tests but this automation test wraps them all.

I understand you want to ensure testharness waits for  input injection to be completed regardless of the tests.

At the moment, your solution is to create a fake test:

var pointerevent_automation = async_test("PointerEvent Automation");
  // Defined in every test and should return a promise that gets resolved when input is finished.
  inject_input().then(function() {
    pointerevent_automation.done();
  });


IMHO a better solution is to use explicit_done which causes the harness to wait for global done before considering test to be finished.

i.e.,


explicit_done = true;
inject_input().then(function() {
  done();
});

This avoids the fake test that can cause problem and is more idiomatic.

I don't understand how this automation test wraps other tests can you elaborate and give and example.

nit: It should be setup({ "explicit_done": true });

The explicit_done doesn't resolve the issue. This is one example test:
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/external/wpt/pointerevents/pointerevent_change-touch-action-onpointerdown_touch-manual.html?q=explicit_done+file:%5Esrc/third_party/WebKit/LayoutTests/external/wpt/pointerevents/+package:%5Echromium$&dr=C&l=91

which also uses explicit_done and was causing the leak at the time before that change. The catch is that the test is calling done while GPU benchmarking was working.