user manual

98 SilkPerformer Java Explorer User Guide
7 E
XPORTING PROJECTS
SilkPerformer Java Projects
2 Specify a name and destination for the exported file, as indicated on the
Export Project dialog. By default, projects are saved to Java Explorer’s
project directory (<SilkPerformer installpath>\Working\Projects\)
Note Ensure that you set the correct proxy in your SilkPerformer
project settings if you are calling a Web Service on the Internet.
SilkPerformer Java Projects
Using Java
Framework
As discussed in the Introduction of this guide, SilkPerformer’s Java Framework
enables developers and QA personnel to coordinate their development and
testing efforts while allowing them to work entirely within their specialized
environments: developers work exclusively within Java programming
environments while QA staff work exclusively in SilkPerformer.
SilkPerformer’s Java Framework thereby encourages efficiency and tighter
integration between QA and development. See “Testing Java Components” for
additional details.
Exporting to SilkPerformer from Java Explorer is valuable for QA personnel
who are proficient with SilkPerformer in facilitating analysis of Java
components and wish to create SilkPerformer projects, test case specifications,
and scripts from which load tests can be run.
When a project is exported directly to SilkPerformer as a Java project, a default
SilkPerformer project (.ltp) file is created. Using SilkPerformer, a project can
thereafter be load tested with multiple virtual users. SilkPerformer also enables
the gathering and analysis of performance data for each method call.
SilkPerformer Java
projects
SilkPerformer Java projects are created with the Java class and a BDF file that
contains the calls to the Java class.