Versions Compared

Old Version 6

changes.mady.by.user Martin Terra

Saved on

compared with

New Version 7

changes.mady.by.user Martin Terra

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt
hiddentrue

How to achieve cleaner code and compile-time type-safety for your tests, probably saving 60% of your time


If you use Test Driven Development in Wicket, the first approach is often to use component's path names (e.g., page:panel:form:component) to test them. This is bearable at first, but as your pages get more and more complicated and have deeper hierarhices, you will find yourself spending a whole lot of time debugging typos and misconceptions (in my opinnion: you would waste 60% of your time doing this). The solution is: make your component hierarcy type-safe so that you can GET all of your components when testing:

...