Hi everbody, it actually seems like there is no problem with the ID's. It looks like webtest cannot handle the input image type... (due to HhtmlUnit?)
If so, my company has to use another testing software although I recommended webtest... *irgs* > Do you have easyAjax set to true in your configuration? I have. I had a look at the resulting pages webtest delivers and a closer look at the log. On the resulting page the "button" is clickable but it doesn't do anything. Also the log file has a lot of warnings like this one: [clickElement] WARN (com.gargoylesoftware.htmlunit.DefaultCssErrorHandler) - CS S error: http://path/to/cssFile.css [497:5] ... I found another topic that looks quite similar but there hasn't been any comments on this: http://lists.canoo.com/pipermail/webtest/2004q4/thread.html#2646 Has this issue ever been kind of quick-fixed or is there another way to make it work? :/ I'm really sorry for all this nooby questions... Cheers, Miriam Lee Butts schrieb: > Hi, > > > Hmmm if there is no error then WebTest must be successfully finding the > element and clicking it. > > I don't know much about JSF, maybe there is an issue with HtmlUnit and > the javascript it uses to submit the form? > Do you have easyAjax set to true in your configuration? > > cheers > > Lee > > > 2009/5/20 Naegreth <[email protected] > <mailto:[email protected]>> > > Hi and thanks for your help! > > > >> what error is WebTest reporing? > > Well, using clickElement it doesn't report an error for the clickElement > but for the next step. > > All seems fine but it does not request for the next page. > 1) I verified the h2 element text of the first page (that's ok), then > 2) I tried to get to the next page using clickElement (WebTest is > reporting no error) and > 3) I verified the h2 heading of the next page (Webtest reporting there > is no such text) > so i realized WebTest's current page is still the first one. > > I changed the test to > 1) verify the first page heading (still fine) > 2) click the Element to get to the next page (still no error reporting) > 3) verify the first page heading again ( fine - what acutually is not > that fine...) > > > > according to the other mailing list thread the issue is due to those > > ID's changing each time the layout is changed, making the test very > brittle. > > Ok... I must have mistaken that... my ID's seem to be ok as all other > elements use them and there is no problem. > > > > > You'll either need to click the inputs based on their position (also > > very fragile) or relative location based on some text nearby that > > doesn't change (have a read about xpath axes like previous-sibling > etc). > > Hmm... ok. I've never used xPath (or even axes) before this and I'll > have a closer look . But if it needs some other "static" text nearby > another problem could be, that there is no such text... > > > > > How about using the image name in the src url? e.g. clickElement > > xpath:"//input[contains(@src,'theImageFile.gif')]" > > I've used: > <clickElement > xPath="//input[contains(@src,'/path/to/image.jpg')]" > /> > > And it's also not causing an error on the current test (although it > should cause an error, because I'm still verifing agains the headline of > the first page). > > Anyway, what is the reason why it doesn't cause an error? Is that a > normal behaviour? > > > Cheers > > Miriam > > _______________________________________________ > WebTest mailing list > [email protected] <mailto:[email protected]> > http://lists.canoo.com/mailman/listinfo/webtest > > _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
