person
/
...
!-- Need some way to cause the test to fail if the StatusCode was not 200 --
...
/ifStep
...
---
How do I best cause the test to fail if the original condition is not true?
Regards,
Doug
Douglas Beattie
problem.
William Soula
QA Analyst
Pointserve, Inc.
110 Wild Basin Road
Suite 300
Austin, Texas 78746
O: 512.617.5311
F: 512.617.0466
- Original Message-
From: webtest- [EMAIL PROTECTED] [mailto:webtest- [EMAIL PROTECTED] On Behalf
Of Douglas Beattie
Sent: Wednesday, February 13, 2008 9
Message-
From: webtest- [EMAIL PROTECTED] [mailto:webtest- [EMAIL PROTECTED] On Behalf
Of Douglas Beattie
Sent: Tuesday, February 12, 2008 3:39 PM
To: webtest@lists.canoo.com
Subject: [Webtest] Help needed on ifStep ... /
I have a test with the following
William,
I really appreciate your responses and thoughts. I agree my thinking about
failing but continuing with more tests is NOT a correct thing to do.
I've finished my meeting so can now get back on trying your suggestions. What
I'm hoping to now accomplish with the test is that if the
I have a test with the following in it:
---
?xml version=1.0?
!DOCTYPE project SYSTEM ../../dtd/Project.dtd
project name=getMeWithValidSessionId default=test
target name=test
webtest name=Get 'Me' With Valid SessionId
I'm starting to get a feel for the basic things I can do with WebTest. I now
have the following question.
How can one best create a schema object, populate it to POST it via a RESTful
API, then GET (via another RESTful API) a similar object, and compare it to an
original in WebTest?
I asked this same question yesterday in a post titled Sequential (as executed)
ordering of the Test Scenario Overview section or the results page question.
I'm glad others are seeing this too.
The version of Java I am running is 1.6.0_03
Doug
Marc Guillemot [EMAIL PROTECTED] 01/18/08 2:08 AM
What does one need to do to get the tests to be ordered sequentially (as
executed) in the Test Scenario Overview area of the results page?
Right now they seem to be displayed somewhat random.
Doug
--
NOTICE: This email
Marc and others,
Sorry for the noise. I found the problem. It was an extra comma before the
closing quote on the ThrowExceptionOnFailingStatusCode name. I just cut and
pasted from the e-mail without looking at what was in the quotes.
Problem solved. It works fine now.
Doug
Douglas Beattie
I properly detect and verify (via verifyXPath) a successful login where the
response contains a statusCode=200, but when I run a test which provides an
invalid username and password to the login API the check for a statusCode=401
never gets executed. I see the 401 in the response but my test is
AM
Hi,
attribute are not case sensitive in an Ant file but invoke doesn't have
any sessionId attribute, no matter with which case it is written.
Cheers,
Marc.
--
Blog: http://mguillem.wordpress.com
Douglas Beattie wrote:
In the following code:
invoke url=http://10.0.1.1:8080
---
I fail to verify the statusCode.
If I comment out the verify statusCode check then I fail to get and store the
sessionID to be used for logout.
Can anyone tell me the error(s) in my code?
Thanks,
Doug
Douglas Beattie [EMAIL PROTECTED] 01/10/08 10:09 AM
I have used C and done much
the login takes a username and
password as its parameters.
If I manually (via the browser) make the call to logout and provide the session
id obtained in the login I get a valid 200 statusCode returned.
Thanks for any pointers any of you may be able to provide.
Doug
Douglas Beattie [EMAIL
In the following code:
invoke url=http://10.0.1.1:8080/identity/v1/logout;
sessionId=#{sessionID}
description=Logout valid user
property=sessionID
/
I specifically set the parameter sessionId, (with an upper case I), but when
it gets executed it
I have used C and done much work with Unix internals over 20 years, but am very
new to programing and testing with html, java, xml, XPath, ... type web
services. I am attempting to use WebTest to validate some new RESTful APIs. In
doing this I have run into what I'm sure is a very basic problem
15 matches
Mail list logo
