Contributions
Re: Conditional GoTo Test Step on failed assertion
nmrao wrote: Add the assertion for response code in previous step itself to avoid. Hi Rao, Sorry I didn't quite understand what you were trying to explain. You said put 'the assertion for response code in the previous step itself to avoid', what are you asking me to avoid? How would I get to input data into the DataSink with your method?8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes0CommentsRe: Conditional GoTo Test Step on failed assertion
@savithajay wrote: Instead of using 'Goto' test step, can you tryusing groovyscript test step?This gives you more flexibility in catching 404 errors as well from other steps. I would prefer not to write a groovy test script as I'm not thatknowledgeable in writing code, but if I did what would the pseudo code look like? also how would I structure the test case? This is what I envision step 1 run Datasource step 2 run JSON request with assertions step 3 groovy test script tocheck for failed assertions in previous step step 4 only run Datasink to enter in failed request links step 5 run Datasource loop8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes0CommentsConditional GoTo Test Step on failed assertion
Hi, I currently have a Datasource Loop which loops a few 100 calls using different endpoints. Within this loop, I want to write a Conditional GoTo step to write to a datasink when the previous service call step has a failed assertion. The Conditional Goto available will only go to the conditional step if the Condition matches an Xpath Expression however the service I am callingreturns a JSON response and if I click on the 'ns:' iconin the Conditional Goto step, I get an error saying 'Missing response in previous request step [TestStepName]'. Is there a way to do what I want? I forgot to mention that some of the assertion fails are due to 404 errors. Can I capture this as well in the Conditional GoTo step?8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes4CommentsReadyAPI 1.6 data source from excel date field imported incorrectly
Hi, I have found an issue with the latest Pro version of ReadyAPI (V 1.6). When using a Data Source to import a value from an Excel sheet, if the value is a date value, the values are not imported correctly by the Data Source. eg If the date is 04/03/1951 In ReadyAPI (V 1.5) it is imported correctly as 1951-03-04 In ReadyAPI (V 1.6) it is imported incorrectly as 3/4/51 This is a big change to the system (I would think it is a defect as dropping the the first 2 characters of the year portionwould break many tests. How would the system know if wewanted to pass in 19XX or 20XX) and I would appreciate if this could be changed back to the way it worked in prior versions. Thanks.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes1CommentRe: ReadyAPI 1.4.1 Inline Command is always executed
Hi Tanya, There is an issue withthe behaviour from SoapUI Pro 5.1.2 to SoapUI NG Pro using Ready API 1.5.0 with regard to the math.random() function. I have a composite project and have a property in the Test case level with the Value of ${=(int)Math.random()*99999+100001} On SoapUI Pro 5.1.2, this is working as expected with every call creating a new value. On Ready API 1.5.0 the random function does not work at all. All the API call are set to 100001 rather than getting a random variable. Can your team please have another look at this issue please.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions4KViews0likes3Comments