A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Validator.nu Unit Tests: Difference between revisions
No edit summary |
|||
| Line 8: | Line 8: | ||
The tree builder of the Validator.nu HTML Parser is tested using the [http://code.google.com/p/html5lib/source/browse/#svn/trunk/testdata/tree-construction tree construction tests] hosted by the html5lib project. <code>nu.validator.htmlparser.test.TreeTester</code> is the test harness. | The tree builder of the Validator.nu HTML Parser is tested using the [http://code.google.com/p/html5lib/source/browse/#svn/trunk/testdata/tree-construction tree construction tests] hosted by the html5lib project. <code>nu.validator.htmlparser.test.TreeTester</code> is the test harness. | ||
==html5lib Encoding Tests== | |||
The meta sniffer of Validator.nu HTML Parser used to be tested using the [http://code.google.com/p/html5lib/source/browse/#svn/trunk/testdata/encoding encoding tests] hosted by the html5lib project. <code>nu.validator.htmlparser.test.EncodingTester</code> is the test harness. ''However, both the tests and the code are out of sync with the spec.'' | |||
Revision as of 08:48, 9 September 2008
Validator.nu has various places for unit tests.
html5lib Tokenizer Tests
The tokenizer of the Validator.nu HTML Parser is tested using the tokenizer tests hosted by the html5lib project. nu.validator.htmlparser.test.TokenizerTester is the test harness.
html5lib Tree Builder Tests
The tree builder of the Validator.nu HTML Parser is tested using the tree construction tests hosted by the html5lib project. nu.validator.htmlparser.test.TreeTester is the test harness.
html5lib Encoding Tests
The meta sniffer of Validator.nu HTML Parser used to be tested using the encoding tests hosted by the html5lib project. nu.validator.htmlparser.test.EncodingTester is the test harness. However, both the tests and the code are out of sync with the spec.