When Wicket was doing this the JS developers were dealing with Dojo 0.4 ;-)
See org.apache.wicket.util.tester.WicketTestCase#executeTest(java.lang.Class,
java.lang.String)
Example:
https://github.com/apache/wicket/blob/2c673f340539812d26a8a8a4153ed6d8505e5628/wicket-core/src/test/java/org/apache/wicket/ajax/markup/html/ajaxLink/AjaxLinkTest.java#L85
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Dec 15, 2016 at 3:39 PM, Boris Goldowsky
wrote:
> It can be convenient to write a unit test that essentially says, “this
> component should return this HTML” (or perhaps a slightly abstracted view
> of the HTML DOM). Snapshot testing frameworks automate this (eg, making it
> easy to update the expected DOM when you intentionally change your
> component). I’m wondering if this is possible for a wicket app; I’ve so
> far only seen it done with ReactJS.
>
> See https://medium.com/@dschmidt1992/jest-snapshot-testing-3ef9fa1222bb
> for a better explanation of the basic idea.
>
> Boris
>
>
> On 12/15/16, 7:04 AM, "Martin Grigorov" wrote:
>
> Hi,
>
> What exactly do you need to do ?
> To test your application against Wicket 7.6.0-SNAPSHOT ?
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, Dec 15, 2016 at 12:40 PM, Boris Goldowsky >
> wrote:
>
> > Has anyone implemented snapshot testing for a wicket app or have
> > suggestions on how it might be done?
> >
> > Boris
> >
> > (yes, I know there are different schools of thought on whether
> snapshot
> > testing is a good idea or not)
> >
> >
> >
>
>
>