WicketTestCase moved from src/test/java into src/main/java

[Juergen Donnerstag <ju...@gmail.com>]

It seems that WicketTestCase has recently be moved from src/test/java
to src/main/java. I'm -1 on this channge. I understand the reason well
and I think we should come up with a better solution rather than to
allow code creep. It is merely for testing purposes. E.g. what about
getting rid of it completely and moving the functionality in
WicketTester.

Juergen

Re: WicketTestCase moved from src/test/java into src/main/java

[Jean-Baptiste Quenot <jb...@apache.org>]

* Juergen Donnerstag:

> It  seems  that  WicketTestCase   has  recently  be  moved  from
> src/test/java to  src/main/java. <snip/> what about  getting rid
> of it completely and moving the functionality in WicketTester.

+1

I would do something like:

WicketTester tester = new WicketTester()
tester.startPage(MyPage.class);
tester.assertResultPage(MyPage.class, "MyPageExpectedResult.html");

And probably add a few methods in WicketTester like:

* executeBehavior()
* executeComponent()
-- 
     Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

Re: WicketTestCase moved from src/test/java into src/main/java

[Jean-Baptiste Quenot <jb...@apache.org>]

* Juergen Donnerstag:

> It  seems  that  WicketTestCase   has  recently  be  moved  from
> src/test/java  to  src/main/java. I'm   -1  on  this  channge. I
> understand the  reason well and I  think we should come  up with
> a  better  solution  rather  than to  allow  code  creep. It  is
> merely for testing  purposes. E.g. what about getting  rid of it
> completely and moving the functionality in WicketTester.

Done.  I  moved the  functionality in  WicketTester, and  put back
WicketTestCase in src/test (many classes were depending on it).
-- 
     Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/