zedros wrote:
>
> I saw it, but we're using guice (when, it wouldn't be a show stopper
> in the end). Still, on the technical side, there's also this issue
> with selenium using mostly id, whereas wicket'ids change with each
> request... How do you solve this issue ?
>
If the element is not in a loop, just specify the HTML ID in the template.
If it is in a loop, use xpath.
zedros wrote:
>
> on a broader picture, my main question was about the way you proceed,
> Do you test every page, including every validator or.. ? If doing so,
> for pages that quite often are then not touched much, i would fear the
> time needed for proper testing quite hard to justify. Am i wrong here
> ?
I test my code based on risk. If it is the code that is frequently use, has
a high impact if it breaks, or is likely to contain bugs, I'll test it more
thoroughly.
-----
--
Kent Tong
Better way to unit test Wicket pages (http://wicketpagetest.sourceforge.net)
--
View this message in context:
http://old.nabble.com/Wicket-tester-test-coverage-tp26505428p26541425.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
