Commit 83e9cb9c authored by Glenn Adams's avatar Glenn Adams
Browse files

Update documentation.

parent f1c92088
......@@ -32,12 +32,80 @@ Commercial Video Player 2 Test Suite
The `cvp2ts` tool provides a test suite for performing signature and feature presence testing on a candidate Commercial Video Player 2 (CVP2) user agent (browser).
## Build Dependencies
## Organization
The `cvp2ts` tool source and build tree is organized as follow:
Makefile - top level (GNU) makefile - general make configuration parameters - specifications parameter (determines which specifications to process) - tools parameter (determines which tools are run) - this readme
specs/ - contains one sub-directory for each specification
tests/ - contains test (and helper and resource) files produced by build
tools/ - contains build, utility,and run tools
Each specification directory is initially populated with a configuration file, e.g.,
`html5.config.json`, which provides configuration parameters for the build tool chain.
## Build Tool Chain
The following tools are executed in the normal build chain:
fetch - fetches specification source, unless skipped (see below)
extract - extracts WebIDL fragments from specification source unless skipped (see below)
parse - parses WebIDL fragments into JSON representation
index - aggregates all parsed WebIDL into an index, used in subsequent steps
generate - generates tests from parsed WebIDL fragments
Fetching a specification may be skipped by its configuration file for various reasons, such as listed below. If not skipped by configuration parameter, an attempt is made to fetch in order to determine the Last-Modified date and time. If a cached version is available and the specification has not changed, then the remainder of the fetch is skipped.
Some reasons for skipping fetch include:
* Specification is final (REC or equivalent)
* Specification must be manually processed after fetching before performing extraction, e.g., in order to create a `respec` snapshot.
* WebIDL must be manually extracted or edited, in which case refetch should be performed manually before this extraction or edit.
Extracting WebIDL from a fetched specification may be skipped according to configuration control if the IDL cannot be automatically extracted or must be manually edited, e.g., to make it acceptable to the WebIDL parser.
## Building Tests
In order to perform a clean build, perform the following steps:
% make clean
% make
% make MANIFEST.json
Normally rebuilding the `MANIFEST.json` file is not required unless some test has changed (or been added or removed).
## Build and Run Dependencies
* node.js
* npm
* cheerio npm module
* webidl2 npm module
* python
## Running Tests
In order to run tests, perform the following steps:
1. Add entries to the local /etc/hosts file as follows:
` web-platform.test`
` www.web-platform.test`
2. From the top-level directory of this `cvp2ts` hierarchy, run the following command in a separate shell:
`python tools/w3c/scripts/`
3. From the test browser (user agent), open the following link:
4. After setting runner options as desired, click on `Start` button. Note that Manual tests are enabled by default, and there is at least one manual test present in the generated tests.
If it is desired that the server and client run on separated devices, then the nameserver in use should be configured to return the desired address for the server (instead of the localhost address).
## Notes
......@@ -55,4 +123,11 @@ The `cvp2ts` tool provides a test suite for performing signature and feature pre
$ npm ls --parseable true --long true webidl2 | awk -F: '{print $2}'
$ python -V
Python 2.7.7
## Issues
See [Open Issues]( for current known bugs, feature requests (enhancements), etc.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment