...
- Start SOAtest on your test machine, then create a workspace containing all the projects and test suites that you wish to run as part of your nightly testing process. For more information, see the Setting Up Projects for Existing Tests section above.
- Configure SOAtest's preferences with any global settings that are required for your tests. To open SOAtest preferences, choose Parasoft> Preferences. If the test suites in your workspace were imported from source control, then you should configure the Parasoft> Source Controls settings. You can set preferences as described in the User Guide section on Importing Existing Preferences.
- (Optional) Create a test configuration to use for your nightly test run. Test configurations have settings that affect the way in which your tests are executed. SOAtest ships with a test configuration named Example Configuration that you can use if you do not wish to create your own. Your test configurations can be managed by choosing Parasoft> Test Configurations. If the projects in your workspace were created from source control, then you should click the Common tab in your test configuration then enable the Update projects from source control option.
- (Optional) Create Local Settings Files - Options. This are text files that can be used to control settings for reports, email, Report Center, Team Server, license server, authorship, and source control.
- Schedule a daily process to invoke SOAtest using the desired command line options. This can be done using a job scheduler mechanism such as Windows Task Scheduler or Unix cron. For example, to run all projects in your workspace you can use the following command:
soatestcli.exe -data "c:\mySOAtestWorkspace" -showdetails -config "user://Example Configuration" -report "c:\mySOAtestReports" -publish -localsettings c:\mySOAtestWorkspace\mylocalsettings.properties"
...
- Load Testing: This is now available in a separate installable called Parasoft Load Test. The current version will allow you to run your existing SOA and web load tests as well as create new ones. It also allows you to load test complete end-to-end test scenarios—from the web interface, through services, to the database. Every protocol and test type available in Parasoft SOAtest is supported in Parasoft Load Test.
- Parasoft Load Test includes the full SOAtest product, so if you are interested in both functional testing and load testing, you should install Parasoft Load Test.
- WebKing Paths: WebKing’s Path view has been replaced by Test Suite-based functional tests using Browser Playback tools. The primary benefit is that Test Suite-based functional tests support much more complex web applications (like RIA and AJAX applications). Moreover, the new implementation follows a consistent test configuration paradigm that supports end-to-end testing. Paths in existing .wkj files can be executed in SOAtest 9.x, but they cannot be edited or extended.
- WebKing Publishing: This functionality is not applicable to SOAtest 9.x.
- Capture HTTP Traffic Tool: This tool is no longer supported. If this functionality is needed, a free tool like WireShark can be used to save the HTTP trace to a file, then the "Generate tests from traffic" option can be used to create tests from it.
- Specific XML Validator Options: The XML DTD preferences and validating against DTD options are no longer available.
- Management Reports: Report enhancements are planned. SOAtest will report all meta-data to Report Center and Report Center will be able to generate different kinds of reports.
- CLI commands:
- -run: This command, which is for running custom Jython scripts through SOAtest, is deprecated. Please contact Technical Support for assistance migrating scripts to 9.x.
- -runtest: This command is replaced with new CLI options. See the Migration Guide topic on Command Line Interface Migration for details.
- -wsdl
- -reportAllTraffic
- -traffic