mirror of https://github.com/tc39/test262.git
f225229f85
In these tests, cleanupSome() would have optionally emptied the FinalizationRegistry synchronously and called the finalization callbacks. Without cleanupSome(), there is no way to observe a FinalizationRegistry being emptied using "pure" ECMAScript: FinalizationRegistry doesn't get cleaned up until the microtask queue is empty, and without external APIs such as setTimeout() there is no way to pause execution until after the microtask queue is empty. Non-deterministic tests are not that useful anyway; these tests are probably better left to implementations' internal testing strategies. |
||
|---|---|---|
| .. | ||
| prototype | ||
| constructor.js | ||
| instance-extensible.js | ||
| is-a-constructor.js | ||
| length.js | ||
| name.js | ||
| newtarget-prototype-is-not-object.js | ||
| prop-desc.js | ||
| proto-from-ctor-realm.js | ||
| proto.js | ||
| prototype-from-newtarget-abrupt.js | ||
| prototype-from-newtarget-custom.js | ||
| prototype-from-newtarget.js | ||
| returns-new-object-from-constructor.js | ||
| target-not-callable-throws.js | ||
| undefined-newtarget-throws.js | ||
| unnaffected-by-poisoned-cleanupCallback.js | ||