Contributions
Specify memory settings during installation
SoapUI's default memory limits are often too low. This means that every time a new version of SoapUI is released, users like myself must manually edit the Java options. - viewtopic.php?f=1&t=13018&p=31762&hilit=JAVA_OPTS%3D+Xms+5.0.0+java.lang.OutOfMemoryError&sid=df3ff8765d830e8abb96099ef4f344e6#p31762 - http://www.soapui.org/Working-with-soap ... usage.html Do you plan to ever improve this process? It would be nice if, during installation, the program automatically detected total system memory and set an appropriate memory limit. Or alternatively, the user is prompted to enter their desired memory limit. Obviously not a huge issue, but it would save some time and frustration whenever SoapUI is updated and some of our tests begin to fail due to java.lang.OutOfMemoryErrors.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes1CommentRe: [Res] Random order of test cases
Trying putting this script in your TestSuite's "Setup Script". (It requires that all of the TestCases be disabled, but its just a proof-of-concept) // Get list of test cases myTestCases = testSuite.getTestCaseList(); // Shuffle the list long seed = System.nanoTime(); Collections.shuffle(myTestCases, new Random(seed)); boolean aFailureOccured = false; // Run each test case for(testCase in myTestCases){ def properties = new com.eviware.soapui.support.types.StringToObjectMap () def async = false result = testCase.run(properties, async).getStatus().toString(); if (result == "FAILED"){ aFailureOccured = true; } } // Set the TestSuite's result if (aFailureOccured){ runner.setStatus(com.eviware.soapui.model.testsuite.TestRunner.Status.FAILED) } else { runner.setStatus(com.eviware.soapui.model.testsuite.TestRunner.Status.FINISHED) }11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0CommentsRe: [Reg] New test case result: Skipped
Just an FYI (this may help for a temporary workaround): There is already a TestCase result called "CANCELLED". You can force this result from a Groovy Script: testRunner.cancel("My Reason For Skipping This Test Case") You can see these results by using the following code in a TearDown Script: for ( testResult in testRunner.results ) { result = testResult.getStatus().toString(); log.info result }11 years agoPlace ReadyAPI QuestionsReadyAPI Questions985Views0likes0CommentsRe: [Re]Access a test steps ID, within TestRunListener.afterStep
A more direct answer to your question: // Get this test step thisTestStep = testStepResult.getTestStep(); // Get a list of all test steps in the test case myTestSteps = thisTestStep.getTestCase().getChildren(); // Set your desired index (Note: test steps are indexed from 0) int desiredIndex = 4; if ( thisTestStep == myTestSteps[desiredIndex]){ // Do something }11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes0CommentsRe: [Re]Access a test steps ID, within TestRunListener.afterStep
From TestRunListener.afterStep you can access the "testStepResult" variable (a list of all variables appears above the event editor). I did a quick look-up in the API: http://www.soapui.org/apidocs/com/eviware/soapui/impl/wsdl/teststeps/WsdlTestStepResult.html http://www.soapui.org/apidocs/com/eviware/soapui/model/testsuite/TestStep.html You could access the ID by using: testStepResult.getTestStep().getId(); Or if you wanted to check the name of the test step you could use: testStepResult.getTestStep().getName(); Hopefully that helps11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes0CommentsRe: LoadUI 2.6.7 RELEASED
Just curious, where is the changelog for this release? At some point (I have no idea where or how), I found the following page: http://www.loadui.org/Getting-Started-with-loadUI/265-changelog.html But for the latest two releases, the page does not exist: http://www.loadui.org/Getting-Started-with-loadUI/266-changelog.html http://www.loadui.org/Getting-Started-with-loadUI/267-changelog.html I've noticed this issue on both the LoadUI and SoapUI sites, it is extremely difficult to find the patch notes. All these are places that I've looked: http://www.loadui.org/News/loadui-267-is-out.html http://www.loadui.org/About-loadUI/whats-new-in-loadui-26.html http://www.loadui.org/News/11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0CommentsRe: Response time of Javascript
This can be done with Groovy script + Selenium. Selenium is a free web-automation API that supports all the main browsers. Selenium allows you to wait for specific elements on the page to load, like so: wait.until( ExpectedConditions.visibilityOfElementLocated( By.id("my-button") ) )564Views0likes0CommentsRe: [R]SoapUI load test - ${ThreadIndex} in a property-expansion
This doesn't directly answer your question, but this workaround might help you: Try inserting a "DataGen" Test Step at the start of your TestCase. Create a variable called something like "index". Type = "Number" Mode = "Step" Shared = true Start = 0 Step = 1 This will create a variable that will increment by 1 for each thread, thus giving each thread a unique index of sorts. It can be accessed by: ${DataGen#index}11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes0CommentsRe: Custom Script: Project Search within SoapUI
To some extent: yes. However, doing a regular text search will just give you the location of each result and a line number. This isn't super helpful if you want to know which TestSuite/TestCase/TestStep that the result is in. If you want to know that, then you'd have to search backwards inside the document and look for a tag like "<con:testStep ... name=". Its doable, but kind of a pain. My script looks-up and displays the TestSuite/TestCase/TestStep location of each search result automatically, which is pretty helpful. While I'm at it: I've attached a slightly newer version.1.7KViews0likes0Comments