Contributions
Re: how to stop testsuite execution on teststep failure
Sorry about that. That post was quite old so I thought there could be something in new versions (saw your answer later) But anyways, thanks. I will try to create a feature request sooner.8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0Commentshow to stop testsuite execution on teststep failure
Is there any option to stop testsuite execution on a teststep failure. Most of my testcase in my testsuite depends on first testcase pass/fail criteria. So I want to abort testsuite execution (and mark fail) if my first testcase/teststep fails.8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes2Comments- 8 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes2Comments
- 1.1KViews0likes1Comment
Re: Endpoints Changed to completely different API
So my issues is resolved, and there was no bug in 1.8.5 but the way I had my project resource url was wrong. Most of my testcase had resource path like "/data/ccap/access-nodes/?limit=werwer" with different query parameters or values like: /data/ccap/access-nodes/?limit=2 /data/ccap/access-nodes/?limit=100 /data/ccap/access-nodes/?depth=2 So instead of 4 diff. resources I should have only one resource url "/data/ccap/access-nodes/"with limit as query parameter and any other additional parameter (which won't be passed unless you input any value).8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews1like0CommentsRe: Endpoints Changed to completely different API
I have already reported this issue with support team here: https://smartbear-cc.force.com/portal/SupPortalCaseEdit?caseId=5003900001gx9mUAAQ But they seems to be not able to reproduce the issue so far. mlankfordIs it possible for you to share your project file with them on the above ticket or here.8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes1CommentRe: Endpoints Changed to completely different API
I have also noticed this issue, after upgrading from 1.8.0 to 1.8.5, In my project, many of my Soapui Testcases got mapped to a different request which is the first request in the Project api definition. I check my jenkins job was still running fine with the same project xml file, so I checkout this file again from git but after opening this in soapui 1.8.5 the testcases were mapped to wrong request endpoints. Also even if i correct my testcases to right request and save the project, but when opening the project again in soapui it shows wrong request mapping. Kindly look into this on priority as this is blocking us. Also let me know how I can downgrade to 1.8.08 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes0CommentsGenerate testsuite dialog, option to generate one testcase for one method each
Feature Request: In generate testsuite dialog, we have two options right now. 1. One Testcase for each resource 2. Single testcase with one request for each method But what I want to generate is one testcase for one method i.e. as many testcase as there are methods. Since a single api call is like a testcase for most of us and we can track performance (response time) for each api call (coz junit report contains time take by each testcase) Example: almost all my resource has 5 methods (get, put post delete patch), so if I have 3 resource with 5 methods each, so what I need is 15 testcases in total (one for each method)1.4KViews0likes0Comments