To add an issue of my own:
Refactoring testing mechanism - I've been thinking about the testcases =
that the parser is using now, and I feel it is not so intuitive, even =
with the utility methods like createParser()... , to create a testcase =
quickly.
I was thinking that it would be important to refactor this asap - as the =
parser seems to be growing fast now. How about if we keep the tests in =
files - with the test HTML and expected results in text files - which =
should be easy to author and add.=20
Also, I think we are looking at a shipping date of Jan 1 for 1.2. So, it =
would be good if we can have some help reviewing the current design, =
tests, and suggesting any last minute modifications that are essential.
Derrick - thanks a ton for your work - I can see the no of tests has =
jumped from 219 to 254!
Cheers,
Somik |
