third_party/WebKit/LayoutTests/webaudio/unit-tests/audit-failures-expected.txt - Issue 2568573002: Additional unit test for audit.js: failure cases and logging examples.

Side by Side Diff: third_party/WebKit/LayoutTests/webaudio/unit-tests/audit-failures-expected.txt

Issue 2568573002: Additional unit test for audit.js: failure cases and logging examples. (Closed)

Patch Set: Adding expected result Created 4 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

« third_party/WebKit/LayoutTests/webaudio/unit-tests/audit-failures.html ('K') | « third_party/WebKit/LayoutTests/webaudio/unit-tests/audit-failures.html ('k') | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 This is a testharness.js-based test.

	2 PASS # AUDIT TASK RUNNER STARTED.

	3 PASS > [basic-failure] Testing basic assertion failures.

	4 FAIL X Setting foo to bar INCORRECTLY threw ReferenceError: "bar is not define d". assert_true: expected true got false

	5 FAIL X function () { var foo = 0; } did NOT throw an exception. assert_true: e xpected true got false

	6 FAIL X 3 < 5 is NOT true. assert_true: expected true got false

	7 FAIL X true is NOT false. assert_true: expected true got false

	8 FAIL X 1 is NOT equal to 2. assert_true: expected true got false

	9 FAIL X 1 should NOT be equal to 1. assert_true: expected true got false

	10 FAIL X number is NOT equal to string. assert_true: expected true got false

	11 FAIL X 1 is NOT greater than 2. assert_true: expected true got false

	12 FAIL X 1 is NOT greater than or equal to 2. assert_true: expected true got fal se

	13 FAIL X 2 is NOT less than 1. assert_true: expected true got false

	14 FAIL X 2 is NOT less than or equal to 1. assert_true: expected true got false

	15 FAIL X Start OAC rendering rejected INCORRECTLY with TypeError: Failed to exec ute 'decodeAudioData' on 'BaseAudioContext': 1 argument required, but only 0 pre sent.. assert_true: expected true got false

	16 FAIL X undefined resolved INCORRECTLY. assert_true: expected true got false
	Raymond Toy 2016/12/09 22:10:26 This test needs a better description because "unde This test needs a better description because "undefined" has no meaning in the context of this message. How does "undefined" resolve? hongchan 2016/12/19 22:14:06 In this case, the author needs to provide the desc Show quoted text On 2016/12/09 22:10:26, Raymond Toy wrote: > This test needs a better description because "undefined" has no meaning in the > context of this message. How does "undefined" resolve? In this case, the author needs to provide the description. I missed it. We decided not to generate the description automatically so it simply prints the evaluated value here.
	17 FAIL < [basic-failure] 13 out of 13 assertions were failed. assert_true: expecte d true got false

	18 PASS > [numerical-failures] Testing numerical assertion failures.

	19 FAIL X 0 is NOT 0.1 within an error of 0: 0 with error of 0. assert_true: expe cted true got false
	Raymond Toy 2016/12/09 22:10:26 This message looks wrong: "0 with error of 0". It This message looks wrong: "0 with error of 0". It ought to be rephrased in some way. hongchan 2016/12/19 22:14:05 Can you suggest something? This error message was Show quoted text On 2016/12/09 22:10:26, Raymond Toy wrote: > This message looks wrong: "0 with error of 0". It ought to be rephrased in some > way. Can you suggest something? This error message was written by you a while ago.
	20 FAIL X [1,8,11,18,6,5,5,5,123,49] contains 7 values that are NOT equal to 5:
	Raymond Toy 2016/12/09 22:10:26 This error message isn't the best because it's har This error message isn't the best because it's hard to tell that you're really expecting 5 for all values. Can we rephrase that? hongchan 2016/12/19 22:14:06 Done. Show quoted text On 2016/12/09 22:10:26, Raymond Toy wrote: > This error message isn't the best because it's hard to tell that you're really > expecting 5 for all values. Can we rephrase that? Done.
	21 Index Actual

	22 [0] 1

	23 [1] 8

	24 [2] 11

	25 [3] 18

	26 ...and 3 more errors. assert_true: expected true got false

	27 FAIL X [1,8,11,18,6,5,5,5,123,49] contains 3 values that are NOT equal to [1,8 ,10,18,6,5,6,5,123,48]:
	Raymond Toy 2016/12/09 22:10:26 This is badly phrased as well. Perhaps it's bette This is badly phrased as well. Perhaps it's better to say: [...] expected to be equal to [...] but differs in 3 places: hongchan 2016/12/19 22:14:06 Done. Show quoted text On 2016/12/09 22:10:26, Raymond Toy wrote: > This is badly phrased as well. Perhaps it's better to say: > > [...] expected to be equal to [...] but differs in 3 places: Done.
	28 Index Actual Expected

	29 [2] 1.1000000000000000e+1 1.0000000000000000e+1

	30 [6] 5.0000000000000000e+0 6.0000000000000000e+0

	31 [9] 4.9000000000000000e+1 4.8000000000000000e+1 assert_true: expec ted true got false

	32 FAIL X [1,1,1,1,2,2,3,3,3] contains an UNEXPECTED value of 3 at index 6. asser t_true: expected true got false
	Raymond Toy 2016/12/09 22:10:26 This could be better phrased too because you can't This could be better phrased too because you can't tell what the actual output was supposed to be. Maybe: [...] expected to be [1..., 3..., 2...] but got 3 at index 6. And shouldn't the error message say that 2 was unexpected at index 4? hongchan 2016/12/19 22:14:05 So we want the first instance of error. Right? I n Show quoted text On 2016/12/09 22:10:26, Raymond Toy wrote: > This could be better phrased too because you can't tell what the actual output > was supposed to be. Maybe: > > [...] expected to be [1..., 3..., 2...] but got 3 at index 6. > > And shouldn't the error message say that 2 was unexpected at index 4? So we want the first instance of error. Right? I need to think about the algorithm for that.
	33 FAIL X [0.5,0.5,0.55,0.5,0.45,0.5] has a GLITCH at index 5 of size 0.049999999 99999999. assert_true: expected true got false

	34 FAIL X [0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.9] does NOT equal [0.7,0.6,0.5,0.4,0.3,0 .2,0.1] with an element-wise tolerance of {"absoluteThreshold":0.02,"relativeThr eshold":0.1}.

	35 Index Actual Expected AbsError RelError Test threshold

	36 [0] 1.0000000000000001e-1 6.9999999999999996e-1 5.99999999999999 98e-1 8.5714285714285721e-1 6.9999999999999993e-2

	37 [1] 2.0000000000000001e-1 5.9999999999999998e-1 3.99999999999999 97e-1 6.6666666666666663e-1 5.9999999999999998e-2

	38 [2] 2.9999999999999999e-1 5.0000000000000000e-1 2.00000000000000 01e-1 4.0000000000000002e-1 5.0000000000000003e-2

	39 [4] 5.0000000000000000e-1 2.9999999999999999e-1 2.00000000000000 01e-1 6.6666666666666674e-1 2.9999999999999999e-2

	40 [5] 5.9999999999999998e-1 2.0000000000000001e-1 3.99999999999999 97e-1 1.9999999999999998e+0 2.0000000000000004e-2

	41 Max AbsError of 5.9999999999999998e-1 at index of 0.

	42 Max RelError of 5.9999999999999991e+0 at index of 6. assert_true: expect ed true got false

	43 FAIL < [numerical-failures] 6 out of 6 assertions were failed. assert_true: expe cted true got false

	44 FAIL # AUDIT TASK RUNNER FINISHED: 2 out of 2 tasks were failed. assert_true: ex pected true got false

	45 Harness: the test ran to completion.

	46

OLD	NEW