user manual

96 SilkPerformer Java Explorer User Guide
6 S
YSTEM & PROJECT SETTINGS
Project Settings
Note The Runtime classpath is stored in both JExlorer.conf and the
project file (.jep). Upon loading a project, if the classpath entries in
the project file do not match the classpath settings in the system
settings (JExplorer.conf), the system settings will override the stored
project settings.
The Restart Runtime Process checkbox fulfills two purposes. First, it signals, if
recent classpath changes made by the user require the restart of the runtime.
Secondly, it allows the user to explicitly force a restart of the runtime process.
By default, only the three classpath groups (Static, JDK, and Dynamic) that can
be customized by the user are visible. With the Show Full Classpath checkbox
enabled, all internally used classpath entries (Java Explorer archives, Web
Service plug-ins, etc) are also visible. This is helpful for expert users and certain
internal purposes (e.g., to see if an archive of a customer’s test environment
conflicts with a Web Service plug-in.
Scripting Settings
The Scripting tab defines the file names, which are used when exporting the
Java Explorer project (see “Exporting Projects” for more information about
exporting projects).
TestClass for
SilkPerformer
Defines the file name of the exported Java test class for SilkPerformer Java
Framework.
TestClass for JUnit Defines the file name of the exported JUnit test class. This test class extends
junit.framework.TestCase.
TestClass for
Standalone
Defines the file name of the exported standalone test class, which can be
executed from the command line, or which can be integrated into other test
frameworks.
TestScript for
SilkPerformer
Defines the name of the BDL script file which will be generated for
SilkPerformer Java Framework.