As you know, it is usual that wicket generates its own attributes ids at random. This is a problem for using selenium because the best way to find a tag it is through its id. That's way con can set up your app to generate an extra id that would be always the same for cases such as Selenium. Here is the code to set up an attribute called wicket:id which helps you to test easily your app:
getDebugSettings().setOutputComponentPath(true); When you set up your app in this way, you can get a wicket:path="some string constant" to test better your app. The problem with selenium that I found is that Selenium doesnt accept attributes with namespaces. I think it is a problem from selenium. That's way I ask Amit how he manages with selenium. I filled up this Jira https://issues.apache.org/jira/browse/WICKET-2322 to get an attribute without namespace. This same issue was resolved for wicket 1.4.r.X. On Sat, Jun 20, 2009 at 8:37 PM, amit_vibhuti <amit_vibh...@rediffmail.com>wrote: > > Can you explain me in detail, what the wicket path you are talking about? > -- > View this message in context: > http://www.nabble.com/Testing-ModalWindows-with-Selenium-tp15166572p24131313.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Fernando Wermus. www.linkedin.com/in/fernandowermus
