Revision 410fe8465f4c5a51d25d95c62a53b569d980c1cf authored by Robert Ma on 19 March 2018, 15:34:37 UTC, committed by Robert Ma on 19 March 2018, 15:34:37 UTC
Similar to #10030 (which was for `wpt run`), this commit makes `wpt check-stability` return a non-zero exit code when no tests run. Also fix some code smells: * `run` was redefined by `do_delayed_imports` to a different function. Rename the other `run` method in this module to `setup_and_run`. * `retcode` was unnecessarily defined in the top scope. Remove it to avoid redefinition. * `global logger` and the call to `get_parser` were extraneous in `run` (now `setup_and_run`) and hence are removed.
1 parent 9b3bb05
firing-events-http-no-content-length.html
<!doctype html>
<html>
<head>
<title>ProgressEvent: firing events for HTTP with no Content-Length</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<link rel="help" href="https://xhr.spec.whatwg.org/#firing-events-using-the-progressevent-interface">
</head>
<body>
<div id="log"></div>
<script>
var test = async_test();
test.step(function() {
var xhr = new XMLHttpRequest();
xhr.onprogress = function(pe) {
test.step(function() {
if(pe.type == "progress") {
assert_greater_than_equal(pe.loaded, 0, "loaded");
assert_false(pe.lengthComputable, "lengthComputable");
assert_equals(pe.total, 0, "total");
}
}, "Check lengthComputed, loaded, total when Content-Length is NOT given.");
}
// "loadstart", "error", "abort", "load" tests are out of scope.
// They SHOULD be tested in each spec that implement ProgressEvent.
xhr.onloadend = function(pe) {
test.done();
}
xhr.open("GET", "resources/trickle.py?ms=0&count=100", true);
xhr.send(null);
})
</script>
</body>
</html>
Computing file changes ...