Show TOC

Procedure documentationChecking the TBOM Coverage and Status

 

Determine whether the prerequisites for using the Business Process Change Analyzer are satisfied, regularly. Select parts of the solution and ensure that, for example:

  • TBOMs and test cases are assigned to all business processes

  • Existing TBOMs are up to date

Prerequisites

  • You have created a solution documentation. You have assigned executable entities and test cases to the relevant nodes, and created TBOMs.

  • To identify obsolete TBOMs, you have scheduled an obsolescence check.

    For more information, see Scheduling Obsolescence Checks.

Procedure

  1. In the Test Management work center, choose Solution Documentation.

  2. Select the solution and the branch.

  3. Choose TBOMs and Test Cases.

    In the solution documenation, the status of the currently edited node, is displayed.

  4. In the solution hierarchy displayed at the top of the screen, choose the hierarchy level, for example Start of the navigation path Solution Next navigation step Libraries Next navigation step Executable Library End of the navigation path.

  5. Choose an SAP-delivered or custom filter layout to analyze your solution.

    Use the SAP-delivered filters or create custom filters to

    • display objects, for example business critical transactions, to check their status

    • display business processes to which test cases or TBOMs are not yet assigned (Test Case Type attribute value Non-Existent, Executable TBOM Type = Missing)

    • check which TBOMs were generated with manual test cases and can be replaced with TBOMs based on automated test cases

    • identify executables types (executables using Web applications, for example), to satisfy the prerequisites for creating TBOMs

    • identify nodes to which currently only static or semi-dynamic TBOMs are assigned and consider creating more precise dynamic TBOMs for business critical nodes

    • identify obsolete TBOMs (TBOM status = Obsolete)

    • for transactions which trigger background jobs, with the Batch Job Status attribute identify whether background jobs were scheduled while the TBOM was being recorded

    • identify TBOMs created by certain persons or at specific times (Created at/by, Updated at/by)

    • ensure that TBOMs are created in specific systems (System/Client)

    • identify TBOMs whose recording has been delegated to business process experts (Work Item Existence)

  6. In the Path column, choose the link, to open the structure element.

  7. On the Elements of <Node> tab page, in the context menu, you have the following options:

    • A test case is not yet assigned to a structure element that is to be tested. Assign or create missing test cases. Choose, for example Start of the navigation path New Next navigation step Test Cases Next navigation step Test Configuration (Create) End of the navigation path, depending on, for example, the test case type or whether you want to assign or create a test case.

    • A TBOM is not yet created for an executable. Do one of the following:

      • Mass-generate semi-dynamic or static TBOMs automatically.

      • Create a dynamic TBOM manually.

      • Assign the corresponding executable for automatic TBOM creation with automated test cases.

      For more information, see Choosing the TBOMs Types.

    • An obsolete TBOM is assigned to a structure element: If you use obsolete TBOMs, the change analysis may be inaccurate. Rerecord the obsolete TBOMs.

    • To check whether a TBOM enhancement has already been created for objects used in transactions which trigger batch jobs, check the Batch Job Status attribute. For more information, see Checking the Status of Batch TBOMs.

Note Note

You may want a business expert to create or update a TBOM. To delegate TBOM recording, create TBOM recording work items for those experts. For more information, see Delegating TBOM Recording to Business Experts.

End of the note.

Result

You can analyze your business processes and create test plans from the analysis results. For more information, see Analyzing Business Processes Affected by Changes.