Hi nmrao
I'm not asking for groovy to do this - I know the groovy will work for this - but the property transfer option should work as well and doesn't - hence the reason I asked.
Ignore the fact that I've used the same responses from my previous post - the problem I'm asking about is totally different.
Why does the propertytransfer fail when the test executes but works when run manually? <-- I'm asking this because it should work but doesn't - hence its a problem
cheers
richie
Would you please show the property transfer step definition(screen shots if possible )?
Does it always return in item in the json array?
Any reason for prefering only Property Transfer?
Hey nmrao
I've attached 2 images.
1 image is where I manually executed the property transfers using the 'Run Selected Property Transfer' button (image is entitled PropXfer_ManualRunOfPropertyTransfers.png) and
1 image is where I've executed the test and I'm getting a failed prop transfer (image is entitled PropXfer_AfterExecutionOfTest.png)
Of the 4 property transfers in the images - its 'GetWHBProcGUID' property xfer that fails - and this transfer is linked to the following response (which you might recognise!)
{
"@odata.context" : "https://whatevs.dynamics.com/api/data/v9.0/$metadata#nhs_default_procedures(nhs_default_procedureid)",
"value" : [
{
"@odata.etag" : "W/\"1569419\"",
"nhs_default_procedureid" : "e6de8a88-cad1-e611-80d2-3863bb361018"
}
]
}
groovyguy has given me some whizzy groovyscript that will do the job - its excellent as it breaks the code down into separate sections and comments the different code components very well - however the place I work wants to minimize the groovyscript included as none of the permanent members of staff know groovy and so when all the contractors (me included) leave - there will be no one here to support the groovy - hence the company's desire to minimise the any code in the soapui projects.
As discussed previously - yes this relates to another post I submitted on the forum - but the purpose of this is different. This is to determine why the property transfer doesn't work during execution but does if I manually execute the property transfer.
I need to identify why this fails so should this arise in my future work (as I'm always using the UI's property xfer function) I can resolve the problem!
Many thanks to all for any advice/guidance/hints/tips etc. that anyone can provide! :smileylol:
richie
yeah - you're right - the 2 transfers are for 2 different responses.
The one prop xfer on the 1 response works,
The one prop xfer on the 2nd response doesn't work (which is why I've posted this)
I can't argue with your assertion about using groovy - I actually completely agree with you - but its a decision that's been made waaaaay above my pay grade - its because they won't pay the amount a permanent member of staff would require if they had expert level SoapUI experience - they don't mind paying ridiculous amounts for temporary contractors to come in and do the job (my team are all contractors) but they just wouldn't attract any SoapUI experts for the money they'd pay for a permanent role!
Cheers,
richie
