lermimou
Occasional Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Re: XPath Expression to RawRequests doesn't work after update to 1.8 version
the expected value is the value of the request parameter filled the dynamic property filled example: <urn:in0>hello20160726113826130@test.fr</urn:in0> That's why i need the real value sent in the request (actually, only accessible through the rawRequest)2.3KViews0likes0CommentsRe: XPath Expression to RawRequests doesn't work after update to 1.8 version
Hi, Thanks for your answer. I defined my property in the project custom property with this value : ${=new java.text.SimpleDateFormat("yyyyMMddHHmmssSSS").format(new Date())} So everytime i used this property, a new timestamp is generated. I aggre with you, the property expansion expand the property in the assertions but a new value. I hope this bug will be fixed asap.2.3KViews0likes1CommentRe: XPath Expression to RawRequests doesn't work after update to 1.8 version
For Example, this is my request. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="http://urn:MEWSUserPref"> <soapenv:Header/> <soapenv:Body> <urn:HelloWorld> <urn:in0>hello${#Project#timestamp}@test.fr</urn:in0> </urn:HelloWorld> </soapenv:Body> </soapenv:Envelope> In the assertion, i compare a parameter to the in0 request parameter declare namespace ns1='http://urn:MEWSUserPref'; //detail[1]/ns1:MEServiceException[1]/ns1:in0[1] ${myTestCase#Request#declare namespace urn='http://urn:MEWSUserPref'; //urn:setFilterSettings[1]/urn:in0[1]} With this method, everytime i launch the assertion, a new timestamp is generated, due to the dynamic parameter. I need to check the parameter sent in the request so i used the RawRequest ${myTestCase#RawRequest#declare namespace urn='http://urn:MEWSUserPref'; //urn:setFilterSettings[1]/urn:in0[1]} In this case, the parameter is always the same in the assertion. The same problem appears with propertyTransfer steps. The Request option transfers the ${#Project#timestamp} instead of the timestamp generated in the request. How can i check these cases without the rawRequest?2.4KViews0likes2CommentsRe: XPath Expression to RawRequests doesn't work after update to 1.8 version
Hi, I my requests, i have thousands of parameters like <urn:transactionId>${#Project#transactionId}</urn:transactionId> So i can't use the request to retrieve the parameter. I needed to use the rawRequest to have the parameter filled. It's not possible to me to switch all parameters like <urn:transactionId>${#Project#transactionId}</urn:transactionId> to a propertyTransfer in the request. Please, how can I do?2.9KViews0likes1Comment[Ready API 1.8.0] Can't transfer property from rawRequest.
Hi, with this new version, i can't no more transfer properties from a rawRequest. It worked with the last version, maybe it's due to the new feature : The RawRequest custom property of the SOAP Request, REST Request and HTTP Request test steps now includes request headers too. (SOAP-5349) I have the error : [Error parsing source property [error: Unexpected element: CDATA]] I can't access to the rawRequest in the source tab.962Views0likes1Comment