Just some background on why I said what I did:
from http://www.checkupdown.com/status/E302.html
Resolving 302 errors - general
The 302 response from your Web server should always include an
alternative URL to which redirection should occur. If it does, a Web
browser will immediately retry the alternative URL. So you never
actually see a 302 error in a Web browser, unless perhaps you have a
corrupt redirection chain e.g. URL A redirects to URL B which in
turn redirects back to URL A. If your client is not a Web browser,
it should behave in the same way as a Web browser i.e. immediately
retry the alternative URL.
If the Web server does not return an alternative URL with the 302
response, then either the Web server sofware itself is defective or
your Webmaster has not set up the URL redirection correctly.
on 17/11/06 09:15 Rob Manthey said the following:
I'm not a great expert, just an average user, but *I* can't see
anything in the url that I would expect to baulk webtest.
(I think) the key here is that your url is immediately redirected by
the server to another page yes? hence the 302, which is handled
without notification to the user by the average browser. But webtest
parks at the 302 (correctly because it is the honest truth!) and
doesn't process the redirect and further? So what you want to do is
nudge it on the next step down the track, which a normal browser would
do silently, and process the 302 redirect's target page. No *I*
don't know how to do this offhand, but hopefully we've clarified your
problem and requirement (if not please correct this description!) and
I imagine one of the gurus will come online sometime in the next few
hours and either toss a solution at you or declare it a shortfall.
No under no circumstances is webtest intended to be useable only by
java coders, though it is perhaps starting to rely on people being
able to slip in snippets of groovy lately where in the (distant) past
it was all declarative xml.
How are those icebergs going over there? Keep them over there won't
you, we don't want them sailing up the Brisbane river!
Rob
on 17/11/06 08:50 Charlie Kuharski said the following:
Reaching via a browser is fine. I can see it also. Know that
WebTest is build upon the HtmlUnit's API.
As far as being reachable via HtmlUnit, this is only a guess, but I'm
guessing the URL is passed through to be used by HtmlUnit. So I'm
guess it's the culprit. There is a slight chance it's WebTest
mangling the name somehow, but I doubt it. Wouldn't know for sure
until someone looks at the source.
Try using the IP address instead.
John and Pip wrote:
Hi Charlie,
Thanks for your response.
Do you mean you couldn't reach
https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do
from a browser or that you think WebTest believes it is not
reachable? This is the main public URL of the Air New Zealand flight
booking engine, and we have a screen up in the office showing
bookings coming through every minute!
re testing with HTMLUnit: I'm not a java programmer - just a tester,
trying to figure out whether I need to be a java programmer to use
WebTest!
Thanks for the hint re version number. I see this is R_1389. In fact
to my embarrassment I see this even appears in my email below!
regards,
John
On 11/17/06, *Charlie Kuharski* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Your host is not reachable. I'm guessing it HtmlUnit. Try
using something without the "...co.nz". You could try and test
with HtmlUnit.
An ugly was to discover the version is to
1) replace your steps with this only:
<verifyTitle
description="we should see the login title"
text="Login Page" />
2) you should see something like:
C:\test\Translink\gtest1.xml:12: Canoo Webtest: R_1393.
Test failed.
Exception raised:
com.canoo.webtest.engine.StepExecutionException: No current
response available! Is previous invoke miss
itle at C:\test\Translink\gtest1.xml:30: with (description="we
should see the login title", taskName="verifyTitle", text
anoo.webtest.engine.StepExecutionException: No current response
available! Is previous invoke missing?, Step: VerifyTitle
nk\gtest1.xml:30: with (description="we should see the login
title", taskName="verifyTitle", text="Login Page")
Good luck.
John and Pip wrote:
Hi,
I have a test that is failing to follow a 302 error. I've
searched the archives and played around trying to enable
redirects but nothing seems to work.
Below is the stripped-down test (just one invoke) and the
output. This is a publicly available page so you can hit
https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do
from either IE or Firefox so I'm hoping someone can help me
figure out how to hit this page from WebTest! Note that I've
tried an internal page that is http rather than https and get
the same problem so it isn't related to SSL.
I am using Java 1.5.0.6 <http://1.5.0.6>, HTMLUnit 1.10 and
WebTest R_1393 (I think! How can I verify this?).
Regards,
John
<?xml version="1.0"?>
<!DOCTYPE project SYSTEM "WebTest.dtd">
<project name="OLH" basedir="." default="main">
<property name="webtest.home" location="..\.."/>
<import file="${webtest.home}/lib/taskdef.xml"/>
<target name="main">
<webtest name="ISIS SFF NZ Search">
<steps>
<invoke
description="ISIS SFF NZ search page" url="
https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do";
/>
</steps>
</webtest>
</target>
</project>
Here is the output:
<?xml version="1.0" encoding="UTF-8"?>
<summary Implementation-Title="Canoo Webtest"
Implementation-Version="R_1389">
<testresult endtime="Fri Nov 17 09:25:42 NZDT 2006"
location="F:\WebTest\doc\ISIS\tempTest.xml:7: "
starttime="Fri Nov 17 09:25:40 NZDT 2006"
successful="no" testspecname="ISIS SFF NZ Search">
<config>
[snipped because I give the full URL below – get
same result if set up config properly including port 443]
</config>
<results>
<step>
<parameter name="description" value="ISIS SFF
NZ search page"/>
<parameter name="method" value="GET"/>
<parameter name="resultFilename"
value="response_1163708742276_invoke.html"/>
<parameter name="taskName" value="invoke"/>
<parameter name="url"
value="https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do
<https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do>"/>
<result>
<failed duration="1469"/>
</result>
<htmlparser>
<error col="1" line="1" url="
https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do";>Empty
document.</error>
</htmlparser>
</step>
<failure
message="com.canoo.webtest.engine.StepFailedException:
Step[invoke "ISIS SFF NZ search page" (1/1)]: HTTP
error 302, at: invoke, Step: InvokePage at
F:\WebTest\doc\ISIS\tempTest.xml:9: with
(description="ISIS SFF NZ search page",
method="GET",
resultFilename="response_1163708742276_invoke.html",
taskName="invoke",
url="https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do"
<https://flightbookings.airnewzealand.co.nz/isbook_en_NZ/book/initSearchForFlights.do">;)"/>
</results>
</testresult>
</summary>
