Show TOC

Procedure documentationCreating Damaged Test Case Support Messages


During testing, testers can detect damaged test cases, which do not work as expected.

You can create a support message for damaged test cases in the following cases:

  • You think a test case failed because of a system malfunction.

  • You think a test case failed because the test case is faulty, but you cannot detect the error.

Before you create a support message to report a damaged test case which is to be checked or repaired by the test engineer, you first check, for example, the following possible causes:

  • System malfunction

  • Missing authorization

  • Error in the test script

If the test case failed because of a program malfunction, you create a support ticket.


  • In the Tester Worklist of the Test Management work center, you have performed a test case which failed. The status Errors. Retest Required is assigned to that test case. For more information, see Assign status.

  • The administrator has created a system user for you and assigned a business partner to the user.

  • The administrator has created a business partner for the test engineer.


  1. Choose the Tester Worklist.

  2. Select the test package which contains errors.

  3. Choose Report Damaged Test Case.

    A screen appears. The screen gives an overview of the test cases of the respective test package.

  4. Select the test cases for which a support message is to be created.

    You do this if you think a test case failed because the test case is damaged, and you want the test case to be repaired by the test engineer. You can select a test case if the status of the test case is red and if no previous unresolved error has been reported already.

  5. Choose Start of the navigation path Create Message Next navigation step Automatically End of the navigation path.

    A support message is created. This support message will appear in the Damaged Test Case Worklist.

    If the support message cannot be created automatically, an error message will be displayed. Choose Start of the navigation path Create Message Next navigation step Manually End of the navigation path.

  6. Set the status for automated test cases to Error. Retest required. For manual test cases, we suggest that you set the status to Ok, with limitations or to Ok, if the error only applies to the test description and if the tested application worked as expected. If the description is not good enough to perform a correct test, assign the status Error or In progress.


The test engineer checks or repairs the test case and sets the status of the support message to Completed.

In case of a broken automatic test, the test engineer needs to repair the test script. For manual tests, he needs to review the document describing the test procedure. If the problem is caused by a functional issue with the application (not with the test), the application developer needs to be involved. Afterwards, the tester can repeat the test.