Creating and Editing Test Plans

Use

You can create test plans for a subset of your solution documentation in SAP Solution Manager. A test plan refers to a solution, a branch, and a view. To create the test plan, you can select the test cases and executables that you have assigned to the set of solution, branch, and view on any level; however, test cases and executables are usually assigned to a process step. Testers perform the test cases by calling the assigned executables and running the test cases.

Note Note

In SAP Solution Manager, test plans can only be based on a solution, a branch, and a view.

End of the note.

Prerequisites

You have defined the solution documentation and its system landscape, in SAP Solution Manager.
In the solution documentation, you have defined the executables that you want to test or automate.
In the solution documentation, you have created or assigned test cases for the processes to be tested. The test cases include the test configurations and test documents.
In the solution documentation, you have accessed the solution, branch or view that you want to test.
We recommend that you create test configurations directly from the solution documentation, it makes the assignment of executables easier.

Activities

Creating a Test Plan

In the Test Plan Management application, choose Test Plan Create .
The editor for test plan management can enter all relevant data in several tabs. You must define some mandatory information under General Data and Settings, before you can save the test plan. When you have saved the test plan, you can still change or finalize it later.
General Data tab:
- Under Header Data, enter a test plan ID. This is the identifier of your test plan, which must be unique in SAP Solution Manager. Naming conventions can help to organize test plans and user access via authorization checks.
  Enter a description and the responsible person. By default, the current user will be selected as responsible person. Each user with the required authorization can access the test plans.
- Under Process Documentation, select the solution, branch, and view to which the test plan belongs.
  
  Note
  After you have saved the test plan, you can no longer change the selection.
  
  End of the note.
  
  Select the ID of the system role in which the test plan is to be executed.
  
  Note
  When you change the system role, the display of systems under System Landscape is updated. This affects the target system where the test is to be executed.
  
  End of the note.
- Under System Landscape, the combination of the system landscape defined in the solution, and on the system role ID define which system landscape is displayed. Both are selected under Process Documentation. In the systems shown in this list, the test cases are executed.
- Under Creation / Change, the date and timestamp for creation and change are displayed, and the person who made the change.
  You can also see if there were changes in the process documentation since the last update of the test plan (changes in the structure, test documentation version, and test data variant).
Settings tab:
Define the release information and further attributes for the test plan.
- Under Release Status, you determine which actions can be performed on the test plan: If the test plan can be changed, you can, for example, select test cases, change attributes, or create test packages. If the test plan can be executed, testers can define the status and create notes and defects.
- Under Attributes, define the following:
  - The value for Executables in Test Case Selection defines how the executables are displayed when a user selects test cases in a test plan. There are three options:
    Show Test Case Only means that executables cannot be selected in a test plan if there is no test case associated with them, so a tester cannot test the executable without a test case. Executables to which test cases are assigned are displayed in the test plan hierarchy. They appear above the assigned test case. The tester can test and document the status, in the test case.
    
    Show Executable when Test Case Missing means that, if an executable but no test case is assigned, the executable can be selected for execution, and a tester can test the executable.
    
    Show Test Cases and Executables: Executable without associated test case are handled as in previous option. Executables and the associated test cases are available and can be selected for execution.
  - The Test Classification assigns the test plan into a category.
  - You can select a Test Set that was defined in customizing for SAP Solution Manager under SAP Solution Manager Capabilities Test Suite Test Suite for SAP Solution Manager Preparation Setup Define Test Set .
    It does not impact the test plan, but in reporting, for example, you can use it as filter criterion, so that you can easily run reports for all test plans that are assigned to the same test set.
  - The Document Type for Test Note/Test Results defines the document type that can be created during test execution. The values in the drop-down selection depend on the document types that are associated with the solution. The templates of the document types are managed in Solution Documentation, under Document Type Administration.
  - Under Test Plan Attachments, you can directly create or assign attachments to the test plan. The title, document type, status, and language are mandatory.
    
    You can use the following functions to assign attachments:
    Create - From Upload to upload a file from a local source.
    Create - From Template to create a new attachment using templates that the administrator has uploaded for different document types.
    
    The attachments you assign here can be reused later, when you create test packages, where you can link to an attachment or copy it.
  - Under Dates, define the planning level and the planned start and end dates. For planning on test plan level, you can also enter the planned effort.
