This topic explains the basic procedure for using extending Parasoft’s Extension Framework to extend Parasoft’s built-in transports and message formats.
|Table of Contents|
Adding an Extension
Parasoft’s Extension Framework is standardized across all extension types. Once you understand the basic process, you can apply it Use the following process to add support for all of the various message formats and transports your team is working with. All extension work is done using Java.
install dir]/plugins/com.parasoft.xtest.libs.web_[version]/root/com.parasoft.api.jarto your Java project classpath. You can also create a new project by going toFile> New> SOAtest>Custom Development> SOAtest Java Project orFile> New>Virtualize> Custom Development> Virtualize Java Project; this will create a new Java project that already has that the .jar file added to the its classpath.:
- Choose File> New> Project
Choose SOAtest or Virtualize> Custom Development> SOAtest or VirtualizeJava Project
Info icon false title Building with Maven?
If you’re building your Java project with Apache Maven, you can add the following to your project's pom.xml:
<project> ... <dependencies> <dependency> <groupId>com.parasoft.soavirt</groupId> <artifactId>com.parasoft.api</artifactId> <version>9.9.0</version> <!-- should match product version --> <scope>provided</scope> </dependency> </dependencies> ... <repositories> <repository> <id>ParasoftMavenPublic</id> <name>Parasoft Public Repository</name> <url>http://build.parasoft.com/maven/</url> </repository> </repositories> ... </project>
- Implement the appropriate interfaces. See the following sections for details on implementing the appropriate interfaces:
parasoft-extension.xmlfile in the default package of your Java project and configure it as appropriate for the item (or items) you’re adding.
Custom extensions can depend on Java libraries other than com.parasoft.api.jar. For details in SOAtest, see Configuring External Dependencies.For details in Virtualize, see Configuring External Dependencies 1.
You can externalize any string displayed in the GUI to support different languages. For details in SOAtest, see Localizing GUI Text.For details in Virtualize, see Localizing GUI Text 1.
If you are using an existing extension and later create a new version of that extension that has a different set of GUI options, you can use a version updater to update your saved .tst (SOAtest) or .pva, .pvn (Virtualize) files to adapt them to the new set of options. For details on updating SOAtest artifacts, see Updating GUI Fields for a New Version 1.For details on updating Virtualize artifacts, see Updating GUI Fields for a New Version..