|
We have just release soapUI Pro 2.0. And Boy, do we have some neat features! As a soapUI Pro License Holder you are most welcome to download them and try them out.
Get it here!
The functionality!
The functionality:
As the first testing tool in the world soapUI releases support for WSDL Coverage analysis. With one simple analysis run you can see how much of the tests are covered by your tests, see a coverage report per request and all the way down to which element is tested.
This is integrated into the test development process and as you create tests you will see the coverage increase. This exclusive functionality will increase development quality, speed and make the Web Service testing faster than ever before.
Test Refactoring enable you to refactor all your tests as the WSDL is updated. Run "Refactor Endpoint" on your project in order to update your tests. Test Refactoring will take into account how the updated WSDL affects your XPath expressions.
Test Refactoring will save you man hours upon man hours and will enable you to focus on writing tests, not updating them. This makes soapUI a perfect tool for Agile Web Service Testing.
In soapUI 2.0 we introduce an efficient way of managing requirements and connecting these to the tests in soapUI. Create or import requirements, choose which TestCases meets which requirements and see requirement fulfillment.
soapUI Requirements is a welcome addition for the professional user, providing the opportunity to integrate your testing tool in the requirements management process.
In soapUI Pro you have earlier been able to get data for your functional testing by the DataSource TestStep, but not been able to put data from your test in a database. soapUI Pro 2.0 introduces the DataSink TestStep which enables you to put data from you?re your TestResponses in a database, Excel file or csv-file.
As a complement to the test quality inspectors in soapUI, we now introduce the Memory Log. The Memory Log will enable you to monitor Memory Consumption during tests.
soapUI introduces comprehensive support for Web Service Security with support for the following WS-Security standards;
- OASIS Web Services Security: SOAP Message Security 1.0 Standard 200401, March 2004
- Username Token profile V1.0
- X.509 Token Profile V1.0
The addition of WS-Security support in soapUI makes it possible for soapUI users to;
- Sign Web Service Messages
- Encrypt Web Service Messages
- Authenticate through the usage of tokens
- Use SAML Assertion insertion
- Message Capturing and Recording!
soapUI 2.0 contains a SOAP Monitor for capturing live traffic. The SOAP Monitor can be run in both Tunnel and Proxy Modes. From the traffic captured in soapUI SOAP Monitor you can;
- Create requests
- Create TestCases
- Create MockServices
Launch it by right clicking a project and choose "Launch SOAP Monitor".
We have long looked for a way of building chains of tests where TestCases depend in each other. The solution is here in the form of the Run TestCase TestStep. The Run TestCase TestStep allows parameter input and output.
- Setup and Teardown scripts
Any TestSuite or TestCase can now have Setup and Teardown scripts just like Unit tests. These scripts can be used to create time stamps, write test results to a file or even send mail!
You can now disable TestCases in order to skip them in TestSuite runs.
You can now disable assertions in TestSteps.
soapUI MockServices now supports SSL for Service Mocking of SSL Web Services.
- MockService WSDL Exposure
In order to make soapUI Mocking even more like the real thing you are now able to expose the WSDL for all MockServices in soapUI.
- Mocking Start and Stop Scripts
You are now able to run scripts at the start or stop of MockServices. This gives you the ability to manipulate properties, context variables or other when you start or stop a MockService.
When you double click a soapUI Project, you now get the soapUI Project Overview. This project overview will show;
- Project Metrics
- Load Save Scripts
- TestSuite Editor run log
Like TestCases before, TestSuites now sports a log window showing each step run in a TestCase. Double Click any logged event in the TestSuite log to see the actual content of the step.
You are now able to create and use properties on the following levels;
- Global Properties
- Project Properties
- TestSuite Properties
- TestCase Properties
You can now have the ability to view properties directly in the tree navigator. This has two advantages;
- You are able to get better overview of the properties available
- You can drag a property from the tree to any Request element for an instant PropertyExpansion
- The Extended Properties View is toggle able.
- TestCase Log improvements
In the TestCase Log you now can limit output and logged results to preserve memory under long running tests.
You can also generate MockServices from TestCase execution
And of course;
a large number of bugs, issues, etc... have been fixed thanks to our users' fantastic support and enthusiasm. Thank you all!!
More about Properties Management
Properties can then be used in levels below the property. That mean you are now able to share Properties such as user names and passwords in between for example TestCases. PropertyExpansions and PropertyTransfers have been extended accordingly.
While the old TestStep properties remain unchanged the syntax of the new properties is extended. They now can refer to properties in other levels in the soapUI hierarchy by explicitly stating which property at which level you are referring to. Properties now have the following Syntax;
${#Scope#Property-name[#xpath-expression]}
${Property-name} refers to a Global Property (example: ${UserName} to a global Property named "UserName")
${#Project#Property-name}refers to a Project Property (example: ${#Project#UserName} to a Property on Project level named "UserName")
${#TestSuite#Property-name} refers to a TestSuite Property (example: ${#TestSuite#UserName} to a Property on TestSuite level named "UserName")
${#TestCase#Property-name} refers to a TestCase Property (example: ${#TestCase#UserName} to a Property on TestCase level named "UserName")
${TestStep-name#Property-name} refers to a property in a named TestStep.
The following rules apply:
- Excepting TestSteps, you can only refer to properties in a path straight ascending from where you are
- Only TestSteps are referred to by name
- If you are running soapUI from command line, Global Properties will be overridden by file based Global Properties (read more about [these here])
- You can drag a Property to an element in a TestRequest in order to create an automatic PropertyExpansion. You can also rename a Property without fear of breaking any tests; references to Properties automatically reactors themselves, rename a property and all PropertyExpansions will rename themselves.
|
