The system editor is used to create and modify system diagrams: graphical representations of how all dependent components are connected to the application under test (AUT). These system definitions serve as templates for the environments that are created by developers, QA, and performance test engineers—who can then define the subset of components that are necessary for their testing/development tasks.
To define a system:
...
- Click on the Workspace tab
...
- and click Add System in the toolbar
...
- .
...
- Enable the Create an empty system
...
- option when prompted and click Create.
- (Optional) Click the edit icon by the name field to rename the system and add a description.
- Click the save or cancel icon to apply changes.
- (Optional) Click the edit icon for other metadata fields to add tags and variables.
- Drag components from the Component Types (palette) tray to the main editor area. If needed, you can add custom components as described in Adding Components to the Palette.
Info title
...
Only one SOAtest Test Executor can be added per system
...
Once an executer is added, it will be removed from the Component Types (palette) tray. It does not need to be connected to other components. For more details, see Integrating Testing with Environment Provisioning.
Specify the connections between components by dragging the points surrounding each component.
Save the diagram by clicking Save (at the top left of the page).
Info title Tip—Creating a new version of an existing system If you want to create a system that is similar to an existing one, you can create and modify a new version of that existing system. For details, see Creating System Sets and Environment Sets.
...
Editing an
...
Existing System
If you later want to edit this system or another existing system, select it from the system tree, then click the Edit Diagram toolbar button to reach "Edit mode."
...