Greetings all,
I propose that we call the next stage "feature freeze", rather than=20
"code freeze", since we'll be changing the code as we fix bugs. =20
After that, we could have a week of actual code-freeze, so we can all=20
re-run our tests on the final product.
Attached is a more completed breakdown of attributes to test. I'll=20
take those under the headings which I've put (lha) after, and have=20
already verified those ending with lha.
I agree with Neal that we really need people to say what testing they=20
have time for, and to pick one or more groups of attributes. Can I=20
ask one of our multi-lingual developers to test the=20
internationalisation (even though those attributes are also all in=20
other groups)?
FYI, I'm also attaching a couple of scripts that I eventually want to=20
put in .../test -- one is a utility to set an attribute in a=20
temporary config file, and the other is what I've been using to test=20
the "fuzzy" rules. (It needs some other files to run, but could form=20
a template for other people's testing.) It would be nice to build up=20
a complete test suite to make the next release easier.
Thanks in advance to all those who can chip in.
Lachlan
--=20
lh...@us...
ht://Dig developer DownUnder (http://www.htdig.org) |
