...
SOAtest’s command line interface (soatestcli) allows you to perform static analysis and execute tests as part of an automated nightly process. Command line mode is available for the Automation Edition of SOAtest and is compatible with Docker deployments.
soatestcli can send results to the Parasoft Report Center and send focused reports to each team developer and tester working on the SOA project. Reports can be generated in a number of formats. Details such as reporting preferences (who should reports be sent to, how should those reports be labelled, what mail server and domain should be used, etc.) Team Server settings (deprecated), Report Center settings, and email settings, license settings, etc. can be controlled by settings files.
...
Setting Up the CLI
Parasoft SOAtest has has two user modes: interactive desktop usage in the GUI and command line mode via the command line interface (CLI). The CLI interface is a standard feature of the Automation Edition.
...
As part of the execution, SOAtest can can use your SCM client (if supported) to automatically retrieve file modification information from the SCM system and generate tasks for specific individuals based on results of code analysis and executed tests.
Specific execution options for SOAtest are controlled via Test Configurations and PreferencesPreferences.
Test Configurations can be sourced from the built-in set, or created using SOAtest interactive mode in the GUI. We suggest using the built-in configurations as starting templates for customer-specific configurations, which are then stored on disk or on Parasoft Team Server (deprecated).
Preferences can be configured from the SOAtest GUI. Most of the preference settings can also be supplied with a configuration file that is provided as a parameter to a CLI call. A table of the configuration file preference settings is available in Local Settings Files - Options. SOAtest preferences set from the GUI are applied by default. These can be overridden—on an individual basis—by preference values contained in the configuration file used with a given run. This enables you to have a basic set of preferences configured for all CLI runs, and then vary individual settings as necessary by providing an additional configuration file for a specific run with a given Test Configuration. This can be useful, for examplefor example, to include different information in reports for different runs, or to change options for email distribution of reports, including report names, email headings, etcand so on.
Step 1: Configure Preferences
...
Create a settings file as described in Local Settings Files - Options.
Step 4: Activate CLI in the Currently
...
Running Build System (
...
for example, batch script)
For example, a sample command line to be added might be:
...