Awesome
Frequent Contributor
Joined 17 years ago
User Profile
User Widgets
Contributions
Assertions failing when using even listener on response
hi, i'm running into the same issue as described in the following post, that my 'contains' assertions don't pass when run from the the testcase and i have to manually run each one or click the 'test' button: viewtopic.php?f=13&t=7174&p=22598#p22598 i've tried three separate event listeners: SubmitListener.afterSubmit RequestFilter.afterSubmit TestRunListener.afterSubmit Each seems to work fine at parsing out the CDATA from my responses; however, the assertions for each one of my responses still fails (i have a wildcard in my assertions as well as a property expansion). thanks for the help!2KViews0likes1CommentRe: An Event Handler to the Rescue
i had a similar problem, i found that there were "left over" chars in my xml that i also needed to parse out (otherwise the xml response had messed up tags), then soapui's outline view correctly displayed the message and i could correctly apply assertions.570Views0likes0CommentsRe: XPath Match Assertion Failing
hi i'm having the exact same issue: when i run my complete testcase my teststep assertions fail; however, they do pass if i run them individually. i tried both events (SubmitListener.afterSubmit, RequestFilter.afterRequest) but i still have the same problem (both events are correctly parsing out the CDATA from my xml though...)1.5KViews0likes0CommentsRe: Deleting REST Resource DELETES ALL related REST TestSteps
that sounds like a good solution. i was able to recreate my rest requests by pulling a previous project file from our svn prior to when i deleted the old resource (thank goodness i check-in my project to version control frequently). nonetheless, this bug could prove to be a big pain, since there's no warning that you'd be losing work/teststeps if you delete a resource! thanks!1KViews0likes0CommentsDeleting REST Resource DELETES ALL related REST TestSteps
hi, this seems like it might be a major bug: i have a REST service with a resource 'A'. i created several test cases with REST teststeps which used resource 'A'. i created a new resource 'B' under the original REST service. i deleted resource 'A'. BUG: all REST teststeps (which depended on resource 'A') in all my test cases have been deleted???? my intent was to go through and manually create new REST teststeps pointing to the new resource 'B'. but now that the original REST teststeps are deleted, i have no reference/recollection of how the REST teststeps were used in the testcases or the assertions that they were using... seems to me like the "orphaned" REST teststeps which used the no longer existing resource 'A', should not have been deleted, but rather marked as 'disabled' indicating that their resource was missing. thanks!3.4KViews0likes4CommentsHow to stop wsdl/endpoint from loading at runtime
hi, when running from either the ui or cmd line, soapui appears to attempt to load the wsdl/ connect to the resource endpoint prior to running any of the testsuites. 1) is there a way to prevent soapui from attempting to load or connect to an endpoint until later on in a testsuite? my initial testsuites actually create and launch the web service application and then the subsequent testsuites connect the endpoint and run the tests. so soapui get's essentially "stuck" attempting to connect to a service that is actually up and running yet.... 2) might also be nice to add a feature to "disable" a resource, for troubleshooting purposes (seems like i can only delete a resource). thanks!1.1KViews0likes0Commentsincreasing the size of the 'resource path' input field
hi, may i request the following, which i think are easy fixes? and will help useability: please see attached image for better description. * increase the size of the 'resource path' input field? some of my paths are long and it's frustrating to use this field when you can't see the full text. * similarly increase the width of the 'resource path' display text in the Navigator. currently the text is truncated, so it's not easy to see the paths, especially if they all all have the same base url. Thanks!3KViews0likes2CommentsBest way to build out REST methods
Hi All, Please see attached screen shot for better description. In SoapUI, i'm building out the REST Methods that let me talk to the RightScale API: ( http://support.rightscale.com/12-Guides ... tScale_API ) I'm a bit unclear what the best practice is to build out the methods for an API: In the attached image you can see outlined in RED that i've added a new RESOURCE for EACH RightScale API call and EACH of it's associated METHOD. VS the outlined in PURPLE in the image, where i have ONE RESOURCE with all the methods contained. each method uses a TEMPLATE override parameter to handle the different path endpoints for each method call. QUESTION: which of the above is the best way to build out the methods for the RightScale API (or any REST API). or is there a 3rd and better method? thank you!1.7KViews0likes1Comment