As a test engineer, you can do the following:
Execute a test case which is to be repaired
Display the execution log of a test script
Identify the causes of damages
Edit and repair test case scripts
Change the status of repaired test cases to inform the reporter
In the Tester Worklist
, a reporter (tester or test coordinator) has created at least one damaged test case support message. For more information, see Creating Damaged
Test Case Support Messages.
As a test engineer, you have the role SAP_STWB_WITC_EXE
.
You have called the Test Management
work center.
Choose Damaged Test Case Worklist
.
To find a damaged test case support message, choose the My Work Items
link and look for support messages with the status New
, Open
or In Process
.
To display information about the damaged test case support message, choose Repair
.
On the General Data
tab page, information is displayed which specifies the damaged test case and comments history.
On the Action Log
tab page, information about who originally created the support message and who last changed it, is displayed.
To check from which context in an SAP Solution Manager project or a solution the test case is executed, select the support message and choose
.You can, for example, check, whether there are predefined target components, with which the test case has to be executed, or whether the system data container is set up correctly for the project and used correctly in the test execution.
To identify the cause of a failed execution of a test case, select the support message and choose Repair
.
A screen appears.
To execute a test case, choose Run Test Configuration
.
To display the log of the last execution of the test case, in the General Data
tab page, in the Execution Data
area, choose the Test Tool Log
link.
To check whether changes in the respective system may have caused the failure of an automated test case, you can start the Business Process Change Analyzer:
Choose the Change Analysis
tab page.
The data of the last successful run is displayed.
The change interval start date is the date of the last successful execution of the test case. The change interval end date is the date of the failed execution of the test case and for which damaged test case support message was created.
Choose Run
.
The BPCA result is created.
To display the result, choose the respective result ID.
You go to the BPCA Result
screen. The system changes from the date of the last successful execution to the date, when the execution of the test case failed, are displayed.
For more information, see Business Process Change Analyzer.
If the execution failed because the test cases is damaged, assign the support message to all occurrences of the test case in all test plans or test packages. Choose Distribute
.
You distribute support messages to all test plans or test packages if the test case is damaged and has to be repaired. The test coordinator can remove the test package or test plan from the schedule.
The support message is assigned to all test cases with the status In Process
or In Error
. It is not assigned to test cases with the status OK
or Not Yet Tested
.
When the test engineer has completed the support message, the test coordinator is notified. The test package or test plan containing the test case can be scheduled again.
To edit a test script, choose the Edit Test Script
pushbutton. For more information, see Test Script Editor.
If you find out that the test case is not damaged but that an application error was the cause of the test case failure, to create a support message, choose the Report Application Error
pushbutton.
The support message automatically contains all data of the original damaged test case support message.
After having repaired or checked the test case, on the General Data
tab page, do the following:
Set the status of the support message to Completed
.
Optional: Add a comment and, for example, to request additional information of the reporter who created the damaged test case support message, do the following,
Choose the General Data
tab page.
In the New Comment
field, enter your comment.
Optional: Select a category.
Note
To assign a category, stest case error categories must be maintained. For more information, see Defining Test Case Error Categories.
Save your entries.