| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
more.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
application/atom+xml, add some "with v.w.o" links.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
with an appropriate content type, use recommended system id in it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
cases documentation from the catalog - needs jinja2 template engine
|
| |
|
|
|
|
|
|
|
|
| |
namespace)
without doctype. One is served as text/html, another with application/xhtml+xml
How the validator should handle these is not very well defined (?)
|
|
|
|
|
|
| |
The test suite may still need to be improved to:
- mention when validation needs to be running with specific options
- mention when an "ideal" result is expected but we know the validator is buggy.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(work in progress) imported from the previously hand-rolled
http://qa-dev.w3.org/wmvs/HEAD/dev/tests/
The metadata is using a simple (?) XML format:
* root element is testsuite
* testsuite element can have 0~n collection children
- collection elements should (for selection purposes) have an id attribute
- collection elements should have a dc:title child element describing the collection
- collection elements may have 0~n collection children (hence allowing nesting of test collections)
- collection elements may have 0~n test children
+ test elements must have a uri child
+ test elements may have a dc:title child describing the test and/or an html:p longer description
+ test elements should include expected results in an expect child
transition of the test suite metadata to this XML format is still work in progress
|
|
|
|
|
|
|
|
|
|
|
| |
(and in longer term, to compare validators)
This work is an evolution from earlier work on the Link Test Suite ( http://dev.w3.org/cvsweb/2008/link-testsuite/ )
with a number of small differences:
* instead of a nested directory structure, the test suite is described in a single XML file
* comparison of results and expected results are more flexible, e.g it is possible to specify
"results should have some warning(s)" rather than "results should have 12 warnings exactly"
* easy selection of the tested validator instance from the command line
* possibility of running only a subset of the test suite with a commandline option
|
| |
|
|
|
|
|
|
|
|
| |
This code is an evolution from earlier work on the Link Test Suite ( http://dev.w3.org/cvsweb/2008/link-testsuite/ )
with a number of small differences:
* instead of a nested directory structure, the test suite is described in a single XML file
* comparison of results and expected results are more flexible, e.g it is possible to specify
"results should have some warning(s)" rather than "results should have 12 warnings exactly"
|
|
|