Unplanned
Last Updated: 07 Oct 2016 13:35 by John
John
Created on: 19 Sep 2016 15:52
Type: Feature Request
3
Import Soap UI Projects into Test Studio
I have a suite of tests already written in Ready API/Soap UI.  I'd really, really like to be able to migrate to your product once it has scripting.  However, it'd be nice to be able to automate some of that work with an "Import from Soap UI" feature that would take my existing Soap UI project and convert it into a Test Studio project.
2 comments
John
Posted on: 21 Sep 2016 20:37
I would say you definitely want to have some pre-canned assertions such as regex and JSON path validation.  As far as scripting goes, I can understand the value of supporting JavaScript since it's so ubiquitous and easy to integrate.  I would also like to be able to use PowerShell because of its power and tight integration with .NET.

As far as having to compile code such as C#, that'd be acceptable for writing plug-ins, but that would likely slow down test development.
ADMIN
Oleg
Posted on: 21 Sep 2016 16:17
Hi,

Thank you for your interest in Test Studio for APIs. We are indeed considering an import of projects from third-party tools as a viable feature. We are still involved into the implementation of more basic features with higher priority though so we cannot say yet if and when we would be able to focus on importing from specific tools like SoapUI, but we will definitely consider it seriously. We are currently working on a basic import of http sessions from Fiddler that could be useful as a middleware for import of automated or manual requests as long as they are captured with Fiddler. The feature is still in beta version, but I hope it will be of good use. Please feel free to give it a try in our next release.

I would like to ask you though for more feedback about what would you expect as a scripting story in Test Studio for APIs. We are evaluating different approaches that we could take in this direction like adding test steps with JavaScript or other scripting language, or maybe .Net code that would require compilation. Alternatively we could add the ability to execute external executable files like powershell, batch files, etc. We could add UI steps for common operations like math expressions, random data generation, etc. or leave it all to coded steps for more flexibility.
Any feedback on how would you prefer to use scripting is highly appreciated so that we can build the tool the way that best fits your needs.