xavjer
New Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Re: Run TestCase from an other project ...
Sorry, I just saw that with this TestStep its not possible with an other project, only within the same project But this can be achieved by a simple 1liner groovyscript testStep Create a new Groovy TestStep, with the following content: testRunner.getTestCase().getTestSuite().getProject().getWorkspace().getProjectByName("TargetProject").getTestSuiteByName("TargetTestSuite").getTestCaseByName("TargetTestCase").run(context.getProperties(),false);4.3KViews0likes0CommentsTestStep PropertyExpansion
As suggested creating a 'New Idea' of my forum post 1. TestStep expansion It is currently possible to use this property expansion ${#TestCase#MyTestCaseValue} but this one is not possible yet: ${#TestStep#MyCurrentTestStepValue} 2. TestStep expansion by name change Let's assume my TestStep is called: Step1 It has a parameter with name: Value1 So to access it, I currently use: ${#Step1#Value1} Now, when renaming a teststep or cloning it (and giving it a new name), all existing property expansions should also be renamed to reference the new name (In HTTP TestStep for example it should check the endpointURL, the content, the assertions).1.5KViews0likes0CommentsImproving SoapUI TestStep PropertyExpansion
I have two suggestions for the PropertyExpansion 1. TestStep expansion It is currently possible to use this property expansion ${#TestCase#MyTestCaseValue} but this one is not possible yet: ${#TestStep#MyCurrentTestStepValue} 2. TestStep expansion by name change Let's assume my TestStep is called: Step1 It has a parameter with name: Value1 So to access it, I currently use: ${#Step1#Value1} Now, when renaming a teststep or cloning it (and giving it a new name), all existing property expansions should also be renamed to reference the new name (In HTTP TestStep for example it should check the endpointURL, the content, the assertions). This could of course be extended to also do this within all TestSteps when a TestCase/Suite/Project name changes, but I think starting with the TestStep only will already have a huge benefit as many of my Steps have a similar layout and I always clone them1.5KViews1like3CommentsStop creating SoapUICore twice on startup
With the current official SoapUI OpenSource 5.2.1 version, the Core is created twice, which leads to spam in the log and is not very performant. The error resides from the fact, that the Core is already required before the actual setup takes place and therefore a DefaultSoapUICore is created. The problem is inside inner class: com.eviware.soapui.SoapUI.SoapUIRunner Method: run() Invalid parts: The if to check if the updateProvider has to be started and the isFirstLaunch request currently are before the 'new StandaloneSoapUICore()' is being created for the startSoapUI method. This should be moved after this initialisation as it will load the whole Core twice currently, which is leading to problems on my end as I have singleton listeners which are now called twice971Views0likes0CommentsRe: Allow uppercase in URL in the HTTP Request test step
Absolutely agree, the problematic part is in method: com.eviware.soapui.impl.support.HttpUtils.completeUrlWithHttpIfProtocolIsNotHttpOrHttpsOrPropertyExpansion(String endpoint) It lowercases the endpoint to check if it starts with http/https but leaves it in lowercase, which is incorrect17KViews0likes0CommentsSoapUI Action for toolbar button
I am currently playing with the possibilities of extending SoapUI I made a little JDialog settings window which is currently reachable under the context menu by right-clicking on a project. Is there an Action which would allow me to put it into the Toolbar of SoapUI (Where CreateGeneric/ImportExisting/SaveAll/Help etc is) Thanks for any help or suggestions Regards Xavjer1.3KViews0likes2Comments