Our very own mr AJAX, Arthur, blogs about how we perform automated Selenium tests on Wicket components for Hippo CMS 7.
Although he credits me for the video, I was merely playing the annoying voice-over and shaky-cam-operator role :-). Arthur does all the talking. So here's credit back, 'Thuur.
In his blog, he explains how we had to tweak the Wicket markup ids to get Selenium to work.
"Use case testing" is my term for what Arthur (and with him probably the rest of the world) calls "integration testing". This is where we bring together two very important stakeholders into our development project: on one hand, the developers want to know whether integration doesn't break functionality, and on the other hand, users and testers want to know whether the new version of the system has at least the same level of functionality and stability as the last time they tested it. That's why, at the end of each development Sprint, we have a round of user testing. During that phase we record the use cases that the testers perform and add that to our set of automated Selenium tests.
Go ahead and enjoy Arthur's blog and the demonstration video (and my shaky camera moves).
