> > Without reference to his article, I can only guess that it may be pointless > to test the position or the color of a button in automated tests.
I think it was this one : http://www.infoq.com/news/2009/11/uncle-bob-tdd-applicability but in fact uncle bob mainly says it's pointless to do TDD when not knowing where it'll end, but still one should then write the tests afterwards. > On the > other hand, functionality of GUI can definitely be tested. For example, > I am writing a Wicket application with TDD (sort of) with the library shown > in my signature. It is working very well. 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 ? 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 ? bye zedros > > > ----- > -- > 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-tp26505428p26509652.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
