Show TOC

Procedure documentationExecuting Manual Test Cases

 

When executing manual test cases, you can do the following

  • Assign a status so that the test cases can be further processed.

  • Measure the current effort

  • Enter information which allows for reproducing errors, for example, the steps which led to a dump.

Prerequisites

  • The test engineer has assigned a test package to your user.

  • You have called the Test Management work center.

Procedure

  1. In the Tester Worklist, select a test package.

    The test cases, which are assigned to the test package, are displayed.

  2. In the Assigned Test Cases area, select a manual test case. To do so, select a test case to which in the Type column the Test Document icon is assigned. The tooltip shows you whether it is a test case of type Test Configuration or of type Test Document (manual test case).

  3. Choose the Run pushbutton.

    You go to the Manual Test Case screen. The test case is displayed. To provide more space to display the test case, you can hide the right side of the screen.

  4. In the Test Status field, set the status to Being Processed.

  5. To start the measurement of the effort for the execution of the current test case, choose the Start Execution pushbutton.

    Note Note

    The Start Execution pushbutton. is only active, if a test object is assigned to the test case.

    End of the note.
  6. Execute the test case.

  7. After having executed the test case, choose the Stop Execution pushbutton.

    The test effort is displayed and can be changed manually.

    For more information about reporting the test effort and the test plan status progress, see BI Reporting.

  8. Select the appropriate test status:

    Situation

    Status

    Action

    You have not yet performed a test.

    Untested

    -

    A test has been temporarily interrupted.

    Being Processed

    -

    Test performed successfully.

    OK

    -

    Errors found which slightly impair the use of the software (for example, ergonomic weaknesses, poor user guidance).

    OK with Reservations

    To enter an explanation, create a test note or create a message.

    Program errors or serious faults found.

    Errors: Retest Required

    To enter an explanation, create a test note or create a message.

    At retest, the original error has been removed and no new errors have arisen.

    Retest OK

    -

    Note Note

    Which statuses are possible depends on how your system is configured. If you are unsure about the meaning of a status, ask the person responsible for your system. For more information, see Central Test Workbench Settings.

    End of the note.
  9. Select the Test Ended field, if the test execution was successful and if the field is not selected automatically.

    Note Note

    Whether or not the Test Ended field is selected automatically depends on how your system is configured. For more information, see Central Test Workbench Settings.

    End of the note.
  10. Enter the test effort.

  11. In the Restrictions area, specify which kind of object was the subject of the test case. If the execution of the test was restricted, for example, to checking the functions only, but not the documentation, select the Functions field.

  12. To add information, you can do the following:

    • To add a test note with text information, on the Test Note tab page, choose the New pushbutton.

    • To add a message, for example to describe an error, on the Messages tab on the right side of the screen, choose the Create pushbutton.

    • To add a protocol of the test execution or a document containing a screenshot, on the Results tab on the right side of the screen, choose the Create pushbutton.

  13. Save your entries.

  14. Exit the function.

Result

You have documented the result of your test case. The test organizer has an overview of the status of all test cases in your test package.