Creating and Editing Test Plans

Use

You 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 within to the set of solution, branch, and view on any level. But usually, test cases and executables are assigned to a process step. These test cases are performed by testers, who can thereby call the assigned executables and run the test cases.

Note Note

In SAP Solution Manager, test plans can only be based on solution, branch, and view. For more information, see SAP Help Portal at http://help.sap.com, in the Test Workbench application help under Start of the navigation path Test Organizer Next navigation step Test Plan Create Test Plan End of the navigation path .

End of the note.

Prerequisites

You have defined the solution documentation and its system landscape, in SAP Solution Manager.
In the Solution Documentation view of the Test Management work center, you have access the solution, branch and view that you want to test.
In the solution documentation, you have defined the executables that you want to test or to 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.

We recommend that you create test configurations directly from the solution documentation, as it gives a better support for executable assignment.

Activities

Creating a Test Plan

Under Test Plan Management in the Test Management work center, choose Test Plan Create .

The editor for test plan management has several tabs to enter all test plan relevant data. You must define some mandatory information under General Data, Settings, and Dates 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 will be able to access the test plans for which he is responsible.
- Under Process Documentation, select the solution, branch, and view to which the test plan belongs.
  
  Note
  Once the test plan is saved, 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.
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 Selectiondefines how the executables are displayed when a user selects test cases in a test plan. There are two options:
    
    Hide Executable when Test Case is Missing 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.
    
    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.
    
    With both options, 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.
  - 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 Management Test Management with 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 type that is 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 package. 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.
Dates tab:

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.
The Test Case Selection tab only shows the hierarchy corresponding to what you select for the test plan. Here, you can refine the selection and define the exact scope of the test package.
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 pPerson
- 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.

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 view, 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 and test packages.

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.
Settings	You can, for example, edit the documentation type for test notes or change the release status. You can attach documents that are relevant for test planning and execution, for example, MS Excel spreadsheets of test data.
Dates	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.
Test Case Selection	You can select or discard test cases. 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.