Make test_transitions report either PASS or TODO for its timing-related tests since we just can't test timing on the unit test VMs. (Bug 522862)

This commit is contained in:
L. David Baron 2009-10-24 18:47:29 -04:00
Родитель 0a9a7468eb
Коммит 30951ee57e
1 изменённых файлов: 5 добавлений и 2 удалений

Просмотреть файл

@ -452,7 +452,7 @@ function check_ref_range()
// This is the only test where we compare the progress of the
// transitions to an actual time; we need considerable tolerance at
// the low end (we are using half a second).
var expected_range = [ (gCurrentTime - gStartTime2 - 750) / 8,
var expected_range = [ (gCurrentTime - gStartTime2 - 40) / 8,
(Date.now() - gStartTime1 + 20) / 8 ];
if (expected_range[0] > 1000) {
expected_range[0] = 1000;
@ -461,7 +461,10 @@ function check_ref_range()
expected_range[1] = 1000;
}
function check(desc, value) {
ok(expected_range[0] <= value && value <= expected_range[1],
// The timing on the unit test VMs is not reliable, so make this
// test report PASS when it succeeds and TODO when it fails.
var passed = expected_range[0] <= value && value <= expected_range[1];
(passed ? ok : todo)(passed,
desc + ": computed value " + value + "px should be between " +
expected_range[0].toFixed(6) + "px and " +
expected_range[1].toFixed(6) + "px at time between " +