Contributions
Re: Option to avoid appending REST resources to endpoint?
Hi Ole, We've considered doing that, but unfortunately we had template ids in almost every endpoint, e.g.: http://www.xxx.com/ws/get/{item}/details where {item} is a TEMPLATE and needs to be replaced with a valid value during request. In 4.0.1 even though a value is given for the TEMPLATE, it wasn't providing any value(due to lack of resource appending) and so we chose not to provide any values for various TEMPLATE items and provided a specific endpoint for each test case. Now in order to adapt to 4.5.1, we need to change each test case to provide a value for TEMPLATE so it gets correctly appended to the endpoint. As this requires a modification at a test case level, wanted to check out any option to disable resource appending. Thanks!12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0CommentsOption to avoid appending REST resources to endpoint?
Hi, We've been using SoapUI pro 4.0.1 to test REST services and upgraded to 4.5.1. In 4.0.1 We've added the WADL file for REST which gives the resources and developed automated tests. With 4.0.1 it didn't have the feature of appending REST resource or method to the endpoint, so we gave the entire URL(including the resource path) as the endpoint. After the upgrade since 4.5.1 is automatically appending the REST resource/method to the endpoint, all the automation suites started failing. Eg: wadl has two resource paths /ws/getSomething /ws/putSomething and the endpoint is http://www.xxx.com With 4.0.1 when the tests are developed, we had two endpoints http://www.xxx.com/ws/getSomething and http://www.xxx.com/ws/putSomething depending on the service used. However, after the upgrade the endpoint becomes http://www.xxx.com/ws/getSomething/ws/getSomething (as it appends the resource path which is /ws/getSomething to the original endpoint) and so it breaks all tests. Understand that this is a feature of latest version, but we don't have time to change the tests right now so would like to see if there is any option to disable this. Moreover, in some cases we need to use a different endpoint than the one which is formulated this way, what could we do to fix this?12 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes3CommentsRunning a specific test suite using maven-soapui-pro-plugin
Hi, I'm using maven-soapui-pro-plugin V3.6.1 to run soapui tests using maven. I'm able to run a composite project with this plugin by giving the project path: <plugin> <groupId>eviware</groupId> <artifactId>maven-soapui-pro-plugin</artifactId> <version>3.6.1</version> <executions> <execution> <id>run-tests</id> <phase>integration-test</phase> <goals> <goal>test</goal> </goals> </execution> </executions> <configuration> <printReport>false</printReport> <projectFile>/Applications/eviware/soapUI-Pro-4.0.0.app/Contents/Resources/app/bin/simplecompositeproject-soapui-project</projectFile> <outputFolder>${basedir}/target/soapui</outputFolder> ... ... ... </configuration> </plugin> This way all the test suites(there are 6 test suites in that project) in that project are getting executed but I want to specify only one test suite to be executed. How can this be acheived? Which testrunner does the pro plugin use or how can it be configured to pick only one test suite? Thanks, Sahitya13 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes2Comments