This topic provides a general guide on how to add projects, .pva (Parasoft Virtual Asset) files and Responder suites using Virtualize’s various wizards. This section includes:
The process for creating action suites and .pvn files for provisioning actions is very similar to the process for creating Responder suites and .pvas. For details on functionality specific to action suites, see Defining Provisioning Actions.
For a description of the various wizards available for adding projects, .pva files, and Responder suites, see Overview of Wizards in Virtualize.
A project (an entity created by Eclipse) can contain any number of Virtualize-specific .pva files. Projects can also contain source files you want to use with Virtualize, and any other resources that make sense for your environment.
Each .pva (virtual asset) file can include any number of Responder suites.
A Responder suite is a collection of virtual assets and related items (such as data source files).
Any .pvas and responder suites that are created in the VirtualAssets project will be automatically deployed to the local server.
You can create an empty project as follows:
To add a new .pva file to an existing project:
You can then complete the wizard to specify how you want to create virtual assets. For help selecting and completing the available wizards, see Overview of Wizards in Virtualize.
If you have an existing SOAtest .tst files with emulated services, you can convert it to a .pva file by changing the extension from .tst to .pva, then importing it into Virtualize (e.g., you could create a project using the Virtualize> Migration for Existing Users> Create Project From Existing Responder Suites wizard).
To create a new Responder suite:
For help selecting and completing the available wizards, see Overview of Wizards in Virtualize.
To create a new Virtualize 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 Virtualize 's Extensibility API. Any Java classes added to your project can be accessed by Extension tools in your Virtualize Responder suite.
To use an existing Java project from your workspace, you must first add that Java project to Virtualize '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 Virtualize will attempt to reload classes from your Eclipse project after being modified or recompiled. The Reload button can also be used to force Virtualize to reload classes from the classpath entries.