Hey, I'm starting to write selenium tests for my wicket app and am running into issues with a couple of wicket related problems that I thought perhaps somebody else may have solved.
1) Sometimes my repeaters don't print out consistent wicket paths, i.e. sometimes it may go element_path_name_1 to element_path_name_4 if I have 4 elements.. Other times it might be element_path_name_4 to element_path_name_7 after some ajax calls, I'm not sure when/why this happens. Need to play with it more. 2) I have issues with timing which is typical, and most people call "waitForPageToLoad" which works fine for normal http requests, but if It is an ajax request I'm waiting for, then I have to implement a waitForContition. Is there a wicket convention I could use here? i.e. how can I know that a wicket ajax call has completed? Thanks, D/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