Test Case Selection tab:
According to the selected solution, you can expand the included processes. At the lowest level, you can see all the test cases and executables that you have defined for each process.

Select the test cases that are to be included in the test plan. You can set the checkmark for a complete process, for example, and all subordinate test cases will be included. To only select individual test cases, only set the checkmark for the selected test case.

You can use a filter for an easier selection.
Test Sequences tab:
Once you saved the test plan, you can create test sequences, which break the test plan into logical, smaller units of work. The test sequence usually describes an end-to-end scenario that is tested in the given order. This is useful, for example, when a test case in a business process depends on the results of another test case. There are two options:
- A test package created from a test sequence as reference will reuse the same sequence. The sequence defines that a test case is only available for testing when the predecessor test case has been completed. In this case, the Ready for Testing indicator is flagged. You cannot change the test case selection in the test package, and changes in the sequence are automatically synchronized with the test package.
- A test package created from a sequence as template initially has the same selection of test cases, executables, and sequence, but it can be changed after creation and is independent of changes in the test sequence. T
You can create one or more test sequences in a test plan. In the test sequence, you select a sub-set of the test cases and executables from the test plan, and define their sequence:
1. Choose Test Sequence Create . The editor for test sequences opens in a new window.
2. In addition to the retrieved test plan ID, define the following:
  - On the Test Case Sequence tab, select the test cases and their order. You can assign an end-to-end document that describes the complete scenario. This document should be a test document in the test plan and can also be used as information for the test sequence.
  - On the Test Packages tab, you can create a test package from test sequence, but only if the test sequence is in display mode and if test plan status allows changes. The tab show the test packages that depend on to the test sequence (test packages with test sequence as reference).
  You can manage the sequence number (if test plan status allows changes), change test case selection and other information.
  
  On the General Data tab you can see if the test execution has already started for referenced test packages. Changes can lead to a reset of test execution data.
  Changes to test sequences are immediately applied to the related test packages. If test execution has already started, you are prompted to decide to which extent the the execution results should be adjusted:
  - Reset Option:
    
    Reset from first changes (default option): The reset will only start from the first impacted test case onwards.
    Reset all: The reset is applied to all test cases, even if changes do not affect them (for example, the removal of the third test case would not have affected the test executed on the first and second test case).
  - Reset Scope:
    
    Status: This is the minimum scope, in which the status of the test cases will be reset to not yet tested.
    Test Note: If Test Note is not selected in the scope, the test notes will remain available.
    Test Results: If Test Results is not selected in the scope, they will remain available.
    Defects: If defects are not part of the scope, they will remain available.
    
    By default, all four are part of the scope. Defects and documents will still be in the system but not be related to the test status any longer.
Test Packages tab:
Once you saved the test plan, you can create test packages, which break the test plan into logically-related, smaller units of work for individual testers.

You can create one or more test packages within a test plan. A test package is a sub-set of the test plan and regroups the test cases a tester is supposed to execute in a selected time frame.

Choose Test Package Create . The editor for test packages opens in a new window.

In the editor for test packages, you will retrieve the same information as the one that you defined for the test plan, such as test plan ID, process documentation, and settings.
In addition, you define the following data:
- Test package ID, description, responsible person
- Planned start and end dates, which must fit the times that you defined for the test plan.
- Planned effort, which you must define if Test Package was defined as planning level.
Test Case Selection tab: You see the test case hierarchy for the test plan, and you can refine the selection for the selected test package.
Tester tab: You can assign testers to the test package, lock and unlock the tester assignment, and see details of test case status for a selected tester.
Status tab: You see the current test evaluation for all test cases. The overall status for a test case in a test package depends on the evaluation rule defined in the customizing and take into account either the last execution result or the worst status.

