A project (an entity created by Eclipse) can contain any number of SOAtest-specific .tst files. They can also contain source files that you want to analyze with SOAtest, and any other resources that make sense for your environment.
Projects can be used to organize your .tst files within the workspace. You can share them over a source control repository, or via the Import / Export feature.
Each .tst file within a project 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.
In this section:
Multiple .tst files can be grouped into a single project.
First, we will create a new project based on existing test suites.
Examplesin the Project Name field.
The Examples project will be added to the Test Case Explorer. It will contain multiple test (.tst) files.
You can also create new projects by selecting different commands from the new project wizard. To see all available New Project options, choose File> New> Other and look under the SOAtest folder.
By default, .tst files are closed. Once a .tst file is open, it will be loaded into memory.
Closed .tst files have the following "closed box" icon:
Open .tst files have the following "open box" icon:
There are two ways to open a .tst file:
We recommend that you create a separate test (.tst) file for each distinct testing requirement. There are two ways to create a new test (.tst) file.
The wizard will guide you through the test creation process, then add a .tst file containing the generated tests.
As you go through the subsequent tutorial lessons, you will learn how to create different kinds of tests.