| BOL Test Tool - Protected Layer (tlbct2210m000)Use this session to test a protected BOL
method. To test the protected method: - In the current session, you must specify a Business Object and a method. If you click Launch, the session generates a test script for
the specified method.
- When the script is generated, a temporary session appears,
which enables you to specify the input arguments with which the method must be
tested. All possible arguments are listed in this session. Select the check
boxes of the arguments you want to use. Mandatory arguments are marked with an
asterisk. Click Continue to confirm your input.
- Another temporary session is displayed that enables you to
specify the values of the arguments you specified in the previous step. Click Test to run the test script.
- A third temporary session appears that displays the output
values, or the return value and error message.
Company handling The test tool handles various data sets, which is visible in
the company numbers displayed in the sessions. See Company handling. Developers mode You can start the session in developers mode to control the
test script that is run. If you work in developers mode, the session provides these
extra options: - You can monitor the program flow if you clear the Hide Technical Details check box. This check box is only available if you
work in developers mode.
- To manually edit, compile, and run the generated test
script, you can use the buttons that are available in developers mode. To
compile the script in debug mode, you must select the Compile Testscript in Debug Mode check box.
- The field that displays the test script is changed from a
display field to an input field, and you can specify another script than the
one that was selected by the session.
To start the session in developers mode, add the following
line to the Command field of your BW Configuration file: -set TMODE=1 . Note that you cannot start the session in developers mode if you use
the Web UI interface. Note The Launch command that is available in
the initial screen generates a test script. To perform a series of tests on the
same business object, for best results, click Continue in the
third temporary session, which enables you to reuse the generated script. If
you return to the first screen by canceling one of the subsequent screens and
then click Launch again, the test script is generated
anew. You can only specify a business object that occurs in your
current package combination. Transactions are supported. When the return value of the
method is not zero, the transaction is aborted. If the return value is zero,
the transaction is committed. If a retry is required, a message is
displayed. Package VRC The package code of the current package VRC. With the Package VRC, the system knows that
you have permission for this package VRC and can ask the application dictionary
information/ BOR information required to perform the test. To switch to another package VRC, click Change Curr PVRC. Package VRC The version of the current package VRC. To switch to another package VRC, click Change Curr PVRC. Package VRC The release of the current package VRC. To switch to another package VRC, click Change Curr PVRC. Package VRC The customer code of the current package VRC. To switch to another package VRC, click Change Curr PVRC. Package VRC The description of the current package VRC. To switch to another package VRC, click Change Curr PVRC. Module The description of the module. Component The name of the Business Object component to
be tested. You can use components to model recurring elements in
Business Objects, for example, a recurring order line. As a result, other parts
of the same Business Object, for example, the order header, are also modeled as
a component. Leave this field blank if the Business Object has no
components. BOL Method The protected Business Object method to be
tested, for example, Create. Note The method name is case sensitive. Script The package of the software component that is used to
perform the test. Extra information about the script type and the VRC is shown in case data is present in the function tree
database. This field is read-only when the session runs in normal
mode. In Developers mode, however, the field becomes an input field. Therefore, you can now
change the script name. In this way, you force the system to run another
object. This can be useful if you made a special library for test
purposes. Script The module of the software component that is used to perform the test. Extra information
about the script type and the VRC is shown in case data is present in the function tree
database. This field is read-only when the session runs in normal
mode. In Developers mode however, the field becomes an input field. Therefore, you can now
change the script name. In this way, you force the system to run another
object. This can be useful if you have made a special library for test
purposes. Script The identification code of the software component that is used
to perform the test. Extra information about the script type and the VRC appears if data is present in the function tree
database. This field is read-only when the session runs in normal
mode. In Developers mode, however, the field becomes an input field. Therefore, you can now
change the script name. In this way, you force the system to run another
object. This can be useful if you have made a special library for test
purposes. Script Additional information about the software component that is
used to perform the test. This information is stored in the function tree
database. Hide Technical Details Clear this check box to monitor the program flow. This can be
useful if you want to know about the (internal) actions the tool performs, or
if you want to know more about the problem that was reported. The program flow
appears in a terminal emulator. By default, this check box is selected, and LN enables
you to avoid the technical aspects. This option is only available in Developers mode. Compile Testscript in Debug Mode If this check box is selected, and you compile a
test script using the Compile button, the compilation is carried out in
debug mode. | |