Chromium Code Reviews (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out

Unified Diff: LayoutTests/fast/harness/should-be-now-expected.txt

Issue 69813015: Add shouldBeNow() to js-tests.js in LayoutTests. (Closed) Base URL:
Patch Set: Rebased against master. Created 7 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: LayoutTests/fast/harness/should-be-now-expected.txt
diff --git a/LayoutTests/fast/harness/should-be-now-expected.txt b/LayoutTests/fast/harness/should-be-now-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..78aeb260bb54c3785c70c4d9e103eeed89cc3168
--- /dev/null
+++ b/LayoutTests/fast/harness/should-be-now-expected.txt
@@ -0,0 +1,19 @@
+Test shouldBeNow() in js-test.js
+On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
+PASS is equivalent to
+PASS new Date() is equivalent to
+Testing type checking with a string. This should fail.
+FAIL 'Hello world!' is not a number or a Date. Got Hello world!
+Testing past dates. This should fail.
+FAIL 50000 is not the curent time. Got 50000 which is 10 seconds in the past.
+Testing future dates. This should fail.
+FAIL 70000 is not the current time. Got 70000 which is 10 seconds in the future.
+Simulating a defective clock that always goes backwards. The test below should fail.
+FAIL new Date() cannot be tested against the current time. The clock is going backwards too often.
+PASS successfullyParsed is true

Powered by Google App Engine
This is Rietveld 408576698