simonjdonnelly
Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Swagger Compliance Assertion - Is it possible to use a relative swagger url path?
Is it possible to provide a relative path as the URL for a Swagger Compliance Assertion? I know it is possible when using the Schema Compliance assertion for SOAP requests. I've tried various combinations (for example: using ${projectDir} etc.) but with no luck thus far... Swagger Example: <con:assertion type="SwaggerComplianceAssertion" id="678ae158-9e15-418d-b145-65aa7a32bc5e" name="Swagger Compliance Assertion"> <con:configuration> <swaggerUrl>C:\ABC\API\metrics\metrics-v1\swagger\Test.swagger.json</swaggerUrl> <strictMode>true</strictMode> </con:configuration> </con:assertion> WSDL Example: <con:assertion type="Schema Compliance" id="710c1657-1fa0-491a-98b9-c8e4d66169c3" name="Schema Compliance"> <con:configuration> <definition>../mds/apps/services/Testing/App/Proxy/Trial_Business_v1.wsdl</definition> </con:configuration> </con:assertion> If anyone has had any success with this, please let me know. Thanks!Re: how to assign property value (of a response) to a variable, and re-use it in a new request?
You are missing the opening curly brace below: $Nameanddestinationcoding#Request#//Response[1]/SessionId[1]} Try it with the brace: ${Nameanddestinationcoding#Request#//Response[1]/SessionId[1]} This should work If it doesn't, Groovy scripting might be the work aroundRe: how to assign property value (of a response) to a variable, and re-use it in a new request?
Passing the value through as a parameterised version should work then: I don't have any sample REST JSON services to hand, so I've used soap but it shouldn't be too different: Place ${Login 1 - Portal Login#Request#//Response[1]/accessToken[1]} in the second request, where you want the access token previously generated to appear. This will take the value from the test step named 'Login 1 - Portal Login' and take the accessToken from the structure Response > accessToken.Re: how to assign property value (of a response) to a variable, and re-use it in a new request?
Does the accessToken value need to be entered as part of the request XML or as one of the soapui properties? If it needs to be part of the XML, are you not able to pass a tokenised value through i.e. <Test>${Login 1 - Portal Login#Request#//accessToken[1]}</Test> For example purposes: My Login 1 - Portal Login request looks like this: <accessToken>1234</accessToken> so the Test element should be replaced with 1234 upon executing the second request.Re: Connecting to Weblogic JMS Endpoint
Hi, Has anyone been experiencing this issue on 1.9.0? I believe I have tried just about every combination possible for adding the weblogic/wlfullclient.jar to the classpath, to the library etc. Each time the following error is returned: Tue Dec 20 12:07:26 GMT 2016:ERROR:An error occurred [Could not initialize class weblogic.jndi.Environment], see error log for details Tue Dec 20 12:07:26 GMT 2016:WARN:Error Response javax.jms.JMSException: Could not initialize class weblogic.jndi.Environment at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder.createConnection(JMSConnectionHolder.java:101) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestReceiveTransport.execute(HermesJmsRequestReceiveTransport.java:37) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.sendRequest(HermesJmsRequestTransport.java:98) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:126) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Re: Using A Transferred Parameter in a Test Step Request (REST)
No worries. If you click the button next to that, the button circled in blue below: Then, select the XPath Value you want from the pop up and click OK: This should leave you with the actual XPath expression you need to concat with te localhost end point.
