Convert track-webvtt-tc[027-029] tests to testharness.js

third_party/WebKit/LayoutTests/media/track/track-webvtt-tc027-empty-cue-expected.txt

Index: third_party/WebKit/LayoutTests/media/track/track-webvtt-tc027-empty-cue-expected.txt
diff --git a/third_party/WebKit/LayoutTests/media/track/track-webvtt-tc027-empty-cue-expected.txt b/third_party/WebKit/LayoutTests/media/track/track-webvtt-tc027-empty-cue-expected.txt
index 027845dbbad696ea1978c34a6107960f19311543..ded6b9c8342c1efd48f63b4ee00b28b6871ba3b2 100644
--- a/third_party/WebKit/LayoutTests/media/track/track-webvtt-tc027-empty-cue-expected.txt
+++ b/third_party/WebKit/LayoutTests/media/track/track-webvtt-tc027-empty-cue-expected.txt
@@ -1,5 +1,4 @@
-Tests that empty cues are discarded.
-
-EXPECTED (video.textTracks[0].cues.length == '0'), OBSERVED '3' FAIL
-END OF TEST
+This is a testharness.js-based test.
+FAIL Check cues from captions-webvtt/tc027-empty-cue.vtt assert_equals: expected 0 but got 3

[Srirama, 2016/06/03 14:09:29]

There are few more tests with similar reason for failure. Digged a bit into it
thinking that i will fix it, but ended up outside blink here
(https://cs.chromium.org/chromium/src/third_party/libwebm/source/webvtt/webvtt...).

[fs, 2016/06/03 14:37:16]

The correct parser would be the one at core/html/track/vtt/VTTParser.cpp - this
test predates a change to the spec though, so you can just update the test to
expect 3 cues. (Looks like it was I that added the failing expectations...
164c59b7e86914c9a0eef9756ef6e8267bf13756)

[Srirama, 2016/06/03 17:54:23]

Done.

+Harness: the test ran to completion.