ginal Message-
From: Andreas Kuhtz [mailto:andreas.ku...@gmail.com]
Sent: Friday, June 14, 2013 4:25 AM
To: users@wicket.apache.org
Subject: Re: Unit testing a repeater or data table by mocking its data
You can define a mock with the same bean id that will override the
original bean (e.g.
onContextMock which is killing me as I have
> quite a lot of mocks to implement just to get the user logged in to the
> application and start a single page :(
>
> I don't yet want to use Spring's ProxyFactoryBean in conjunction with
> HotSwappableTargetSource as it would make
mess of my
applicationContext.xml.
~ Thank you,
Paul Bors
-Original Message-
From: Andreas Kuhtz [mailto:andreas.ku...@gmail.com]
Sent: Wednesday, June 12, 2013 11:26 AM
To: users@wicket.apache.org
Subject: Re: Unit testing a repeater or data table by mocking its data
Hi Paul,
ests (talk about being lazy).
>
> ~ Thank you,
> Paul Bors
>
> -Original Message-
> From: heikki [mailto:tropic...@gmail.com]
> Sent: Tuesday, June 11, 2013 11:14 AM
> To: users@wicket.apache.org
> Subject: Re: Unit testing a repeater or data table by mocking its dat
: Unit testing a repeater or data table by mocking its data
dear Paul,
I've recently used Mockito and am quite happy with it. You can easily mock any
class and make it behave as you need.
Best regards
Heikki Doeleman
On Tue, Jun 11, 2013 at 5:08 PM, Paul Bors wrote:
> Up to recently we
dear Paul,
I've recently used Mockito and am quite happy with it. You can easily mock
any class and make it behave as you need.
Best regards
Heikki Doeleman
On Tue, Jun 11, 2013 at 5:08 PM, Paul Bors wrote:
> Up to recently we got away with running our unit tests fully integrated
> with
> the
Up to recently we got away with running our unit tests fully integrated with
the back end db by performing live queries via our DAOs.
Due to recent changes to our product schema we run into the inevitable high
cost of having to spend too much time on maintain our mocked unit test data
straight int
