summaryrefslogtreecommitdiffstats
path: root/misc/testsuite
Commit message (Collapse)AuthorAgeFilesLines
* Fix SVG 1.1 test case title.Ville Skytt?2011-08-231-1/+1
|
* Use "W3C Markup Validation Service" instead of "W3C HTML Validation Service" ↵Ville Skytt?2010-06-301-1/+1
| | | | more.
* Drop CVS keywords.Ville Skytt?2010-06-231-4/+1
|
* Update instructions etc from CVS to Mercurial.Ville Skytt?2010-06-221-1/+1
|
* Fix unknown FPI tests.ville2010-03-041-8/+8
|
* Usage message fix.ville2010-03-041-1/+1
|
* Add another Windows-1250 test case.ville2010-03-041-0/+8
|
* Update Atom test case to one that currently really serves ↵ville2009-12-041-6/+12
| | | | application/atom+xml, add some "with v.w.o" links.
* Link fixes.ville2009-12-041-5/+5
|
* URI encoding fixes (jinja2 does not have a filter for that :().ville2009-12-041-30/+30
|
* Note Python 2.6 dependency.ville2009-11-161-0/+3
|
* Improve unsuccessful request handling.ville2009-11-162-15/+22
|
* Fix test URI escaping.ville2009-11-161-2/+2
|
* Fix --help.ville2009-11-161-1/+1
|
* Initial Python 3 compatibility tweaks.ville2009-11-161-8/+8
|
* Rename MathML2 test file to *.mml so servers are more likely to serve itville2009-10-251-1/+1
| | | | with an appropriate content type, use recommended system id in it.
* adding test case for http://www.w3.org/Bugs/Public/show_bug.cgi?id=4412ot2009-02-131-0/+8
|
* adding html5 test casesot2008-08-201-0/+47
|
* introot2008-07-311-0/+5
|
* wrong metadata for W07 test caseot2008-07-311-1/+0
|
* note about automationot2008-07-281-3/+6
|
* using the site-wide SSI for headerot2008-07-281-19/+6
|
* finalizing routines and templates for the listing and generation of test ↵ot2008-07-287-13/+285
| | | | cases documentation from the catalog - needs jinja2 template engine
* python2.4-friendly class declarationsot2008-07-222-3/+3
|
* adding a couple of test cases of XHTML documents (could be identified by the ↵ot2008-05-051-0/+12
| | | | | | | | 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 (?)
* Test suite pretty much fully migrated to metadata-rich XML file.ot2008-03-281-135/+502
| | | | | | 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.
* testcase titleot2008-03-281-3/+8
|
* metadata for the Markup Validator Test Suiteot2008-02-271-0/+774
| | | | | | | | | | | | | | | | | | (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
* test suite script for the W3C markup validatorot2008-02-271-0/+158
| | | | | | | | | | | (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
* samples for test suite sanity checksot2008-02-274-0/+47
|
* Test Suite python classes for markup validation.ot2008-02-271-0/+236
| | | | | | | | 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"
* simple python code to access the markup validator via its HTTP headers responseot2008-02-271-0/+95