There are a couple of Posts but none that answers my Question.
How is a Unit Test for a Wicket CDI Application supposed to be written?
For the CDI Module itself there is CDIUnit from JGlue, but this does not
work
for ApplicationTests as the Classes are not found and some are marked as
Package
I have a very simple testcase running, described here
http://www.effectivetrainings.de/blog/2013/11/30/wicket-und-cdi-1-1-auf-den-richtigen-kontext-kommt-es-an/.
But I´m pretty sure there must be an easier way.
--
View this message in context:
Hi,
There is a new experimental module that provides CdiWicketTester -
https://github.com/apache/wicket/blob/wicket-6.x/wicket-experimental/wicket-cdi-1.1/src/test/java/org/apache/wicket/cdi/CdiWicketTester.java
It's first release will be with Wicket 6.13.0
But as you can see CdiWicketTester is
Hi,
Usually when running (WicketTester) tests people provide mock
implementations of the external services like MQ, DB, ...
It is much easier to return some mock data, either good data or broken, to
your application and verify that it behaves correctly in both situations.
On Fri, Nov 29, 2013
