Automated PiL-test (incl. releasing of libraries)
Neuron Power Engineer provides a tool for the automated PiL-tests for POUs specified within a library incl. a tool for releasing a library in Neuron Power Engineer.
Good to know |
---|
The tool is intended for usage by an experienced user of Neuron Power Engineer. A condition for the successful usage of the tool is the knowledge of the action to be executed as it would be executed in the graphical user interface of Neuron Power Engineer. The output of the tool is in English only. |
In this article: |
---|
Preparation
-
Make sure that a variant of Neuron Power Engineer is installed in which the test framework is provided. Have the following information prepared:
-
The path to the Neuron Power Engineer installation directory
-
The path to a directory that will be used as the workspace
In case the directory does not exist, the tool creates it. -
The path to the project that should be imported (before the PiL-tests are executed)
-
The path to the log configuration file (see below for more information)
A sample configuration file is included in the installation of Neuron Power Engineer.
-
-
If the JAVA JDK has not already been installed on your computer, install and unpack the JAVA JDK. In case of an installation, also enhance the environment variable
PATH
of the operating system by the folder to which the JAVA JDK has been installed/unpacked. In case of doubts, ask your administrator to support you in doing so. -
Open a command line: e.g.
cmd.exe
under Windows and navigate to the Neuron Power Engineer installation directory.
Invocation
|
Description of parameters:
Parameter |
Description |
Example |
---|---|---|
|
absolute path to a workspace to which the project should be imported
|
|
|
version number of the required Java version |
|
|
path to the log configuration file |
|
|
absolute path to the project that should be imported |
|
|
name of the project containing the test suites |
|
|
name of the library configuration (with |
|
|
name of the generated library (incl. the version number) |
|
|
name of the device to which the library should be loaded |
|
|
Example for invocation |
---|
|
Log configuration file
This file is needed to configure the log4j logging mechanism. The file specifies how log events are output.
Sample log configuration file |
---|
|