Contributions
Re: WSDL load SoapUI credentials
You're replying to a thread that's 8 years old, and if I am not mistaken, are referencing SoapUI Open Source versus ReadyAPI. You might want to try starting your own thread over in the right community area here.5 months agoPlace ReadyAPI QuestionsReadyAPI Questions6Views1like0CommentsRe: Smartbear Virt server upgrade
You'll probably want to open a support ticket for this. The forums has some really knowledgeable people here with the products themselves, but for activation/installation/etc. issues, that's usually something that requires official support. Smartbear Support Portal7 months agoPlace ReadyAPI QuestionsReadyAPI Questions133Views0likes0CommentsRe: Test Engine and Custom Project Properties
If you are using the command line testrunner.bat/testrunner.sh to run your projects, you can see a list of command line parameters and arguments here. Specifically: -P<args> Specifies a value of a project property for the test run. This value will override the variable’s value during the run. Usage: -P<variable>=<value>. If the value includes spaces, enclose the entire argument in quotes. To override several variable values, specify the -P argument several times.7 months agoPlace ReadyAPI QuestionsReadyAPI Questions220Views3likes1CommentRe: Is there a way to store a global or project property inside a virtualized service response script?
Gotcha, I wasn't certain what you meant in regards to "running in the cloud." That said, I still do not have a good idea of why it would error. What are you seeing as an error message when ran that way??7 months agoPlace ReadyAPI QuestionsReadyAPI Questions392Views0likes0CommentsRe: Is there a way to store a global or project property inside a virtualized service response script?
Not a problem, I really appreciate the chance to help. I love learning, because who knows? I might need to do the same thing down the road. I have a sample groovy script that might work. // Assuming you know how to get the data from the mock Request to save. def propertyValue = "This is a test" // Gets the project we're working in def project = context.mockService.project def testSuite = project.getTestSuiteByName("Test Suite Name") def testCase = testSuite.getTestCaseByname("Test Case Name") def testStep = testCasee.getTestStepByName("Test Step Name") testStep.setPropertyValue("PropertyName", propertyValue)7 months agoPlace ReadyAPI QuestionsReadyAPI Questions505Views1like0CommentsRe: Is there a way to store a global or project property inside a virtualized service response script?
Just to clarify, do you need the virtual service script to write data to a test step, or read from it? Not that it much matters, but I can try to see what I can figure out.7 months agoPlace ReadyAPI QuestionsReadyAPI Questions506Views0likes0CommentsRe: Is there a way to store a global or project property inside a virtualized service response script?
Depending on how you store that data in the script, if you read it from / wrote it to a properties test step, maybe that might work?7 months agoPlace ReadyAPI QuestionsReadyAPI Questions512Views0likes0CommentsRe: Is there a way to change settings to all test cases?
You can accomplish this, as I said, with a groovy script. It's very powerful, but prone to error, so you have to be careful. There's two options here, "failOnError" which is failing as soon as there's a failure with any given step, and "failTestCaseOnError" which marks a test case failed for any given error. I think you want "failOnError" here. That said, here's some code that might help. // assuming you have multiple projects that you want to adjust. def workspace = context.testCase.testSuite.project.workspace; for (p in workspace.getProjectList()) { for (s in p.testSuiteList) { for (c in s.testCaseList) { c.getSettings().setBoolean("failOnError", true) } } }7 months agoPlace ReadyAPI QuestionsReadyAPI Questions263Views1like0Comments