Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 This is a testharness.js-based test. | |
|
dcheng
2015/08/19 18:44:17
Since the imported tests are based on tests that a
| |
| 2 FAIL If there is one applet, it should be returned (name) assert_equals: expecte d (string) "test1" but got (undefined) undefined | |
| 3 FAIL If there are two applets, a collection should be returned. (name) assert_eq uals: expected (string) "test2" but got (undefined) undefined | |
| 4 FAIL If there is one applet, it should be returned (id) assert_true: "test3" in document should be true expected true got false | |
| 5 FAIL If there are two applets, a collection should be returned. (id) assert_true : "test4" in document should be true expected true got false | |
| 6 FAIL If there are two applets, a collection should be returned. (name and id) as sert_equals: expected (string) "test5" but got (undefined) undefined | |
| 7 FAIL If there are two applets, a collection should be returned. (id and name) as sert_equals: expected (string) "test6" but got (undefined) undefined | |
| 8 FAIL A name shouldn't affect getting an applet by id assert_true: "test7" in doc ument should be true expected true got false | |
| 9 FAIL An id shouldn't affect getting an applet by name assert_equals: expected (s tring) "test8" but got (undefined) undefined | |
| 10 Harness: the test ran to completion. | |
| 11 | |
| OLD | NEW |