tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Formalize asynchronous failure conditions 

Previously, the error message generated by failed asynchronous tests was
generic and underspecified. Improve the format and explicitly document
it in project's interpreting guidelines.
This commit is contained in:
Mike Pennisi 2018-05-20 15:15:48 -04:00
parent fbccd8eeff
commit 51bbcf59be
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
INTERPRETING.md
View File

@ -330,8 +330,9 @@ following strings:
considered complete until the implementation-defined `print` function has
been invoked or some length of time has passed without any such invocation.
In the event of a passing test run, this function will be invoked with the
string `'Test262:AsyncTestComplete'`. If invoked with any other value, the
test must be interpreted as failed. The implementation is free to select an
string `'Test262:AsyncTestComplete'`. If invoked with a string that is
prefixed with the character sequence `Test262:AsyncTestFailure:`, the test
must be interpreted as failed. The implementation is free to select an
appropriate length of time to wait before considering the test "timed out"
and failing.
@ -345,7 +346,7 @@ following strings:
.then(function() {
print('Test262:AsyncTestComplete');
}, function(reason) {
print('Error: ' + reason);
print('Test262:AsyncTestFailure: ' + reason);
});
```

2
harness/doneprintHandle.js
View File

@ -13,5 +13,5 @@ function $DONE(){
if(!arguments[0])
__consolePrintHandle__('Test262:AsyncTestComplete');
else
__consolePrintHandle__('Error: ' + arguments[0]);
__consolePrintHandle__('Test262:AsyncTestFailure:' + arguments[0]);
}