In the Test Repository
view of the Test Management
work center, you create and edit test configurations and test scripts. A test script is part of each test configuration and describes the technical components that are required to execute the business process step. For more information, see Components of Automated Test Cases.
You assign a test configuration and test script to a solution, which is linked to a system data container. You can assign a test data container to a test configuration.
You create a test configuration to create an automated test case. Since there cannot be a test configuration without a test script, you have to create the related test script in parallel. Later, you can edit an assigned test script or replace it with a different test script.
You can automatically create the test script by recording a sequence of steps in a transaction with the CBTA tool, for example. You can also us eCATT or third-party test scripts.
See the prerequisites under Test Repository.
Caution
Before you edit an existing test configuration, check in which test plans, test packages, or test scripts it is used. To do so, select the test configuration and choose Where-Used.
.
We recommend that you create a test configuration from the Solution Documentation
view in the Test Management
work center, for the following reasons:
In the Solution Documentation
view, you can select a specific process step in the right solution and branch, first, and directly create the test case with the test configuration to it. So the correct assignment exists from the beginning.
You can select the executable object for the process step, in the solution documentation, or directly get the executable that is assigned to it.
You can assign several test configurations to a process step and organize your tests accordingly.
You can use the Business Process Change Analyzer for the solution
After creation, you can also edit test configurations in the Test Repository
view.
Create a test configuration as follows:
In the Solution Documentation
view in the Test Management
work center, select a solution.
Then select the relevant branch of the solution and choose Open
in the Solution Documentation
column.
In the Column Browser
(selectable at the top of the new window), drill down to the business process step for which you want to create a test.
In the table of elements, you see the executables and test cases that have been assigned already.
To assign a new executable to the business process step, right-click in this table and choose
. Such an executable can be a transaction, program, SAP GUI transaction, a CRM application (using the role and logical link parameters), a Web Dynpro ABAP application, or a URL.As a consequence, the executable is available to be assigned to a test case, in the next steps.
To create and assign a new test case to the business process step, right-click in the table with elements and choose
:Fill the mandatory fields and save.
The editor for the test configuration opens. Complete the settings on the Attributes
tab.
For more information, see Maintaining Attributes.
If you chose the CBTA (component-based test configuration) as test tool, select the executable to be tested. Then you can choose Launch CBTA
to directly start the creation of the test script by running the selected executable in CBTA.
When the test configuration is complete, choose Save
and Close
.
Back in the editor for the business processes, select the newly created test case.
On the right-hand side, you can define further characteristics:
Test Classification
: You can define the test case as regression test or user acceptance test, for example. This is helpful when you create test plans, later, for these specific purposes.
Test Data Variant
: You can select it for automatic test cases. The test data contains a set of values to be used for the automatic test. The variant defines which specific sets are to be used,
Target Logical Component Group
: When you create a test configuration, you have to define the logical component group. Together with the branch and system role, this will allows to execute the test in the correct target system. The logical component group specified here reflects the one that is selected for the test configuration.
Save and close the window.
You can edit test configurations in the Test Repository
view or in the Solution Documentation
.
We recommend that you create test configurations including the test script in the Solution Documentation
view. But to create a very simple test, quickly, you can create the bare test script directly in the Test Repository
view:
in Test Repository
view, choose one of the following sub-views:
Test Scripts
Test Configurations
When you create or edit a test configuration, the test script is automatically included.
Choose Create
.
Select a solution.
You can define the system role directly in the test repository. Together with the solution and branch, it allows to automatically derive the physical system, to which the logical component group points. Changing the system role changes the system on which the tests are recorded and executed. This is useful when you define a set of landscapes which contain a set of systems like development, test, pre-production, and production systems.
If you create a test configuration: In the Test Configuration
field, enter the name of the test configuration.
Note
If you want a test configuration to remain local (not be transported to other systems) enter a technical name starting with Z (depending on the name space specified in your system configuration). For example, you store all your test cases on a single SAP Solution Manager system. The name space is automatically assigned after recording a screen component. For more information about configuring the name space, see SAP Note 1763697.
This does not apply to third-party test tools or CBTA.
In the Test Tool
field, select the test tool.
Enter the name of the test script to be created, or assign an existing test script, if you create a test configuration.
Note
If you do not assign an existing test script, a test script is created automatically when you create a test configuration. The name of the test script is the test configuration name.
Optional: Change the default version number.
In the Title
field, enter a name.
In the Package
field, select a transport package or Local Object
.
Confirm.