SOAtest uses the following views in the default SOAtest perspective:
For details on other views provided by the Eclipse workbench (such as the Tasks and Problems view), see the Workbench User Guide, which can be accessed from Help> Contents.
The Quality Tasks view provides actionable information about test results. Test failures and possible causes are listed in this view. See Reviewing Results for additional information.
The Console View shows summary information about any executed test, including how many tests were executed, failed, and skipped.
You can also configure the Console to show variables as described in Monitoring Variable Usage.
The Data Repositories view is your main control point for adding, deleting, editing, and reviewing Parasoft Data Repositories, which allow teams to define, extend, and review large and/or hierarchical data sets for use in Parasoft messaging tools. Each repository’s hierarchy is represented graphically, and this graphical representation links to a Data Editor that simplifies extending and browsing large, complex data sets.
For details, see Working with Large Hierarchical Data Sets.
The Editor view is the largest panel in the workbench. This is where SOAtest displays tool/test configuration panels or source code—depending on what Test Case Explorer or Navigator node was selected. For instance, if you double-click a SOAP Client tool node in the Test Case Explorer, a SOAP Client tool configuration panel opens in an Editor.
The Queue Browser allows you to see the contents of queues deployed on Websphere MQ, Websphere Application Server, Tibco EMS, Sonic MQ, ActiveMQ, and any other JMS provider. This is helpful for debugging purposes, especially for the initial configuration of a JMS transaction. For details, see Browsing Queues.
The SOAtest Server view allows you to start and stop the SOAtest server, which works with the Call Back tool and Asynchronous testing—as well as Message Stub tools integrated into end-to-end test scenarios.
The Test Case Explorer presents your projects and the included test suites and test assets (data sources, environments, etc.).
The Workflow Palette view shows the right-click actions and wizards that are applicable in the current context.
You can create, configure, and manage Smart Test Template (.stt) files in the Smart Test Template view. Smart Test Templates are used to automatically configure tests generated using the SOAtest Smart API Test Generator. See Training the Smart API Test Generator for additional information.