Import wpt@40665266227e475bc4a56884247d8c09d78dfb6a

third_party/WebKit/LayoutTests/external/wpt/streams/resources/test-utils.js

 'use strict';
 
 self.getterRejects = (t, obj, getterName, target) => {
   const getter = Object.getOwnPropertyDescriptor(obj, getterName).get;
 
   return promise_rejects(t, new TypeError(), getter.call(target));
 };
 
-self.methodRejects = (t, obj, methodName, target) => {
+self.methodRejects = (t, obj, methodName, target, args) => {
   const method = obj[methodName];
 
-  return promise_rejects(t, new TypeError(), method.call(target));
+  return promise_rejects(t, new TypeError(), method.apply(target, args));
 };
 
 self.getterThrows = (obj, getterName, target) => {
   const getter = Object.getOwnPropertyDescriptor(obj, getterName).get;
 
   assert_throws(new TypeError(), () => getter.call(target), getterName + ' should throw a TypeError');
 };
 
 self.methodThrows = (obj, methodName, target, args) => {
   const method = obj[methodName];
@@ skipping 11 matching lines @@
     GCController.collect();
   } else {
     /* eslint-disable no-console */
     console.warn('Tests are running without the ability to do manual garbage collection. They will still work, but ' +
       'coverage will be suboptimal.');
     /* eslint-enable no-console */
   }
 };
 
 self.delay = ms => new Promise(resolve => step_timeout(resolve, ms));
+
+// For tests which verify that the implementation doesn't do something it shouldn't, it's better not to use a
+// timeout. Instead, assume that any reasonable implementation is going to finish work after 2 times around the event
+// loop, and use flushAsyncEvents().then(() => assert_array_equals(...));
+// Some tests include promise resolutions which may mean the test code takes a couple of event loop visits itself. So go
+// around an extra 2 times to avoid complicating those tests.
+self.flushAsyncEvents = () => delay(0).then(() => delay(0)).then(() => delay(0)).then(() => delay(0));