Update parse errors for tree construction tests #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've gone through nearly all the tree construction tests and updated the parse errors.
My method was to take each test and compare the number of reported parse errors between html5lib-python and the parser I'm working on. Where they agreed, I simply pasted html5lib-python's errors in. Where they disagreed, I stepped through with the spec in hand and tried to tease out the proper errors. (Sometimes html5lib-python looked right. Sometimes my parser looked right. Sometimes neither looked right. And I'm sure I didn't get them all right, but I think it's a good deal better than nothing.) Note that although the number of errors for a given test may be agreed upon between the two parsers, I did not verify that those errors are accurately described.
I have not yet done tests09 and tests10. I'll add them later, in this or another pull request. I have not done, and do not plan to do, template.
I did delete one test: the fifth test in tests18. It was an exact duplicate of the fourth test in tests18.
Whenever I resolved disagreements between the parsers against html5lib-python, I took notes. They're available in this gist in hopes that they may be helpful. I numbered the tests in each file starting with zero, as they were before any commits in this pull request.
Fixes #14 (and then some).