Hi,
What is the purpose of having the WebTestCase generated at runtime from the
WebTester? It's not entirely clear to me.
Considering that the entire class is just a proxy around the WebTester, the
only additional functionality that I can see it adding is the ability to
provide a custom tester. But the custom tester must extend WebTester
already.
What if we renamed WebTester to WebTestCase and allowed it to extend JUnit's
TestCase directly? It will still be possible to provide custom testers by
extending WebTestCase.
Benefits that I see:
- one less Maven plugin to worry about
- we do not have to go through an additional step to generate the interface
for WebTestCase
- less compile warnings (the parser doesn't currently copy generics in
method definitions)
- it makes browsing source code easier (the missing WebTestCase from source
files stumped me for a couple of hours when I was first working with
JWebUnit)
Thoughts?
Jevon
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
JWebUnit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development
