Contributions
Re: [RESOLVED] Get data to run in parallel threads
I have a more subtle question... how do I model client-side parallelism? That is: in a test case, some activities are done sequentially, then some are done in separate threads, then some more in series, etc. I don't just want to run all my steps in a suite at once. I made a bit of progress threading teststeps in Groovy, but unfortunately I'm passing parameters to them via property expansions on the TestCase - which is shared between all the steps, and thus they overwrite each other's data. Am I trying to hit a nail that SoapUI won't hammer, or is there a better way?1.2KViews0likes0CommentsRe: Inserting a random ID into a request parameter
It's not perfect, but this is one way: <tem:Type>ID</tem:Type> <tem:Value>${#TestCase#thingValue}</tem:Value> Then in the Ruby bit: testRunner.testCase.setPropertyValue('thingValue', idnos[(rand.nextInt(3))].toString()); [edit: http://www.soapui.org/userguide/properties.html ] You can probably be a lot neater than this, though.1.5KViews0likes0CommentsRe: Things we love about SoapUI
Oh, come on people. More: I love the fact that I can write a bunch of functional test steps, then call them from a Groovy script. Then, for free, I get a Load Test. Even the fact that they're getting called from a Groovy script doesn't stop the steps appearing in a load test report with accurate data about how long they took to run, how often they individually got called, how much data was involved and how many times they failed. And that (for a while, I wish this was configurable) the log entries for those failures magically click through to data on what went out and what came back, for that step.15 years agoPlace ReadyAPI QuestionsReadyAPI Questions745Views0likes0CommentsThings we love about SoapUI
Nearly all the threads on this forum are help requests (even though those should really go in the other one). Those that aren't are mostly complaints. The thing is, though I file bug reports and ask for help as much as anyone, I really do like SoapUI. So... what do you really like about it? I'll get the ball rolling - I like the way you can look at a piece of an XML response, and through the GUI, semi-magically create a property transfer with the XPath already done for you. - I like the way you can get to nearly everything through Groovy, if you have the patience to look through the JavaDoc. - I like the fact that the developers fixed the command-line interface when I filed a bug, allowing me to get back to work using the nightly build, when I was otherwise screwed.15 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes2CommentsRe: Interpreting LoadTest Reports
Kade wrote: The cnt for each step shows 39 and the test case total cnt shows 39. What I am trying to analyze is the total number of requests that were sent during the test duration of 60 seconds. Would it be 390? (10 steps x 39 cnt = 390)? Yes712Views0likes0CommentsRe: slow load test when using Groovy
sadia wrote: i am expecting that each thread will execute the script, increment the counter and pick the next value from file and copy into request. IS IT CORRECT UNDERSTANDING? Possibly not. Can you post the Groovy script you are using? Since there are many ways to do what you describe, some of them error-prone, it would be easier to help if we could see the piece of code in question. J1.1KViews0likes0CommentsRe: slow load test when using Groovy
Richards wrote: pick random credential,1,41,0.01,0,8669,28.9,0,0,0 It looks like the Groovy step is running pretty quickly. Could it be the randomness of the credential that is causing your SOAP operation to be slower? ie., is SoapUI just reporting the behaviour it sees? Can you verify independently that the operation is still running as fast as you think it is, from the server side?1.1KViews0likes0CommentsRe: Data Driven from Excel
kishore.konka wrote: I need to add more than 500 property names for each test case ,but is tedious process to add that many property’s for each test case by clicking. Please let me know is there any option in tool to import the properties names from external source like Excel. There isn't a way to do it using the tool itself, but you can do it with a Groovy TestStep a bit like this: Assume you have a dataSource for your property names, called something like 'propertyNames', that exports each row as a property on itself called 'name'. def dataSource = testRunner.testCase.testSteps['propertyNames']; getNewProperty = { if (!dataSource.next(testRunner, context)) { dataSource.run(testRunner, context); } return dataSource.properties['name'].value; } getNewValue = { // Put whatever you want in here! // You could even have your Excel datasource export the name/value pairs, and fold this in. } for (int i = 0; i < 500; i++) { testRunner.testCase.setPropertyValue(getNewProperty(), getNewValue()); } NOTE that this is cribbed from my own projects but I haven't run the code precisely as written - should be fine though.800Views0likes0Comments