1
edit
Changes
→Tests
** Install the webvtt npm module:
$ sudo npm install -g webvtt
* Add humphd's webvtt github repo as a remote
* Switch to the seneca branch
$ git checkout seneca
* Add your tests to test/spec/good and test/spec/bad
We'll break the tests up by type within the file format specification. Each group will be responsible for determining tests for their section of the spec. The sections, while somewhat arbitrary (i.e., feel free to further subdivide or offer other divisions) are:
Each group is responsible for determining and writing the tests necessary for their section, and can be listed below, or in a separate wiki page. Every section/test needs to be owned so it doesn't get lost.
===Test Naming Format===
http://zenit.senecac.on.ca/wiki/index.php/Test_files
== Open Questions ==
* Which metadata should we capture about each test?
* Which format should we use for this metadata?
** Should we embed in the WebVTT comment block?
** Should we have test-file.vtt and test-file.vtt.html (i.e., 2 files per test, one with metadata)?
** Should we have one large file with data about the tests in the folder?
** Should we write code/build steps to generate metadata from webvtt files? (e.g., extract from header of test file, merge secondary files into one file, etc.)
** I asked this of the #whatwg channel on freenode, where the W3C spec editors hang out. [[WebVTT Testing Question on #whatwg|Their answer is here]].
== Resources ==
