CubeTest and Selenium handling of re-directs

[jlcopp]

Hi, I'm new to Cubetest, but not new to testing in general.

Anyway. I have a web-app that does numerous redirects, but within the
same web-server. And with these redirects the back-end maintains
various "state" about what is going on.

As I started doing the gui automation, I noticed that once a user-
interaction happens that then performs a redirect, the recorder stops
as well as any tests that would start from an extension point seem to
go out to lunch and eventually timeout.

I've tried setting the URL starting points, but that too didn't seem
to work, becuase as the test would run, the web-app wouldn't have the
pre-req info that would be required before getting to that page.

Someone has to have encountered this before me... therefore, any
suggestions would be nice.

So how are Re-directs to be handled? As an example I start from
http://<mywebpage and then go thru successive pages ie(
http://<mywebpage>/nextpage?someparm=x, http://<mywebpage>/targetpage)

I end up on the http://<mywebpage>/targetpage. However, the Selenium
context from which recording and/or running is no longer the page
within the browser.

I've also hunted for this in the documentation, but no success.

[Christian Schwarz]

Try using plain Selenium RC. If it works there, then the problem is within CubicTest. If not, then the Selenium and hence the Selenium runner in CubicTest cannot be used to test your site.

Selenium (and CubicTest) should handle normal HTTP 302 redirects. Check out how your application redirects with i.e. the "Live HTTP Headers" Firefox add-on.

C.

2011/1/5 jlcopp <jlc...@hotmail.com>