header
header
Main Menu
Home
Eviware Store
Downloads
Products
News
Forum
Eviware Blog
Search
FAQs
Customer Area
Support
Documentation
Tutorials
CookBook
Downloads
Forum
Login Form
Welcome, Guest. Please login or register.
January 09, 2009, 06:24:02 am
Username: Password:
Login with username, password and session length

Forgot your password?
 
Form view is not being used as default for requests
Welcome, Guest. Please login or register.
January 09, 2009, 06:24:02 am
Home Help Search Login Register
News: The Forums are up! Welcome to eviware.

+  Eviware Forum
|-+  soapUI
| |-+  soapUI
| | |-+  Form view is not being used as default for requests
« previous next »
Pages: [1] Print
Author Topic: Form view is not being used as default for requests  (Read 771 times)
mohbubur rahman
soapui pro users
Newbie
*
Posts: 21


« on: June 23, 2008, 12:24:52 pm »

My current SoapUI instalation is configured to use the Form view for requests. However this does not seem to be working. I am data driving the request and have created a property transfer for all the fields. I am having to specify which fields I require before running the test in the outline view. if I use the Form view then I am required to enter a value in the fields otherwise empty fields are removed when viewing in outline.

This is fine for the first iteration but for the second iteration it fails, the outline view changes to what was used in the first iteration. Any fields that are not present in the outline view fail on the property transfer for these fields.

How can I get SoapUI to use the form view and get it to use the same initial request at each iteration
Logged
omatzura
Administrator
Hero Member
*****
Posts: 1,666


« Reply #1 on: June 26, 2008, 12:10:30 am »

Hi,

I'm not exactly sure what you mean here.. could you attach some screenshots that describe the issue?

regards!

/Ole
eviware.com
Logged
mohbubur rahman
soapui pro users
Newbie
*
Posts: 21


« Reply #2 on: July 01, 2008, 05:31:40 am »

Hi Ole,

I have attached a document full of screenshots, hope it helps. A propertyTransfer fails for a field that is not present in the outline view of the request, the outline view changes after each iteration, so if in the first iteration you send a request with 10/15 fields, the outline view will display those 10 fields, the propertyTransfer will fail for the additonal 5 fields. If in the second iteration, you send 5/10 fileds, the outline view wll display these 5 fields and the propertyTransfer for any of the other 10 fields will fail.
Logged
omatzura
Administrator
Hero Member
*****
Posts: 1,666


« Reply #3 on: July 08, 2008, 09:15:48 am »

Hi,

ok.. thanks for your detailed info. I suggest you use property-expansions together with the "Remove Empty" setting for your request instead of using property-transfers;

1) Disable the property-transfer step (right-click menu)

2) Use the "getdata-button" in the form editor in each field to select the corresponding property from the DataSource step.. you should see content like ${DataSource#Case} in the different fields. These will be replaced by the corresponding values when the request is sent.

3) Set the "Remove Empty" option in the bottom left properties list for the request to true; this will remove empty elements from the outgoing request after the property values have been populated.

Hope this works out for you.. let me know!

regards,

/Ole
eviware.com
Logged
mohbubur rahman
soapui pro users
Newbie
*
Posts: 21


« Reply #4 on: August 06, 2008, 12:41:55 pm »

Hi Ole,

Thanks for the help it has resolved this issue however I am also capturing the requests and responses and writing these to file. The response is fine, it is what I am expecting but the request does not display the data used.

The request is using the property expansion method and displays the data in the request like '${DataSource#InstrumentCode}'. When the request is captured and saved to file, the request also shows this property expansion as the value i.e. <InstrumentCode>${DataSource#InstrumentCode}</InstrumentCode>. This makes it slightly difficult to reconcile with the data file used, although the workaround I used for this is using row id to identify. Could this be changed/configured to show the values in the request or am I capturing the request at the wrong time?

Thanks

Moks
Logged
omatzura
Administrator
Hero Member
*****
Posts: 1,666


« Reply #5 on: August 07, 2008, 12:08:24 am »

Hi!

exactly how are you writing the Request xml to a file? You need to get hold of the WsdlTestRequesStepResult object for the corresponding TestStep which exposes a requestContent property containing the actual xml sent, after all properties have been expanded..

regards!

/Ole
eviware.com
Logged
mohbubur rahman
soapui pro users
Newbie
*
Posts: 21


« Reply #6 on: August 07, 2008, 12:33:07 pm »

Hi,

I am using the following syntax to catch the request.

// get the request object
def request = testRunner.testCase.testSteps["Request_1"].testRequest

// get the actual messages
def SOAPrequestContent = request.requestContent

Regards,

Moks
Logged
Pages: [1] Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
header header
header
header