Test Plan Management

With this function you can:

• Create
• Change, copy or delete test plans

Integration

You organize tests after you have created a project structure in Create Business Blueprint. You have Configured, and want to test these configurations by process. When you create a test plan for a project, the default test plan structure is based on the structure of the Business Blueprint that you have previously created for your project.

Features

With test plan management, you can:

• Create, change, or copy test plans
• Delete an individual test plan, or delete several test plans at the same time, after a test campaign, to clean up the system
• Transport test plans
• Divide test plans into test packages and assign them to testers
• Monitor test progress with the status info system, and export test results

With test plan management, you can create test plans that are based on:

• The project structure that you created in the Business Blueprint
• One or more test catalogs

The test plans are the set of all test cases which you need for a specific test phase, and can comprise the following objects:

• Manual test cases
• External applications, for example, third-party test tools or an MS Word document
• CATTs
• eCATT test configurations
• Function module tests

In the Utilities menu you can also:

• See the worklists of individual testers
• Upload and download notes
• Display project data for a project to which a test plan is assigned
• Check the system landscape of a project to which a test plan is assigned

You can create and print a test report which contains, for example, the test case descriptions, messages and status, in the Goto menu.

You can sort the test cases in test sequences within a test package or assign test cases to different testers. For better test execution control, you can set up a workflow that is based on a release status schema.

Source: www.help.sap.com

Test Preparation

To be able to use the Test Management functions of the work center effectively, you must make certain prparations in your system: The business processes which are affected by the changes are analyzed according to the TBOMs and their filter and criticality settings.

The following preparation is required:

• Assign the scenarios, business processes or process steps to executable entities.
• Create a list of objects (Technical Bill of Materials, TBOM) for every executable entity.
• Define test cases for the scenarios and processes.

This process guides you through the required steps.

Prerequisites

You created a project or solution structure while creating the business blueprint.

The system landscape of the project or solution is configured.

You have at least ST-PI 2008_1 SP03 in the managed system in which your processes run.

You are authorized to change TBOMs. 

Process

1. Complete executable entities and test cases for the relevant nodes of your business processes
2. Check the status of your business processes.
3. Create TBOMs for all executable entities.
   Alternatively, send TBOM recording tasks to the business process expert responsible, who creates the TBOMs.
4. Configure the TBOM filter.
5. Configure the TBOM criticality.

The following additional activities may be required in the preparation phase:

• Delete TBOM

• Lock or unlock TBOM

• Check whether a TBOM is up-to-date
• Update TBOM classification types
• Recalibrate TBOM
• Delete test TBOMS from the database by mass TBOM deletion
• Delete TBOMs not assigned to business processes, from the database, regularly

Result

Your business processes contain test cases and executable entities with current TBOMs.

You have configured the TBOM filter and criticality.

You can now run the Business Process Change Analyzer, and generate the test plans required, from the results.

Source: www.help.sap.com

Component-Based Test Automation (CBTA)

Component-Based Test Automation allows you to create automatic tests.

An automatic test is made up of components. There are two kinds of components: default and screen components:

• Default components perform basic actions like clicking on a button or selecting a tab. They are delivered in the SAP Solution Manager system.
• Screen components are generated for either SAP GUI transaction screens or SAP CRM Web UI application views. In both cases, they are created with a parameter for each field on the screen. The value of a parameter is given to the corresponding field during execution.
  There is only one screen component per SAP GUI transaction screen or SAP CRM Web UI application view, so a screen component can be shared among several tests.

You maintain the screen components and tests in the Test Composition Environment. They are both eCATT test scripts, so CBTA assets are compatible with the eCATT framework.

Note

You can only test business processes of SAP ABAP ERP and CRM products (SAP GUI and SAP CRM Web UI only).

Integration

• SAP Solution Manager: Store data required to create, optimize, and maintain tests and components.
• SAP system under test (SUT): Support both SAP GUI, and SAP CRM Web UI technologies

Features

• You can record tests.
• You maintain tests via shared components.
• You can maintain changed screen components.
  
  
  Source:  https://help.sap.com/