Contributions
Do SOAPUI provide a switch to run a testsuite
Hi, I have a requirement where in SOAPUI Project I need to have some setup which is disabled by default in the project and I need to enable it just on certain environments like DEV or INTE: For e.g. by default the setup is disabled and the project uses some hard coded account values which should be used in CI environment. However while running the same project on DEV Or INTE it enables the setup and dynamically create the accounts and use those acounts instead of hardcoded values. Is it possible to have such a switch at project level in soaui Many Thanks, Vivek7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes5CommentsRe: Repeat a Test Step until you get desired response and then move to next step.
Thanksgilugopifor you reply. I tried belwo loop to repeat "TestStep_101" in my tests until its status is success but it goes to indefinite loop. How to make this come out of the loop as soon as the responseAsXml contains success. def responseAsXml = context.expand( '${TestStep_101#ResponseAsXml#declare ns1:payments[1]/ns1:payment-state[1]}' ) while (['success'].contains(responseAsXml) == false ){ testRunner.runTestStepByName('TestStep_101') } Cheers. Vivek8 years agoPlace ReadyAPI QuestionsReadyAPI Questions9.1KViews0likes4CommentsRepeat a Test Step until you get desired response and then move to next step.
Hi, I have a requirement where I am querying using a GET Request or say a DB select. This is async service which returns me a state say "in-progress" . Then I added a step called delay with 2 seconds delay and checking the status again as it should be "success" or "fail". However this is not good approach and fails sometimes on different servers. I am looking for some solution how I can do this? I tried few stuff with Groovy and Data Source Loops but still don't know which is the best approach. Also, for how long shall I loop. It might happen that there is some deadlock on DB Level and this might loop for ever. Shall I have some limit also say 5 seconds or something. I have attached structure of my project. I need to re-run the step called "Verify Payment Status in DB" until status is success and then move to other steps. Any help will be much appreciated. Thanks, VivekSolved8 years agoPlace ReadyAPI QuestionsReadyAPI Questions9.2KViews0likes6CommentsHow to Verify XML Assertions in ReadAPI where response doesnt always come in Order
Hi, I have a query regarding assertions. I have to assert some XML Response where my application Returns two error codes. However they always dont come in same order. For e.g. if you see below sometimes the first errror code is returned as 400.1109 or 400.1009. If I use Assertion like below it Fails some times. How to resolve such assertions in easiest possible way. Do we have something like OR (||) in SoAPUI declare namespace ns1='http://www.xxx-payments.com/schema/payment'; //ns1:multi-pm[1]/ns1:multi-pm-statuses[1]/ns1:status[1]/@code <multi-statuses> <status code="400.1109" description="xxxxxx Please check your input and try again." severity="error"/> <status code="400.1009" description="yyyyy. Please check your input and try again." severity="error"/> </multi-statuses> <multi-statuses> <status code="400.1009" description="yyyyy. Please check your input and try again." severity="error"/> <status code="400.1109" description="xxxxxx Please check your input and try again." severity="error"/> </multi-statuses>8 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes2CommentsWhy I get org.reflections.ReflectionsException when running ReadyAPI Project from Maven Command
Hi, I am using licensed Version of Ready API 1.8.0 and recently upgraded to 1.9.0. However, After this I faced lots of issues and rolled back to 1.8.0. The main issue I am facing right now is that the tests are green when I run it from ReadyAPI, but when I run it via Maven command I can see below warnings in the logs: I have all the required plugins in [C:\Users\vivek.malhotra\.soapui\plugins\ready-api-git-plugin-1.1.0.jar]. Why it complains to load the plugins? 10:38:45,963 WARN [PluginLoader] Could not load plugin from file [C:\Users\vivek.malhotra\.soapui\plugins\ready-api-git-plugin-1.1.0.jar] org.reflections.ReflectionsException: could not get type for name com.smartbear.readyapi.plugin.git.GitPluginConfig at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:389) at org.reflections.ReflectionUtils.forNames(ReflectionUtils.java:398) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:385) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:370) at com.eviware.soapui.plugins.PluginLoader.readPluginConfigurationClasses(SourceFile:77) at com.eviware.soapui.plugins.PluginLoader.a(SourceFile:59) at com.eviware.soapui.plugins.PluginManager.loadPlugins(SourceFile:92) at com.eviware.soapui.SoapUIPro$SoapUIProCore.loadPlugins(SourceFile:811) at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:142) at com.eviware.soapui.SoapUIPro$SoapUIProCore.init(SourceFile:801) at com.eviware.soapui.SoapUIPro$SoapUIProCore.<init>(SourceFile:764) at com.eviware.soapui.SoapUIProTestCaseRunner.createSoapUICore(SourceFile:200) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:178) at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:134) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) 10:38:45,965 INFO [PluginLoader] Adding plugin from [C:\Users\vivek.malhotra\.soapui\plugins\ready-jira-plugin-1.1-dist.jar] 10:38:46,830 WARN [PluginLoader] Could not load plugin from file [C:\Users\vivek.malhotra\.soapui\plugins\ready-jira-plugin-1.1-dist.jar] org.reflections.ReflectionsException: could not get type for name com.smartbear.ready.plugin.jira.PluginConfig at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:389) at org.reflections.ReflectionUtils.forNames(ReflectionUtils.java:398) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:385) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:370) at com.eviware.soapui.plugins.PluginLoader.readPluginConfigurationClasses(SourceFile:77) at com.eviware.soapui.plugins.PluginLoader.a(SourceFile:59) at com.eviware.soapui.plugins.PluginManager.loadPlugins(SourceFile:92) at com.eviware.soapui.SoapUIPro$SoapUIProCore.loadPlugins(SourceFile:811) at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:142) at com.eviware.soapui.SoapUIPro$SoapUIProCore.init(SourceFile:801) at com.eviware.soapui.SoapUIPro$SoapUIProCore.<init>(SourceFile:764) at com.eviware.soapui.SoapUIProTestCaseRunner.createSoapUICore(SourceFile:200) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:178) at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:134) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) 10:38:46,831 INFO [PluginLoader] Adding plugin from [C:\Users\vivek.malhotra\.soapui\plugins\ready-mqtt-plugin-dist.jar] 10:38:46,867 WARN [PluginLoader] Could not load plugin from file [C:\Users\vivek.malhotra\.soapui\plugins\ready-mqtt-plugin-dist.jar] org.reflections.ReflectionsException: could not get type for name com.smartbear.mqttsupport.PluginConfig at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:389) at org.reflections.ReflectionUtils.forNames(ReflectionUtils.java:398) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:385) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:370) at com.eviware.soapui.plugins.PluginLoader.readPluginConfigurationClasses(SourceFile:77) at com.eviware.soapui.plugins.PluginLoader.a(SourceFile:59) at com.eviware.soapui.plugins.PluginManager.loadPlugins(SourceFile:92) at com.eviware.soapui.SoapUIPro$SoapUIProCore.loadPlugins(SourceFile:811) at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:142) at com.eviware.soapui.SoapUIPro$SoapUIProCore.init(SourceFile:801) at com.eviware.soapui.SoapUIPro$SoapUIProCore.<init>(SourceFile:764) at com.eviware.soapui.SoapUIProTestCaseRunner.createSoapUICore(SourceFile:200) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:178) at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:134) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) 10:38:46,867 INFO [PluginLoader] Adding plugin from [C:\Users\vivek.malhotra\.soapui\plugins\ready-uxm-plugin-1.0.jar] 10:38:46,886 WARN [PluginLoader] Could not load plugin from file [C:\Users\vivek.malhotra\.soapui\plugins\ready-uxm-plugin-1.0.jar] org.reflections.ReflectionsException: could not get type for name com.smartbear.ready.PluginConfig at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:389) at org.reflections.ReflectionUtils.forNames(ReflectionUtils.java:398) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:385) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:370) at com.eviware.soapui.plugins.PluginLoader.readPluginConfigurationClasses(SourceFile:77) at com.eviware.soapui.plugins.PluginLoader.a(SourceFile:59) at com.eviware.soapui.plugins.PluginManager.loadPlugins(SourceFile:92) at com.eviware.soapui.SoapUIPro$SoapUIProCore.loadPlugins(SourceFile:811) at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:142) at com.eviware.soapui.SoapUIPro$SoapUIProCore.init(SourceFile:801) at com.eviware.soapui.SoapUIPro$SoapUIProCore.<init>(SourceFile:764) at com.eviware.soapui.SoapUIProTestCaseRunner.createSoapUICore(SourceFile:200) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:178) at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:134) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) 10:38:46,886 INFO [PluginLoader] Adding plugin from [C:\Users\vivek.malhotra\.soapui\plugins\soapui-swagger-plugin-2.5.1-dist.jar] 10:38:47,081 WARN [PluginLoader] Could not load plugin from file [C:\Users\vivek.malhotra\.soapui\plugins\soapui-swagger-plugin-2.5.1-dist.jar] org.reflections.ReflectionsException: could not get type for name com.smartbear.swagger.PluginConfig at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:389) at org.reflections.ReflectionUtils.forNames(ReflectionUtils.java:398) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:385) at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:370) at com.eviware.soapui.plugins.PluginLoader.readPluginConfigurationClasses(SourceFile:77) at com.eviware.soapui.plugins.PluginLoader.a(SourceFile:59) at com.eviware.soapui.plugins.PluginManager.loadPlugins(SourceFile:92) at com.eviware.soapui.SoapUIPro$SoapUIProCore.loadPlugins(SourceFile:811) at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:142) at com.eviware.soapui.SoapUIPro$SoapUIProCore.init(SourceFile:801) at com.eviware.soapui.SoapUIPro$SoapUIProCore.<init>(SourceFile:764) at com.eviware.soapui.SoapUIProTestCaseRunner.createSoapUICore(SourceFile:200) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:178) at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:134) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)8 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes0CommentsRunning Selected Test Suites in parallel but not all Test Suites under one Project.
Hi All, I know we about the option where we can run the test suites in a project in parallel or even test cases in a particular test suite. However, I would like to know if there is an option to to run only selected test suites in parallel. For Instance, I have a project containing 10 test suites. The first Test Suite is my Setup Part which should always run first as it sets up some important configuration which will be used by all the tests. Then I have 8 test suites which can run in paralled. Then my last test suite, 10th Test suite is my cleanup, whcih should always run last. Can we achieve this order with ReadyAPI 1.9.0 And also, will this order be maintained, if I run the entire Project on Jenkins using Maven. Thanks, Vivek Malhotra8 years agoPlace ReadyAPI QuestionsReadyAPI Questions938Views0likes1Comment