Make asynchronous test configuration explicit
For asynchronous tests, the contract between test file and test runner is implicit: runners are expected to inspect the source code for references to a global `$DONE` identifier. Promote a more explicit contract between test file and test runner by introducing a new frontmatter "tag", `async`. This brings asynchronous test configuration in-line with other configuration mechanisms and also provides a more natural means of test filtering. The modifications to test files was made programatically using the `grep` and `sed` utilities: $ grep "\$DONE" test/ -r --files-with-match --null | \ xargs -0 sed -i 's/^\(flags:\s*\)\[/\1[async, /g' $ grep "\$DONE" test/ -rl --null | \ xargs -0 grep -E '^flags:' --files-without-match --null | \ xargs -0 sed -i 's/^---\*\//flags: [async]\n---*\//'
Showing
- test/built-ins/Promise/prototype/then/resolve-pending-fulfilled-thenable.js 1 addition, 0 deletions...mise/prototype/then/resolve-pending-fulfilled-thenable.js
- test/built-ins/Promise/prototype/then/resolve-pending-rejected-non-obj.js 1 addition, 0 deletions...romise/prototype/then/resolve-pending-rejected-non-obj.js
- test/built-ins/Promise/prototype/then/resolve-pending-rejected-non-thenable.js 1 addition, 0 deletions...e/prototype/then/resolve-pending-rejected-non-thenable.js
- test/built-ins/Promise/prototype/then/resolve-pending-rejected-poisoned-then.js 1 addition, 0 deletions.../prototype/then/resolve-pending-rejected-poisoned-then.js
- test/built-ins/Promise/prototype/then/resolve-pending-rejected-self.js 1 addition, 0 deletions...s/Promise/prototype/then/resolve-pending-rejected-self.js
- test/built-ins/Promise/prototype/then/resolve-pending-rejected-thenable.js 1 addition, 0 deletions...omise/prototype/then/resolve-pending-rejected-thenable.js
- test/built-ins/Promise/prototype/then/resolve-settled-fulfilled-non-obj.js 1 addition, 0 deletions...omise/prototype/then/resolve-settled-fulfilled-non-obj.js
- test/built-ins/Promise/prototype/then/resolve-settled-fulfilled-non-thenable.js 1 addition, 0 deletions.../prototype/then/resolve-settled-fulfilled-non-thenable.js
- test/built-ins/Promise/prototype/then/resolve-settled-fulfilled-poisoned-then.js 1 addition, 0 deletions...prototype/then/resolve-settled-fulfilled-poisoned-then.js
- test/built-ins/Promise/prototype/then/resolve-settled-fulfilled-self.js 1 addition, 0 deletions.../Promise/prototype/then/resolve-settled-fulfilled-self.js
- test/built-ins/Promise/prototype/then/resolve-settled-fulfilled-thenable.js 1 addition, 0 deletions...mise/prototype/then/resolve-settled-fulfilled-thenable.js
- test/built-ins/Promise/prototype/then/resolve-settled-rejected-non-obj.js 1 addition, 0 deletions...romise/prototype/then/resolve-settled-rejected-non-obj.js
- test/built-ins/Promise/prototype/then/resolve-settled-rejected-non-thenable.js 1 addition, 0 deletions...e/prototype/then/resolve-settled-rejected-non-thenable.js
- test/built-ins/Promise/prototype/then/resolve-settled-rejected-poisoned-then.js 1 addition, 0 deletions.../prototype/then/resolve-settled-rejected-poisoned-then.js
- test/built-ins/Promise/prototype/then/resolve-settled-rejected-self.js 1 addition, 0 deletions...s/Promise/prototype/then/resolve-settled-rejected-self.js
- test/built-ins/Promise/prototype/then/resolve-settled-rejected-thenable.js 1 addition, 0 deletions...omise/prototype/then/resolve-settled-rejected-thenable.js
- test/built-ins/Promise/prototype/then/rxn-handler-fulfilled-invoke-nonstrict.js 1 addition, 1 deletion.../prototype/then/rxn-handler-fulfilled-invoke-nonstrict.js
- test/built-ins/Promise/prototype/then/rxn-handler-fulfilled-invoke-strict.js 1 addition, 1 deletion...ise/prototype/then/rxn-handler-fulfilled-invoke-strict.js
- test/built-ins/Promise/prototype/then/rxn-handler-fulfilled-next-abrupt.js 1 addition, 0 deletions...omise/prototype/then/rxn-handler-fulfilled-next-abrupt.js
- test/built-ins/Promise/prototype/then/rxn-handler-fulfilled-next.js 1 addition, 0 deletions...-ins/Promise/prototype/then/rxn-handler-fulfilled-next.js
Loading
Please register or sign in to comment