Joel's near-reemergence reminded me of a few low-priority patches I'd sent
his way just before he became more interested in his new daughter than in
us; mostly they're low-priority convenience (to let you add "all tests in
this package" rather than enumerating them individually), but it uncovered
one perhaps-more-important thing that I dropped the ball on:
There appear to be several GWTTestCase classes in UISuite's package space,
which are not actually in UISuite's enumeration of test classes to add to
the suite (and thus aren't being exercised).  Feature or bug?

The classes are:

PasswordTextBoxTest
RandomTest
TextBoxTest


I can't see any particular reason the tests shouldn't be run, I think they
actually pass; should they be included?

And having gone that far, let me reprise the patch I sent Joel.  Note that
the change provoked some legit latent faults in various tests, and also
provoked some not-yet-explained test failures in DOMSuite and I think
TreeTest, so there's still some work to do if we think the package-add
function is useful.  Regardless, we should decide how to handle the three
orphan tests above.

--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Attachment: testclassfinder-r3861-3.patch
Description: Binary data

Reply via email to