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" <mgrigo...@apache.org> 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 <bgoldow...@cast.org> 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) > > >
