This topic provides a general guide on how to add projects, .tst files and test suites using SOAtest’s various test creation wizards.
For a description of the various wizards available for adding projects, .tst files, and test suites, see Wizards for Creating Projects, .tst Files, and Tests.
A project (an entity created by Eclipse) can contain any number of SOAtest-specific .tst files. They can also contain source files you want to analyze with SOAtest, and any other resources that make sense for your environment.
Each .tst file can include any number of test suites/scenarios, tools, and inputs. The organization and structure is up to you. To keep file size down and to improve maintainability, we recommend using one .tst file for each distinct testing requirement.
For best practices related to projects, test files, and workspaces, see Workspaces, Projects, and Test Files.
A test suite is any collection of tests that are individually runnable, and has the following setting in the test suite configuration panel:
A scenario is any collection of tests that are not individually runnable because they have dependencies. One example of a scenario is when a series of API tests extracts a value from one test’s response and uses it as part of subsequent test message. Another example is a sequence of web scenarios recorded from a browser.
You can create an empty project as follows:
We recommend that you create a separate test (.tst file) for each distinct testing requirement. To add a new Test Suite (.tst) file to an existing project.
You can then complete the wizard to specify what type of tests you want to create and how you want them created. For help selecting and completing the available test creation wizards, see Wizards for Creating Projects, .tst Files, and Tests.
To create a new test suite:
For help selecting and completing the available test creation wizards, see Wizards for Creating Projects, .tst Files, and Tests.
SOAtest allows you to create a new Eclipse Java project that has access to SOAtest's Extensibility API, then configure SOAtest scripts and Extension tools to invoke classes from the new Java project.
To create a new SOAtest Java project:
Your new Java project will be shown in the Package Explorer view in the Eclipse Java development perspective. The project's build path will automatically have the jar files needed in order to use SOAtest's Extensibility API. Any Java classes added to your project can be accessed by Extension tools in your SOAtest test suite. For an example of how to do this, see "Java Example" in Extensibility and Scripting Basics.
To use an existing Java project from your workspace, you must first add that Java project to SOAtest's classpath as follows:
The selected Java Project's build output folder and build path entries will be added to the classpath table.
If the Automatically reload classes option is enabled, then SOAtest will attempt to reload classes from your Eclipse project after being modified or recompiled. The Reload button can also be used to force SOAtest to reload classes from the classpath entries.