Difference between revisions of "OSD600/webvtt/cue settings"
(→"position", "size" & "align" settings) |
(→"position", "size" & "align" settings) |
||
| Line 32: | Line 32: | ||
00:11.000 --> 00:13.000 :10% | 00:11.000 --> 00:13.000 :10% | ||
| − | |||
| − | |||
*no cue setting | *no cue setting | ||
| Line 40: | Line 38: | ||
00:11.000 --> 00:13.000 position:10% | 00:11.000 --> 00:13.000 position:10% | ||
| − | |||
*positive test (should succeed) | *positive test (should succeed) | ||
| Line 47: | Line 44: | ||
00:11.000 --> 00:13.000 position:A% | 00:11.000 --> 00:13.000 position:A% | ||
| − | |||
*character above utf-8+0039 | *character above utf-8+0039 | ||
**NOTE: the parser currently passes this test instead of failing it | **NOTE: the parser currently passes this test instead of failing it | ||
| Line 55: | Line 51: | ||
00:11.000 --> 00:13.000 position:+% | 00:11.000 --> 00:13.000 position:+% | ||
| − | |||
*character below utf-8+0030 | *character below utf-8+0030 | ||
**NOTE: the parser currently passes this test instead of failing it | **NOTE: the parser currently passes this test instead of failing it | ||
| Line 63: | Line 58: | ||
00:11.000 --> 00:13.000 position10% | 00:11.000 --> 00:13.000 position10% | ||
| − | |||
*':' missing in between cue setting and value | *':' missing in between cue setting and value | ||
| Line 70: | Line 64: | ||
00:11.000 --> 00:13.000 position:10 | 00:11.000 --> 00:13.000 position:10 | ||
| − | |||
*'%' missing at the end | *'%' missing at the end | ||
| Line 79: | Line 72: | ||
00:11.000 --> 00:13.000 size:10% | 00:11.000 --> 00:13.000 size:10% | ||
| − | |||
*positive test (should succeed) | *positive test (should succeed) | ||
| Line 86: | Line 78: | ||
00:11.000 --> 00:13.000 size:A% | 00:11.000 --> 00:13.000 size:A% | ||
| − | |||
*character above utf-8+0039 | *character above utf-8+0039 | ||
**NOTE: the parser currently passes this test instead of failing it | **NOTE: the parser currently passes this test instead of failing it | ||
| Line 94: | Line 85: | ||
00:11.000 --> 00:13.000 size:+% | 00:11.000 --> 00:13.000 size:+% | ||
| − | |||
*character below utf-8+0030 | *character below utf-8+0030 | ||
**NOTE: the parser currently passes this test instead of failing it | **NOTE: the parser currently passes this test instead of failing it | ||
| Line 102: | Line 92: | ||
00:11.000 --> 00:13.000 size10% | 00:11.000 --> 00:13.000 size10% | ||
| − | |||
*':' missing in between cue setting and value | *':' missing in between cue setting and value | ||
| Line 109: | Line 98: | ||
00:11.000 --> 00:13.000 size:10 | 00:11.000 --> 00:13.000 size:10 | ||
| − | |||
*'%' missing at the end | *'%' missing at the end | ||
| Line 118: | Line 106: | ||
00:11.000 --> 00:13.000 :start | 00:11.000 --> 00:13.000 :start | ||
| − | |||
*no cue setting | *no cue setting | ||
| Line 125: | Line 112: | ||
00:11.000 --> 00:13.000 align:start | 00:11.000 --> 00:13.000 align:start | ||
| − | |||
*positive test (should succeed) | *positive test (should succeed) | ||
| Line 132: | Line 118: | ||
00:11.000 --> 00:13.000 align:middle | 00:11.000 --> 00:13.000 align:middle | ||
| − | |||
*positive test (should succeed) | *positive test (should succeed) | ||
| Line 139: | Line 124: | ||
00:11.000 --> 00:13.000 align:end | 00:11.000 --> 00:13.000 align:end | ||
| − | |||
*positive test (should succeed) | *positive test (should succeed) | ||
| Line 146: | Line 130: | ||
00:11.000 --> 00:13.000 align:star | 00:11.000 --> 00:13.000 align:star | ||
| − | |||
*test misspelling of one of the possible values | *test misspelling of one of the possible values | ||
| Line 153: | Line 136: | ||
00:11.000 --> 00:13.000 align: | 00:11.000 --> 00:13.000 align: | ||
| − | |||
*test missing value | *test missing value | ||
| Line 160: | Line 142: | ||
These tests look okay, but just one thing to point out, the draft does require that a cue has a cue payload (eg, the text content of the subtitle), so if they weren't in the actual test files, they need to be added in so that we're only testing the pass/fail of the specific conditions we're looking at. | These tests look okay, but just one thing to point out, the draft does require that a cue has a cue payload (eg, the text content of the subtitle), so if they weren't in the actual test files, they need to be added in so that we're only testing the pass/fail of the specific conditions we're looking at. | ||
| − | |||
Latest revision as of 20:07, 25 September 2012
Contents
Cue Settings Tests
"vertical" & "line" settings
09/23/2012
Download: caitp-cue_settings_tests-09232012.tgz
Discussion:
"position", "size" & "align" settings
Note: Hi Caitlin here are the tests I've come up with so far for the position, size and align cue settings. I have a few concerns about some of the things I saw in the parser so if you could help me test them it would be great.
Some notable things I've discovered:
- 00:11.000 --> 00:13.000position:10% passes
- there is no space between the cue setting and the cue timing. this is a problem with the toy parser, because the draft requires one or more whitespace characters ([U+0020 || U+0009]) between the timestamp and the cue setting (and between each subsequent cue setting)
- 00:11.000 --> 00:13.000 position:A% passes
- any character besides ' ' (space) between : and % will pass. This is another problem with the toy parser, as the draft defines that the text between ':' and '%' must be in the U+0030-U+0039 range (ASCII digits)
A few things to note about the tests:
- The first test for position is the absence of the cue setting tag, I think technically this test should work for the rest of the tests that use the :n% format as well hence its absence in the size tests.
- I have a test for each cue setting type where the ':' is missing, what do you think about this? I have been thinking that only one for all the cue settings would be enough as this simply tests the parser for whether it can split setting from value.
Position
WEBVTT
00:11.000 --> 00:13.000 :10%
- no cue setting
WEBVTT
00:11.000 --> 00:13.000 position:10%
- positive test (should succeed)
WEBVTT
00:11.000 --> 00:13.000 position:A%
- character above utf-8+0039
- NOTE: the parser currently passes this test instead of failing it
WEBVTT
00:11.000 --> 00:13.000 position:+%
- character below utf-8+0030
- NOTE: the parser currently passes this test instead of failing it
WEBVTT
00:11.000 --> 00:13.000 position10%
- ':' missing in between cue setting and value
WEBVTT
00:11.000 --> 00:13.000 position:10
- '%' missing at the end
Size
WEBVTT
00:11.000 --> 00:13.000 size:10%
- positive test (should succeed)
WEBVTT
00:11.000 --> 00:13.000 size:A%
- character above utf-8+0039
- NOTE: the parser currently passes this test instead of failing it
WEBVTT
00:11.000 --> 00:13.000 size:+%
- character below utf-8+0030
- NOTE: the parser currently passes this test instead of failing it
WEBVTT
00:11.000 --> 00:13.000 size10%
- ':' missing in between cue setting and value
WEBVTT
00:11.000 --> 00:13.000 size:10
- '%' missing at the end
Align
WEBVTT
00:11.000 --> 00:13.000 :start
- no cue setting
WEBVTT
00:11.000 --> 00:13.000 align:start
- positive test (should succeed)
WEBVTT
00:11.000 --> 00:13.000 align:middle
- positive test (should succeed)
WEBVTT
00:11.000 --> 00:13.000 align:end
- positive test (should succeed)
WEBVTT
00:11.000 --> 00:13.000 align:star
- test misspelling of one of the possible values
WEBVTT
00:11.000 --> 00:13.000 align:
- test missing value
These tests look okay, but just one thing to point out, the draft does require that a cue has a cue payload (eg, the text content of the subtitle), so if they weren't in the actual test files, they need to be added in so that we're only testing the pass/fail of the specific conditions we're looking at.
