Difference between revisions of "Cue Times"

From CDOT Wiki
Jump to: navigation, search
(Dale: updating github repo url)
(Vince: peer review)
Line 79: Line 79:
 
|
 
|
 
|
 
|
|
+
|Dale, Sept 26 2012
 
|-
 
|-
 
|bad02.vtt
 
|bad02.vtt
Line 87: Line 87:
 
|
 
|
 
|
 
|
|
+
|Dale, Sept 26 2012
 
|-
 
|-
 
|bad03.vtt
 
|bad03.vtt
Line 95: Line 95:
 
|
 
|
 
|Took out the -->
 
|Took out the -->
|
+
|Dale, Sept 26 2012
 
|-
 
|-
 
|bad04.vtt
 
|bad04.vtt
Line 103: Line 103:
 
|
 
|
 
|
 
|
|
+
|Dale, Sept 26 2012
 
|-
 
|-
 
|bad05.vtt
 
|bad05.vtt
Line 111: Line 111:
 
|
 
|
 
|
 
|
|
+
|Dale, Sept 26 2012
 
|-
 
|-
 
|bad06.vtt
 
|bad06.vtt
Line 119: Line 119:
 
|
 
|
 
|
 
|
|
+
|Dale, Sept 26 2012
 
|-
 
|-
 
|}
 
|}
 
'''TODO:''' Break hour, see if days work, create multiple cue times that don't make sense (first cue at 2 minutes, second at 1 minute)
 
'''TODO:''' Break hour, see if days work, create multiple cue times that don't make sense (first cue at 2 minutes, second at 1 minute)

Revision as of 07:53, 26 September 2012

Group Members

  • Vince Lee
  • Thevakaran Virutthasalam
  • Dale Karp

Test Ideas

  • Syntax
  • Single cue tests
    • Times out of order
  • Multiple cue tests
    • Nested cues
    • Overlapping cues
    • Cue times out of order

Testing Procedure

Writing Tests

  1. Check if the test you have in mind exists already in the wiki
  2. If not, write your test case file
  3. When you finish writing, document the test case in the wiki ASAP so you don't forget!
  4. Commit your test case to the github repo

Peer Review

  1. Review someone else's test case
  2. Sign off in the 'Peer Review' column of the table with your name so that we know it's been looked at (TO DO: Create Peer Review column in tables)

Cue Time Syntax Rules

  1. A WebVTT timestamp representing the start time offset of the cue. The time represented by this WebVTT timestamp must be greater than or equal to the start time offsets of all previous cues in the file.
  2. One or more U+0020 SPACE characters or U+0009 CHARACTER TABULATION (tab) characters.
  3. The string "-->" (U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS, U+003E GREATER-THAN SIGN).
  4. One or more U+0020 SPACE characters or U+0009 CHARACTER TABULATION (tab) characters.
  5. A WebVTT timestamp representing the end time offset of the cue. The time represented by this WebVTT timestamp must be greater than the start time offset of the cue.

Tests

Dale

URL to git repo with tests: https://github.com/daliuss/webvtt/tree/master/test/spec

Filename Description Should Pass / Fail? Reasoning Creation Note Comments Peer Review
cuetime_bareminimum.vtt Bare minimum file that passes (no cue content) Pass Conforms to spec ST2
cuetime_bareminimum_content.vtt Bare minimum file that passes (cue content) Pass Conforms to spec ST2

Vince

I'm gonna remake the table using markdown. Hitting <td></td> is tedious

Filename Description Should Pass / Fail? Reasoning Creation Note Comments Peer Review
bad01.vtt 00:00.000 --> 00:00.000 Fail End timestamp must be greater than start timestamp Dale, Sept 26 2012
bad02.vtt 00:00.001 --> 00:00.000 Fail End timestamp must be greater than start timestamp Dale, Sept 26 2012
bad03.vtt 00:00.000 00:00.001 Fail Timestamp separator not found Took out the --> Dale, Sept 26 2012
bad04.vtt 00:00.0000 --> 00:00.001 Fail Milliseconds must be 3 digits Dale, Sept 26 2012
bad05.vtt 00:000.000 --> 00:00.001 Fail Seconds should be 2 digits Dale, Sept 26 2012
bad06.vtt 000:00.000 --> 00:00.001 Fail Minutes should be 2 digits Dale, Sept 26 2012

TODO: Break hour, see if days work, create multiple cue times that don't make sense (first cue at 2 minutes, second at 1 minute)