ole lensmar's blog: SoapUI Plugins

I've created a bunch of SoapUI plugins over the years, primarily for integrating new technologies into SoapUI but also for improving SoapUIs functionality in general and for showcasing its extension possibilities.

The plugins are all hosted on GitHub under the Apache license and downloadable from sourceforge. Installation instructions are provided in the corresponding blog-posts (under the Read more link).

Plugin	Description	Version	SourceCode	Download
RAML / APIHub Plugin	Adds RAML and APIHub import functionality [Read More]	0.2	GitHub	SourceForge
Swagger Plugin	Adds Swagger import and export functionality [Read more]	0.3	GitHub	SourceForge
Groovy Console	Adds an interactive Groovy console for arbitraty scripting tasks. [Read More]	1.0	GitHub	SourceForge
ProgrammableWeb Plugin	Makes it possible to browse and import APIs from the ProgrammableWeb API directory [Read more]	1.0	GitHub	SourceForge
Runscope Plugin	Reroutes all requests through the Runscope platform [Read more]	1.0	GitHub	SourceForge
Email TestStep	Adds a custom TestStep for sending emails from a TestCase [Read more]	1.0	GitHub	SourceForge

Also, be sure to check out the SoapUI Abstract Plugin which makes it easy to get started with your own plugins.

Please don't hesitate to comment with new ideas, complaints or improvements!

/Ole

3 comments:

Christian EscobarMay 7, 2015 at 8:56 PM
Email TestStep works great! For non-Pro users, just create a plugins folder in the SoapUI/bin location, and restart SoapUI!
i.e. C:\Program Files (x86)\SmartBear\SoapUI-5.0.0\bin\plugins

You can verify in the soapui.log file in the bin folder that the UI loaded properly.
UnknownJuly 21, 2015 at 1:24 AM
Can you please let me know what can we include in the message box of the email test Step? Can we use groovy commands or can we try to attach a report or html report file that is generated?
AnonymousMarch 9, 2016 at 9:16 PM
Cool! Hey, is it possible to make SoapUI look for plugins in another folder(s), besides /path/to/soapui/bin/plugins? I'm wanting to have a slim centralized SoapUI directory, possibly with some common plugins (oh, and externals), and then to have individual projects itemize any additional, not-so-common plugins (and/or externals) they need in the individual project folders (e.g., /path/to/project_dir/plugins/not_so_common_plugin.jar and /path/to/project_dir/ext/not_so_common_external.jar).