ContributionsMost RecentMost LikesSolutionsRe: RandomStringUtils.random variation locks up soapuiHi SiKing, With your script I have now got my problem sorted. Thank you very much for your assistance. Regards, JamesRe: RandomStringUtils.random variation locks up soapuiHi SiKing, thanks for your reply and the new link. Where is the info about what versions are used, on the Codehaus or SmartBear website? Possibly because I've not had enough coffee yet, but your answer doesn't make it any clearer. I would be grateful if you could you kindly provide an example, thanks. Regards, JimLinRandomStringUtils.random variation locks up soapuiHi, I have a small script for generating a random 3 digit numeric/alphanumeric string which works without issue: import org.apache.commons.lang.RandomStringUtils //Random 3 digit string String randomString = (RandomStringUtils.random(3, false, true)) The 'false/true' above sets numbers and/or letters. I now need one that generate a random 3 digit string, but between specific limits, i.e. starting at 1 and finishing at 193. Looking at this page http://commons.apache.org/proper/commons-lang/javadocs/api-2.6/org/apache/commons/lang/RandomStringUtils.html, this variation seems to fit the bill 'RandomStringUtils.random(int, int, int, boolean, boolean)' - which represents ' - 'int count, int start, int end, boolean letters, boolean numbers', however, when I add in the start and end integers, soapui locks up and the only thing to do is kill it in task manager. This happens when used in a Groovy step in a test or via the Groovy console. Does anyone have any suggestion as to what it causing the issue. It's a tiny script, so I'm surprised it causes me such issues.Re: Getting Testrunner/Maven to skip testsuite setup scriptHi redfish4ktc2, Thanks for the suggestion, that works well. Cheers, JamesRe: Calling different APIs with Maven/JenkinsHi, firstly, my apologies for not replying, I hadn't realised you had replied. I have solved my problem to an extent. I had made a fundamental error in not realising that you could add multiple APIs to one project, and had created two projects, one for each API. Once I created a project with both APIs added, I was able to get my tests running after a small amount of Groovy reconfiguration. Regards, JamesRe: trim zeros after retrieving val from db queryI use this in a Groovy step. You can adjust the number of digits by increasing or decreasing the -3: // Remove trailing zeros def firstDepositMinusZero = firstDeposit[0..-3] as int Getting Testrunner/Maven to skip testsuite setup scriptIs it possible to get Testrunner/Maven to skip a testsuite setup script? For my testsuites I have a startup script that brings up a dropdown list to choose which environment to run the tests in (we have 5 different ones). This is intended for running the testsuites manually. Now I'm moving on to initiating these tests with testrunner/Maven, having a manual selection box come up is a pain when doing automated tests and I've temporarily hashed the code out. Is there a way of skipping the setup script?Calling different APIs with Maven/JenkinsHi, I have searched on this forum and know that this question has been asked in a number of different ways, but I can't find one that seems to fit my issue. I have Googled extensively and can't find an answer that fits there either. I'm after some advice or suggestions to help me run my regression tests using TestRunner/Maven/Jenkins. I'm using SOAPUI Pro, but posting in the general board as it is not a Pro specific issue (I don't think). All of my tests are regression tests of some sort and as such do sequential calls against different APIs, i.e. call an Account API to create an account, then use a Payment API to add a credit card and money to the account, make a withdrawal, then call the Account API again to add a limit to the account, etc. These tests and testsuites work fine when run from within SOAPUI, but fail when I run the using TestRunner/Maven/Jenkins. I’ve found out from these forums (5th post down: viewtopic.php?f=5&t=2323), that Test runner will only call one API per test suite, rather than loading the workspace containing all of them. There is a suggested fix, which is to create a test suite which will check whether a workspace is loaded and if not load one, but I’m a bit out of my depth on the Groovy coding, so I’m stuck and unable to progress things. I’m not completely convinced it will completely cure my situation anyway, as other posts go on about reporting issues when doing this. I wondered whether anyone has encountered this issue before, had any tests similar to this and if so, how you got around it. Any assistance or advice to help me progress would be greatly received Cheers, James EDIT I should add that the APIs are located in different projects as well.Re: Extracting an account number from an HTTP raw responseHi Wehrmacht, I had come to a similar conclusion and think it's something to do with the construction of the WADL, I need to get some time with the developer who created it. I have realised that there is another API call that makes the account number field available in the normal way, so I've gone down that route for the time being. I'll update this post if I find a solution. Cheers, JamesRe: Extracting an account number from an HTTP raw responseHi Wehrmacht, Thanks for the reply. I'm not sure what you mean by 'Download all the xml resources'. There is no xml being displayed. the only results tab that is populated is the Raw one, all the rest are blank. Cheers, James