This is a bit of a general question: I'd be interested in hearing about how people do automated tests of their Wicket applications. I'm thinking about system tests of the full application, not unit tests.
There are of course tools like Selenium which let you automate actions on a web application. My colleagues with experience of this from other applications tell me that one of the main challenges is to stop test cases from being very brittle by relying on the details of the generated markup. It would be nice if it was possible to target components on a page in a way that related them back to roughly the hierarchy of Wicket components. Or even better, if individual parts of the page (links, input fields, buttons etc.) could be identified in a way that didn't break when there were changes to the Wicket component hierarchy (say, new grouping components being inserted higher up in the component tree). I realise this isn't the responsibility of Wicket, but are there ways in which Wicket can help here, e.g. by generating ids or other attributes inside the markup in a way that makes it easier to locate items on a page? Are there other tools than Selenium that people use, that makes things easier? I'm looking forward to hearing about how other Wicket users deal with these issues! Regards, Jan