You can also create a test package from a test sequence: Choose Start of the navigation path Test Package Next navigation step Create from Test Sequence End of the navigation path . In the popup, select the creation type as described above, under 5.

If you selected the template mode, you are in the same situation as described above, under 5,, with a predefined selection of test cases.
If you selected the reference mode, there are some differences:
The General Data tab shows the referenced test sequence (ID and description).

The Test Case Selection tab is only in display mode and represents the Test Case Sequence tab from the test sequence.

The Tester tab shows the list of test cases and allows the assignment of testers on test case level. You can replace the tester assignment, so that test execution data set by the original tester are assigned to the new tester. Assigning testers to the test package is still relevant and derived from the individual assignment.

Editing a Test Plan

You can change attributes in the test plan, for example, the release status, planned start and end date, or the person responsible for the test plan. You can also add test cases to your existing test plans.

From the Test Plan Management application, you can select a test plan and edit it. This will open the editor for test plans.

Depending on the release status, you can change most of the attributes, the test case selection, attachments, and test packages. Test plan ID, solution, branch, view, release schema and executables cannot be changed after the test plan has been created.

If changes are not allowed, you can only change the release status value, to eventually allow changes again. You can no longer change attachments, test packages, or any other data.

Tab	Functions
General Data	Caution If you change the system role of a test plan, this can lead to inconsistencies in the test results, if the test plan has already been processed, because you now access test cases in other systems. Only change the system role if it will not cause inconsistencies. End of the caution. You can display who created and last changed the test plan, and the associated times. You can see if changes occur in the solution documentation on which the test plan is based: Structure changes: New nodes were added or nodes belonging to the test plan were removed. Test document version: A new version was uploaded for the solution. A new test data variant was selected for a test configuration.
Settings	You can, for example, edit the documentation type for test notes or change the release status. You can define at which level, the expected test effort is to be managed, and display or specify the expected test effort values. The system shows the actual effort (the actual effort expended by testers) automatically. For more information, see Planning Test Schedules and Resources. You can attach documents that are relevant for test planning and execution, for example, MS Excel spreadsheets of test data.
Test Case Selection	You can select or discard test cases. In the Change column, you can see which test cases and nodes were changed in the solution compared to the last image used in the test plan. For changes on the test document version or test data variant, you can adopt the change in the test plan. In this case, the test status for the corresponding test cases is reset. Status information for test cases or executables that have already been put in the test plan, is lost when you deselect the test case and save your test plan and test package.

Tab

Functions

General Data

Caution Caution

If you change the system role of a test plan, this can lead to inconsistencies in the test results, if the test plan has already been processed, because you now access test cases in other systems. Only change the system role if it will not cause inconsistencies.

End of the caution.

You can display who created and last changed the test plan, and the associated times.

You can see if changes occur in the solution documentation on which the test plan is based:

Structure changes: New nodes were added or nodes belonging to the test plan were removed.
Test document version: A new version was uploaded for the solution.
A new test data variant was selected for a test configuration.

Settings

You can, for example, edit the documentation type for test notes or change the release status.

You can define at which level, the expected test effort is to be managed, and display or specify the expected test effort values. The system shows the actual effort (the actual effort expended by testers) automatically. For more information, see Planning Test Schedules and Resources.

You can attach documents that are relevant for test planning and execution, for example, MS Excel spreadsheets of test data.

Test Case Selection

You can select or discard test cases.

In the Change column, you can see which test cases and nodes were changed in the solution compared to the last image used in the test plan. For changes on the test document version or test data variant, you can adopt the change in the test plan. In this case, the test status for the corresponding test cases is reset.

Status information for test cases or executables that have already been put in the test plan, is lost when you deselect the test case and save your test plan and test package.