AD_How-To Guide - Option 1 TWB

8/18/2019 AD_How-To Guide - Option 1 TWB

http://slidepdf.com/reader/full/adhow-to-guide-option-1-twb 1/70

Confidential

SAP Solution Manager

SAP Solution Manager Test Workbench

Configuration & Implementation Guide

Applicable Releases:

Solution Manager 7.1



CONFIGURATION AND IMPLEMENTATION GUIDE - SAP SOLUTION MANAGER TEST WORKBENCH

2

TABLE OF CONTENTS

1

PREREQUISITES .............................................................................................................................. 4

1.1

General Requirements .................................................................................................................... 4

1.2 Basic Test Management Setup ....................................................................................................... 4

1.2.1 Activate Solution Manager Services .................................................................................................. 4

1.2.2

Activate Workflow Functionality ......................................................................................................... 7

1.2.3 Setup Release Status Schema .......................................................................................................... 8

1.2.3.1 Define Status Values ......................................................................................................................... 8

1.2.3.2 Setup Release Status Schema .......................................................................................................... 9

1.2.4

Set-Up Automatic E-Mail Notification for Testers ............................................................................ 10

1.2.4.1 Setup SAPconnect ........................................................................................................................... 10

1.2.4.2

Setup Periodic Job for SAPconnect ................................................................................................ 13

1.2.5 Define Test Case Types .................................................................................................................. 15

1.2.6

Test Case Status definition .............................................................................................................. 15

1.2.7 Activate BI Reporting ....................................................................................................................... 16

1.2.7.1 Set BI-Relevant Flag in Release Status Profile ............................................................................... 17

1.2.7.2 Setup BI Reporting .......................................................................................................................... 19

1.2.7.3 Map Customer Specific Status Values for BI Reports ..................................................................... 20

1.2.8 Settings for Test Effort Calculation and Recording ......................................................................... 22

1.2.8.1

Expected Test Effort ........................................................................................................................ 22

1.2.8.2 Automatic Recording of Test Efforts ................................................................................................ 22

1.2.9

Test Case Document Types ............................................................................................................ 23

1.2.10 Keywords for Test Cases ................................................................................................................. 24

1.2.11 Test Note Setup ............................................................................................................................... 26

1.2.12

Transaction Type for Service Desk Message .................................................................................. 26

1.3 Authorizations and User Parameters .......................................................................................... 27

1.3.1 SAP Solution Manager System ....................................................................................................... 27

1.3.2 Managed System ............................................................................................................................. 28

1.3.2.1

Standard Authorizations .................................................................................................................. 29

1.3.2.2 Trusted Authorizations ..................................................................................................................... 30

2 STEP-BY-STEP PROCEDURE....................................................................................................... 31

2.1 Test Preparation ............................................................................................................................ 31

2.1.1

Define and Assign Test Cases ........................................................................................................ 32

2.1.2

Test Case Attributes ........................................................................................................................ 35

2.1.2.1 Other attributes ..................................................................................Error ! Bookmark not def ined.

2.1.2.2

Document Links ............................................................................................................................... 37

2.1.2.3 Test Objects ..................................................................................................................................... 38

2.1.3

Check Test Case Coverage of Business Processes ....................................................................... 39

2.2 Test Planning ................................................................................................................................. 40

2.2.1 Create a Test Plan ........................................................................................................................... 40

2.2.2

Create a Test Package .................................................................................................................... 44

2.2.3 Assign Test Package(s) to Tester(s) ............................................................................................... 45

2.2.4 Setup Test Sequences .................................................................................................................... 47

2.2.5

Check Assignment of Test Cases to Test Plan and Test Packages ............................................... 48

2.2.6 Effort Calculation ............................................................................................................................. 50

2.2.7 Release your Test Plan ................................................................................................................... 51

2.3

Test Execution ............................................................................................................................... 53

2.3.1

Perform a Manual Test .................................................................................................................... 53 2.3.2 Set Test Status ................................................................................................................................ 55

2.3.3 Create a Message ........................................................................................................................... 55




3

2.3.4

Create a Test Note .......................................................................................................................... 57

2.4 Test Reporting ............................................................................................................................... 58

2.4.1 Check Status for Current Test Phase .............................................................................................. 59

2.4.2

Check Messages for Test Plan ........................................................................................................ 61

2.4.3

Create a Test Report ....................................................................................................................... 61

2.4.4 Use Test Reporting Features Based on SAP BI............................................................................. 64

2.4.4.1

Status Report ................................................................................................................................... 65

2.4.4.2 Progress Report ............................................................................................................................... 66

2.4.4.3

Messages Report ............................................................................................................................. 67

2.4.4.4 Test Effort Report ............................................................................................................................ 67

Further Help ................................................................................................................................................... 68




4

1 PREREQUISITES

Before the setup activities for Test Management can be started, some prerequisites need to be fulfilled.

1.1 General Requirements

For the purposes of this document, the following assumptions are made:

- Initial- and Basic Configuration has been performed with transaction SOLMAN_SETUP

- SAP Solution Manager Landscape Management Database is setup and contains system definitionabout satellite systems under test

- Managed systems considered for testing are available in Solution Manager Landscape Managementand are assigned to logical components and appropriate System roles (transaction SMSY)

- RFC destinations from Solution Manager to managed system and vice versa have been created

- Users have been created as system users and business partners (with role ‘Employee’) in SAPSolution Manager, and e-mail addresses have been assigned to the users

1.2 Basic Test Management Setup

The following describes test management specific configurations that have to be made before you canproductively use the manual testing functionalities within SAP Solution Manager.

Note

The settings explained in this chapter have to be made only once prior to productive usage. Hence,making these settings is a one-time effort.

Once you have performed the steps explained in detail below, you will be able to perform basic manualtesting activities using the features explained in chapter 2.

1.2.1 Activ ate Solut io n Manager Services

As a first mandatory configuration step, you have to activate the services for the Web Dynpro applications.The service activation assures that the test cases in a test package can be sorted into a specified sequenceand allows you to make settings for Test Workbench BI Reporting.

To activate the services, proceed as follows:

1. In the SAP Reference IMG, choose SAP Solution Manager Implementation Guide SAP SolutionManager Capabilities Test Management Standard Configuration Activate SolutionManager Services.




5

2. Click on w to execute the IMG activity.This opens the Choose Activity dialog box.

3. In the Name of Activity column, place the cursor on Activate Service and click on .

The ICF: Report for Activating Special Service During Installation screen opens.

4. In the Technical Name field, enter SM_IMPLEMENTATION.

5. Choose Execute ( ) to run the report. A screen opens to inform you that the services have been activated.

6. Choose the Exit pushbutton ( ).Back on the Choose Activity dialog box, you can see that the activation of the service has beenperformed.




6

Opt ional :

To check the service activation, proceed as described below. The following only describes how tocheck the activation of the “BI-based Test Workbench Reporting” service.

7. Place the cursor on Check Service Activation and click on ( ).

8. On the Maintain Services screen, enter SERVICE in the Hierarchy Type field and choose the

Execute pushbutton.

The Maintain service screen opens.

9. In the Virtual Hosts / Services hierarchy, go to default_host sap bc webdynpro sap aiccmsbi_twb_setup (Set-Up Test Workbench BI Reporting).

10. Right-click on the service ‘aiccmsbi_twb_setup’.

11. From the context menu, choose the option Test Service.




7

If the service has been properly activated, the following screen is displayed in your browser:

12. Close your browser and exit the Maintain service screen.Back on the Choose Activity screen, a green tick indicates that the check of the service activation

has been performed.

13. Choose Exit ( ) to return to the IMG.

1.2.2 Activ ate Work f low Func tion ali ty

Using the workflow functionality, a test coordinator can specify actions that the system triggers at pre-definedevents in the test management process or during testing. Sending an e-mail is the default behavior. Moreprecisely, the system informs assigned testers about released and locked test packages and test cases.Therefore, the workflow functionality can help you reduce coordination effort during the test phase and

allows you to accelerate test execution.In general the setup of the workflow functionality in focus should be functional with the standard settingsprovided by a SAP Solution Manager System. After a successful SAP Solution Manager Basic Configurationthe standard Workflow Configuration should already be activated. However, additional configuration settingsneed to be checked/setup.Call transaction SPRO SAP Reference IMG SAP Solution Manager CapabilitiesTest Management Extended Configuration Workflow

Standard Transaction Types along with Action Profiles, Conditions etc. should already exist and ready foruse after the SAP Solution Manager Basic Configuration. Further customizing activities in this area are not inscope of this guide.By launching IMG activity ‘Set-Up Workflow’ it needs to be checked whether the correct Transaction Typesare assigned:




8

1.2.3 Setup Release Status Schem a

As test coordinator you can use this function to lock or release Test Workbench objects, such as test plansand test packages, to be changed or executed by the tester. The release status schema defines a set ofrelease status values that you can set in the test plan.

Integration

You can use workflow as well as the release status schema. This means you can control and monitor theexecution of tests more effectively. For example, the system tells testers when their test packages are readyfor testing.

FeaturesDepending on the release status values settings in Customizing, you can influence the release of test plansand packages in the following ways:

Settable release status values A status number is assigned to each release status value. The status numbers specify the releasestatus values sequence in the release status schema. The system determines the settable releasestatus values from the highest and lowest status numbers assigned to each release status value inthe test plan attributes, and shows them in the input help.

Change lockIf a settable release status value is locked for changes in the test plan attributes, the attributes andstructure of the test plan, including its test packages, cannot be changed.

Execution lockIf a settable release status value is locked for execution in the test plan attributes, a tester cannotexecute his tests. He or she cannot change the test status.

Signature strategy (not in scope of this document) A signature strategy is a combination of individual signatures required to sign a procedure. Itspecifies:

o Which individual signatures are required, that is, which user groups must sign the procedure

o In which order the individual signatures must be attainedo With which signature or signatures the signature process is completeo Which signature method is used for signing, for example, user signature or system signature

authorized by user ID and password.If a signature strategy is assigned to the release status value set in the test plan attributes, thesepersons must sign to fulfill the signature strategy. If the signature strategy is fulfilled, the systemsets the end status value. If the signature strategy is cancelled, the system sets the cancelstatus value.You can assign signature strategies to the release status values. This only makes sense forstatuses that have a defined end and cancellation status value, that is, review status in thestandard release status schema.

1.2.3.1 Define Status Values

Before a Release Status Schema will be prepared, appropriate status values need to be defined. SAPSolution Manager already contains predefined status values which can be reused in Release StatusSchemas, but self-defined values can be setup as well. Perform the following steps to do so:




9

1. Call transaction SPRO SAP Reference IMG SAP Solution Manager Implementation Guide SAP Solution Manager Capabilities Test Management Extended Configuration ReleaseStatus Profile.

2. Launch ( ) Activity Specify Release Status Values.

3. The following table contains all existing status values.

4. Define new status values using the button in Change Mode and provide a properdescription.

5. Save entries when finished.The status values can now be used for a Release Status Schema.

1.2.3.2 Setup Release Status Schema

Once the status values have been defined, a Release Status Schema can be set up:

1. Call transaction SPRO SAP Reference IMG SAP Solution Manager Implementation Guide SAP Solution Manager Capabilities Test Management Extended Configuration ReleaseStatus Profile.

2. Launch ( ) Activity Set Up Release Status Profile.

3. The displayed table contains an overview of all existing Release Status Schemas in the system.

4. Create a new schema using the button. Define a Status Schema name and description(Explanatory Text).

5. Save.




10

6. Select your previously defined Release Status Schema from the list and choose test Plan ReleaseStatus Values.

7. The new screen contains a table with several (empty) columns you need to provide data for:a. Status Number: define numbers in a sequence for the status values you want to include.

b. Status: Provide Status Value via F4 help from the selection screen.

c. Initial: Mark the value reflecting the initial status of Test Plan.

d. Lowest/Highest Number: Defines the lowest or highest Status Value which can be selectedaccording to the Status Number sequences defined.

e. Change Lock: Mark Status Values for your Test Plans which do not allow changing TestPlan content.

f. Execution Lock: Mark Status Values for your Test Plans which do not allow test execution.

g. Signature Strategy: Optional field. Allows assigning already defined signature strategiesalong with End- and Cancelation Status for a digital signature (not in scope of thisdocument).

h. BI Relevant: Mark Status Values relevant for later BI Reporting. Only Test Plan relevantinformation will be collected for BI Reporting when a Test Plan status is explicitly defined.This provides that test related data is extracted permanently for all Test Plans which helps toprotect system performance and database growth.

1.2.4 Set-Up Au tom atic E-Mail Notif icat ion for Testers

The setup of automated e-mails is required to enable automated notification for testers participating in testingactivities.This setup step is a prerequisite for Test Management in SAP Solution Manager if you want to use theworkflow functionality.E-mails sent from an SAP application are first sent to a queue. The queued e-mails are then subsequently

sent by a periodic background job.

For automatic e-mailing you have to perform the following activities:a) Set up SAPconnect (chapter 1.2.4.1)b) Set up a periodic job for SAPconnect (chapter 1.2.4.2)

1.2.4.1 Setup SAPconnect

SAPconnect provides a standard interface for external communication, which supports sending usingtelecommunication services, such as FAX, text messages (pager/SMS), Internet mail and X.400, as well assending to printers and between different SAP Systems. It enables external communication components tobe connected to the SAP System.




11

SAPconnect provides a direct connection to the Internet through the SMTP plug-in of the SAP Web Application Server. This enables you to send and receive Internet mails, faxes and text messages(pager/SMS) directly, without having to use additional external communication systems.

Required basic settings for SAPconnect are usually provided during the Basic Configuration setup of a SAPSolution Manager System. For setting up/verifying SAPconnect functionality proceed as follows:

1. In the SAP Reference IMG, go to SAP Solution Manager Technical Settings Set UpSAPconnect

2. Click on to execute the IMG activity.This opens the SAPconnect: Administration screen.

3. To ensure that you are using the appropriate view, choose View System status.

4. In the menu bar, choose Settings Default Domain.

5. Specify your default domain (e.g. <mydomain.com>) and confirm your entry by choosing Continue.

6. On the SAPconnect: Administration screen (system status view), double-click on the SMTP node.

The SAPconnect: General node data screen opens.

7. In the General Information section, specify the Maximum waiting time for repeat send attempt procedure (e.g. one minute).

8. Choose the Node in Use checkbox.




12

9. In the SMTP Connection section, specify the Mail Host for SMTP (e.g. "mail.mydomain.com").

10. Specify the Mail Port .By default, the port is set to 25.

11. Select the desired entry from the Code Page dropdown box, e.g. 1100 SAP-internal, like ISO 8859-1.

12. In the Supported address types section, choose the Set pushbutton next to the Internet entry.The SAPconnect: Address type for node dialog box opens.

13. In the Address areas text box, enter an asterisk (*).

14. In the area of Output Formats for SAP Documents set TXT for SAPscript / Smart Forms.




13

15. Confirm your entry by choosing Continue.

1.2.4.2 Setup Periodic Job for SAPconnect

The following describes how to schedule the periodic background job to send queued e-mails:

1. In the SAP Reference IMG, choose SAP Solution Manager Implementation Guide SAP SolutionManager Cross-Scenario Settings Automatic E-Mail Set-Up SAPconnect .

2. Click on to execute the IMG activity.This opens the SAPconnect: Administration screen.

3. To ensure that you are using the appropriate view, choose View Jobs.

The SAPconnect: Administration (jobs) screen opens.




14

4. In the menu bar, choose Job Create.

The Schedule send process dialog box opens.

5. In the Job name field, specify a name for the periodic job.

6. Confirm your entry by choosing Continue.The SAPconnect send process: Variants screen opens.

7. In the list of variants, select the entry SAP&CONNECTALL.

8. Choose the Schedule pushbutton.The SAPconnect send process Scheduling: Start Time screen opens.






16

1. Call the Work Center for Test Management Administration Central Test Workbench Settings Status definition.

2. The table containing all defined status values appears.

3. Provide a proper status and status description.

4. The traffic light indicates whether a Test Case of a specific type will be shown as red, yellow orgreen in e.g. the Status Overview as well as in the BI Reporting.

5. Provide input for the parameter SortField which allows sorting values according to numbersprovided.Status values are listed from top to bottom for the testers beginning with the smallest number inSortField column.

Note:When customer specific status values are being configured, take care to setup the mapping to SAP standardvalues for the BI Reporting capabilities! Details see chapter for BI Reporting 1.2.7.

1.2.7 Activ ate BI Report in g

To be able to use BI-based test reporting features, the settings explained below have to be made inadvance. Activating the BI reporting capabilities does not require BI expertise.

The standard setup for the BI client in SAP Solution Manager System has been performed in the course ofthe basic configuration. If the productive SAP Solution Manager client is located in a different client than theBI client, the RFC connection to the BI client has to work properly (RFC could be different, depending on

your system setup):




17

The setup activities for BW Reporting require specific additional authorization:

SAP_BI_E2E

SAP_BI_TWB

SAP_SM_BI_DISP

SAP_SM_BI_EXTRACTOR

The SAP standard roles should be copied to the customer namespace (details see chapter 1.2.2). For furtherdetails see Security Guide for SAP Solution Manager 7.1: http://service.sap.com/instguides

NoteWe recommend that you check SAP Note 1333715 on a regular basis, as this note documents known issues

and appropriate solutions with regard to BI Reporting for Test Management. Additionally, review the following SAP notes:Note 1433304 - TWB BI Reporting: Data migration Note 1603682 - You cannot filter by customer attributes in TWB BI Reporting Note 1616737 - TWB Reporting setup cannot be executed

In general the IMG contains all required activities which need to be performed. Go to transaction SPRO SAP Solution Manager Capabilities Test Management BW based Reporting

If it is required to use own priorities for incident messages different from SAP standard, a mapping to SAPstandard values needs to be done. The same counts for Test Case status values, which also need to bemapped first when customer specific customizing is in place. The details are described in IMG steps ‘AssignOwn Message Priorities’ and ‘Assign Own Status Values’ and will not be introduced further in this guide.

1.2.7.1 Set BI-Relevant Flag in Release Status Profile

The use of a Release Status Schema helps controlling a Test Plan and is used to switch phases of a testcycle, e.g. whether test execution is allowed, blocked or changes can be done to a Test Plan. The ReleaseStatus Schema is part of a Test Plans attributes and can be setup according to the customer´s requirements(see transaction SPRO SAP Solution Manager Capabilities Test Management Extended

Configuration Release Status Profile).

http://service.sap.com/instguides



https://service.sap.com/sap/support/notes/1433304













18

Whether data of Test Plans is considered for the BI reporting also depends on the setup of Release StatusProfiles and appropriate status values in use. SAP delivers standard Release Status Profiles which can beused instantly.For example you have specified the release status values for which BI data shall be extracted. You may, for

example, not want to consider test plans that are in status ‘new’. To specify the BI relevance of the individual test plan status values, proceed as follows:

1. In the SAP Reference IMG, choose SAP Solution Manager Capabilities Test Management Extended Configuration Release Status Profile Set Up Release Status Profile.

2. Click on to execute the IMG activity.

3. Confirm the dialog box that opens by choosing Continue.

The overview screen for release status schemas for test plans opens.

4. In the Dialog Structure on the left of the screen, choose the Release Status Schema for Test Plan folder.

5. In the list of status schemas, select the desired entry, e.g. DEFAULTS or a customer specificschema.




19

6. In the Dialog Structure, double-click on the Test Plan Release Status Values sub-folder.

7. Select or deselect the BI-Relevant checkbox for each status value as required. Only Test Plan

relevant information will be collected for BI Reporting when a Test Plan status is explicitly defined forthis purpose. This provides that test related data is extracted permanently for all Test Plans whichhelps to protect system performance and database growth.

8. Choose Save.

1.2.7.2 Setup BI Reporting

To be able to use BI-based test reporting features, you still have to enable and configure the appropriate BIreporting settings. This is done as follows:

1. Call up transaction SOLMAN_WORKCENTER to access the work center, which serves as centralaccess point for SAP Solution Manager.

2. From the navigation bar, choose the Test Management work center.

3. From the navigation area on the left of the screen, choose Administration.

4. From the content area, choose Reporting (Analytics) Settings.




20

The Settings for Test Workbench BI Reporting service opens in a separate window.This service allows you to activate the BI Content. In addition, you can enter the RFC connectionsfrom SAP Solution Manager to the BI system and vice versa, and specify when data shall beextracted from SAP Solution Manager every day.

5. Select the Enforce content activation checkbox.

6. Choose Save.

1.2.7.3 Map Customer Specific Status Values for BI Reports

For proper BI Reporting it is relevant that customer specific status values which might have been definedpreviously are mapped to SAP standard status values. To setup the mapping perform as follows:

1. Ensure you have a Test Plan that is BI relevant and an extraction has been performed to BW.

2. Launch a BW based Status Report and scroll down to the botton3. Here you find the buttons ‘Configuration View’ and ‘Store Global View’




21

4. Click on ‘Configuration View’ Here you can insert and re-arrange the mapping of all the status values to up to 6 groups that willalso reflect the different colours:

Test Case Status (1): green

Test Case Status (2) yellow

Test Case Status (3) red

Test Case Status (4) blue

Test Case Status (5) grey Test Case Status (6) white

The first entry for each Status is used as description for the column / legend in the report.Hint: When using the search help for selecting multiple status values for one mapping they will besorted in alphabethical order, so CATT….. is always first. To avoid this enter the values manually.

5. Apply your mapping while clicking the ‘Execute’ button.6. To save the mapping please click on ‘Store Global View’

Repeat the mapping for each BW based Report




22

Please Note: As soon BI content is activated e.g. after an SP update, the mapping need to be re-done andstored.

1.2.8 Sett ings for Test Effort Calculat ion and Recordin g

SAP Solution Manager supports you regarding the calculation of expected test efforts for test execution andalso allows the (automatic) recording of the actual test effort. The following chapter introduces relevantsettings for test effort calculation and recording.The expected effort for the execution of a single Test Case can be defined centrally or per single Test Caseas specific attribute.

A pragmatic approach would be a combination of both defining the default value that fits to most Test Casesand specify dedicated values when a big deviations from the default is expected.

1.2.8.1 Expected Test Effort

Perform the following steps enter the central settings for Test Case efforts:

1. Call transaction SOLMAN_WORKCENTER

2. Choose the Work Center for Test Management Administration

3. Choose Default Required Time for Test Case Types.

4. Define expected test efforts as required.

Note:Setting defined for Manual Test Case also count for Test Case Type Test Document.

If you want to define test effort individually for specific Test Cases, refer to chapter 2.1.2.

1.2.8.2 Automatic Recording of Test Efforts

SAP Solution Manager 7.1 supports the automated recording of time which is required for the execution ofmanual Test Cases. By default this setting for automatic recording is disabled, for activation please performthe following activities:

1. Call transaction SPRO and open the SAP Solution Manager Reference IMG

2. In IMG view go to SAP Solution Manager Capabilities Test Management ExtendedConfiguration

3. Start the IMG activity for Automatic Recording of Test Effort for Manual Test Cases




23

4. In the new screen choose New Entries and provide parameter MTC_TIME_RECORDING with value X .

5. Save.

1.2.9 Test Case Docum ent Types

In order to create Test documents based on a specific customer template, it is recommended to createspecific Document Types in SAP Solution manager for this purpose. The Document Types are part of theProject Standards of a SAP Solution manager Project.

Call transaction SOLAR_PROJECT_ADMIN choose your project Project Standards tab DocumentTypes tab Project Template

A new Document Type can be setup as follows:

1. Define a new Documentation Type and Name in a blank row of the right hand side of the screen

shown above. Enter a shortcut representing the Document Type and a name for it.

2. On the right hand side of the screen ‘Complete Directory of Document Types’ (see screenshotabove) additional settings can be made.

3. Define whether Document Types should be used globally for all Projects or only for a the specificone by (de)selecting the relevant checkbox

4. Take care to allow that several documents of this document type are allowed at one structure node,otherwise only one document based on the newly created document type is possible at a time pernode (select relevant Checkbox)

5. Provide the document file extension of the documents to be created (e.g. DOC)

6. Assign a Status Schema for documents if wished




24

7. Upload customer document template to SAP Solution Manager (see screenshot on previous page):

a. Mark the line representing your newly defined document type

b. Choose Document Template button below the table Import and upload physical templatefrom a hard drive.

8. Select the line representing the newly created Document Type and move it to the left side using the

left arrow button

9. Save and close Window

10. On the tab for ‘Document Types’ take care to take relevant document types created before to the

‘Project Documentation Types’ in scope using the button.

1.2.10 Keyw ords for Test Cases

Keywords can be used as filter during test scope definition. Assignment to relevant Test Cases as forexample indication about test relevance, geographical or organizational attributes. Keywords are easy to setup. To set up a Keyword, perform the following steps:

1. Call transaction SOLAR_PROJECT_ADMIN choose your project Project Standards tab Keywords tab Project Template




25

2. Create new Keyword in the ‘Complete Directory of Keywords’ when in change mode in a blank lineof the table (see screenshot above).

3. Move the appropriate Keywords to the ‘Project Keywords’ on the left hand side of the screen by

using the button. Save and close the window.

4. In the Keywords tab select required rows containing the keywords in scope and move those to the‘Project Keywords’ by using the arrows of the screen pointing to the left side. Save.

The Keywords can now be selected as Test Case Document attribute and also on the administration tab inBusiness Blueprint and Configuration (SOLARxx) transaction.

Please Note: If you plan to work with Solution Directory the Keyword assigned to the Admin Tab will not beavailable in the Solution as no Admin Tab exists in Solution Directory. Therefore for classifying Scenarios /Processes and Steps the Structure attributes shall be used.




26

1.2.11 Test Note Setup

Test Notes can be used during Testing to hand-over test relevant information between different tests, e.g. ina sequence based test approach. The setup of Test Notes is comparable with the setup of Test CaseDocument Types.

1. In the SAP Solution Manager Reference IMG go to SAP Solution Manager Capabilities TestManagement Extended Configuration Test Documentation (Notes).

2. Call IMG activity Select Test Documentation (Notes) Editor .

3. In the Central Workbench Settings Screen select Notes and hit the button.

4. In the Notes Editor choose the settings as following (recommended):

5. Back in the IMG as described in step 1, call IMG activity Define Template for Test Documentation(Notes)

6. In the pop-up screen take care to choose Assign Templates for KW Documents.

7. The transaction for Project Administration is called. Choose your project in scope.

8. Go to Project Standards tab and then to Document Types tab.

9. Perform activities as described in previous chapter covering Test cases Types.

Note:The default Document Type in scope is called ST . Upload your document template to this document

type or define a separate one. It will be used afterwards for Test Notes.

1.2.12 Transaction Type for Service Desk Message

To be able to follow up detected errors during testing in an adequate way the Test Workbench is integratedwith the Service Desk.By default there are 2 message types available for testing:

1. SMIN as standard message type for Incident Management to follow-up defects found during testing

2. SMDT is used to follow-up damaged test cases as part of the Test Automation Framework

It is recommended to copy standard transaction types into the customer namespace and perform further

customizing if required (not in scope of this document). The customer´s transaction types need to be




27

assigned accordingly in the SAP Solution Manager Test Workbench Settings.

1. Call transaction SOLMAN_WORKCENTER and select the Work Center for Test Management.

2. Choose Administration from the navigation menu.

3. Select Central Test Workbench Settings from the overview.

4. In the overview of Test Workbench Settings select Transaction Type for TWB Service DeskMessages.

5. Assign the appropriate Transaction Types to each of the applications.

1.3 Authorizations and User Parameters

1.3.1 SAP Solut io n Manager System

In addition to the roles and authorizations referred required for the general Work Center access, the below-mentioned roles must also be assigned to users working with the Work Center.

Standard Roles fo r Test Manager/Test Organizer:

Role Name Type Purpose/Remarks

SAP_SOL_PM_COMP ABAP composite role Organize and plan a project




28

SAP_SOL_AC_COMP ABAP composite role Create business content and documentoperational activities

SAP_SOL_BC_COMP ABAP composite role Perform technical configuration

SAP_SOL_TC_COMP ABAP composite role Develop customer-specific programs andauthorizations

SAP_SUPPDESK_DISPLAY ABAP Display authorization for Service Deskmessages

SAP_SMWORK_BASIC_TEST_MAN ABAP Basic role for using Work Center for TestManagement

SAP_SMWORK_ITEST ABAP Role for using Test Management Work Center

SAP_SMWORK_BASIC_IMP Basic Role for using Work Center forImplementation and Upgrade scenario

SAP_SMWORK_IMPL ABAP Work Center for Implementation and Upgradescenario

Standard Roles for Tester:

Role Name Type Purpose/Remarks

SAP_SOL_TESTER_COMP ABAP

SAP_STWB_WORKFLOW_CREATE ABAP Use Workflow

SAP_SUPPDESK_CREATE ABAP Make sure that authorization objectB_NOTIF_IB is active and configured as follows:Field Activity , values 01, 02, 03Field DSWP IBase number , value *

SAP_SMWORK_BASIC_TEST_MAN Basic Role for using Work Centers

SAP_SMWORK_ITEST Role for using Test Management Work Center

For more detailed information on roles and authorizations, please also refer to the Security Guide which canbe found on the SAP Service Marketplace at:http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.1 4Operations Security Guide SAP Solution Manager 7.1.

1.3.2 Managed System

The following authorization objects are required on the managed system:







29

1.3.2.1 Standard Authorizations

On the managed system, make sure that the below-mentioned standard authorization objects are maintainedas indicated.

S_DATASET: Authorization for activities 06 and 33 is required.

S_PATH: Authorization for activities 02 and 03 is required.

To maintain an authorization object, proceed as follows:

1. Call up transaction SUIM to access the User Information System.

2. Expand the node Authorization Objects and choose the By Object Name, Text transaction button.

3. In the Authorization Object field, enter the name of the authorization object that you want to maintain(e.g. S_PATH)

4. Choose the Execute pushbutton.

5. On the screen that opens, double-click on the entry for the authorization object.The Display authorization object screen opens.

6. On the Display authorization object screen, switch to edit mode.

7. Choose the Permitted Activities pushbutton.




30

8. In the Define Values dialog box, select the activities that you want to enable for the authorizationobject.

9. Choose the Transfer pushbutton ( ) to confirm your entries.You will automatically return to the Maintain authorization object screen.

10. On the Maintain authorization object screen, choose Save.

1.3.2.2 Trusted Authorizations

Trusted RFC is a “contract” between two systems in which the target system agrees to trust connectionscoming from a particular system. In this case, the logon is permitted without having to enter a password.

Since this is a particularly sensitive feature, trusted RFC is protected by an additional authorization check. In




31

order to log on to a trusted system, the user in question must possess the following:

A user in the target system

Authorizations for the applications he or she needs to use in the target system

Authorization for the object S_RFCACL (see table below)This authorization object regulates a user’s right to log on to a system via trusted connection.

Authorization Object Field Value Description

S_RFC RFC_TYPE FUGR Function group

ACTVT 16 Execute

RFC_NAME STTF eCATT auxiliaryfunctions

S_RFCACL RFC_SYSID The system ID of the originating system

RFC_CLIENT The client of the originating system

RFC_USER The user in the originating system

RFC_EQUSER Flag that indicates whether the user in the target systemmust be the same as the user in the originating system

RFC_TCODE Transaction code of the application that executed the call

RFC_INFO

ACTVT Activity (only supports 16 – Execute)

2 STEP-BY-STEP PROCEDURE

This section explains the step-by-step procedure for managing a standard, straightforward software testingcycle using SAP Solution Manager Features. For the following descriptions, we assume that a generalSolution Documentation of business process structures along with transaction assignment has already beendone.

2.1 Test Preparation




32

SAP Solution Manager provides the central infrastructure for configuring your process requirements. TheConfiguration transaction SOLAR02 is used to:

Define Test Cases

Assign BC Sets and define configuration/IMG objects for customizing during implementation orupgrade (customizing settings)

Specify development activities and modifications that are in scope of your project(development objects)

Assign Business Functions

Prepare training material for process structure content

The starting point for configuring your business processes is the business process structure that you createdin the Business Blueprint, along with all of its assignments. Therefore, configuration requires that theBusiness Blueprint has been completely created and approved.

2.1.1 Define and As sign Test Cases

You can create entirely new documents or upload existing documents that contain instructions to helpmanual testers perform tests. The documents can be built based on the Document Types createdbeforehand (see chapter 1.2.9).Test Cases are assigned to scenarios, processes, or process steps and form the basis for the test planningand execution phases.To assign a test case to the process structure, proceed as follows:

1. Call up transaction SOLMAN_WORKCENTER to access the Work Centers.


3. From the navigation area on the left of the screen, choose Test Preparation and select the Projects

view.

4. From the content area, choose the All Projects query.

5. Click on Refresh to refresh the active query. A list of all projects available in the system is displayed.

6. From the list of results, highlight the desired project by clicking on the appropriate row.




33

7. Choose Configuration to access the Configuration transaction.

8. In the Configuration Structure on the left side of the screen, drill down to the level where you want toassign the test case.

Example: To assign a test case to the ‘Create Sales Order’ process step of our sample project, chooseBusiness Scenarios Logistics Business Processes Order to Cash Create Sales Order inthe Configuration Structure.

9. Choose the Test Cases tab.

10. In the Test Case Type column, select the option Test Document from the dropdown list to set up atest case for manual testing.

11. In the Add Document dialog box, specify whether you want to create a new document or upload anexisting one by selecting the appropriate radio button.

12. Enter the Title of the document to be created.

13. In the Documentation Type field, select the option Test Case Description or another Document Typeyou have created beforehand.

14. In the Status field, select a proper value depending on your Status Schema for Documents, e.g.Released .




34

15. Confirm your entries by choosing OK ( ).In our example, a new document is created and the default template for test notes opens in thedocument editor.

16. Fill in the template with the appropriate instructions and information.

17. Choose Save.

18. Choose the Close Document pushbutton ( ).

19. Confirm the Document dialog box by choosing Yes.

To finalize the test case, the actual object which is to be tested needs to be identified as follows:




35

20. In the Test Object column, place the cursor in the cell of your test case.

21. Press F4 to call up the input help (Select Test Object dialog box).

Note: You can only assign test objects which are assigned to the same structure element in theTransactions tab. Therefore, it is crucial that the Transactions tab has been properly maintained. Inaddition, the transactions have to be set as ‘in Scope’ on the Transactions tab which shall be usedas Test Object.This allows the Tester to navigate with one click to the System under Test while the assignedtransaction is launched automatically. In addition this is needed to create TBOMs in backgroundwhen performing a manual test.

22. Choose the Copy pushbutton ( ) to assign the transaction as test object.

23. Choose Save.

24. To check the test case you previously created, highlight the line containing your test case andchoose the Display pushbutton (. ).

Note:Since the number of test cases usually increases as time goes by, you can also assign a range ofattributes to make the test cases easier to catalog and locate.

2.1.2 Test Case Attr ib utes

In addition to the Structure Attributes that can be used to classify Business Processes you can use TestCase Attributes to classify single test cases. Example: For one Process Step there are various Test Cases toreflect various use cases and test types (string, integration, user acceptance, regression test)

And they might be treated with different priority.The attributes also allow to specify for which type of test (String Test, Integration Test, Regression Test, etc.)a test case should be selected.

Attribute Type Standard Values Description Relevant

Priority X Very High - Low Filter for Test Planning andReporting




36

Status X by status schema Filter for Test Planning

Time RequiredX

Time in minutes Calculation of expected Effortused in planning and reporting

Keyword Project Standards customizing Customer definedclassification of Test Cases,Filter for Test Planning andReporting

Link

X

Other documents e.g. Reference to Specification/ Requirement documents,Filter for Test Planning andReporting

Test Object

X

Objects in Trans. Tab Reference to ExecutionObjects that are covered byTest Cases, Filter for TestPlanning and Reporting

Other attributes Knowledge Warehousecustomizing

Customer definedclassification of documents.Not recommended for TestCases as test plan filtering isnot supported.Please use Keywords for TestCase classification.

In order to access the Test Case document attributes perform the following activities:

1. Call transaction SOLMAN_WORKCENTER choose Test Management Work Center.

2. Choose Test Preparation from the navigation.

3. Select appropriate Test Plan from overview and choose Configuration.

4. Drill down to the appropriate are of the business process structure, e.g. on process step level, youwant to change attributes




37

5. The attributes of a Test Case document can be accessed via the Test Case tab of the configuration

transaction. Select the Test Case document in scope and choose the button.

2.1.2.1 Document Links

Documents can have links to other documents or even bidirectional as indication about a relationship. Atypical use case is to link a specific Requirements Document a Test Case might belong to. Such links can beused for example indication during test scoping for a user acceptance test.

1. On the Maintain Attributes screen switch to the Link tab.

2. Choose to assign a new Link.

3. From the next selection screen Add Document choose Link to SAP Solution Manager Document.

4. In the upcoming screen provide the relevant searching criteria.




38

5. Select the appropriate document from the result list given and continue.

6. A new link to the document is created. Depending on your requirements establish a bidirectional link.

2.1.2.2 Test Objects

The assignment of additional Test Objects in this tab allows referencing to Execution Objects that arecovered by Test Cases spanning more than one Test Object. Only Test Objects can be assigned which areassigned to the transactions tab of the specific process structure node. The assignment is used as filtercriteria during test planning activities.

1. On the Maintain Attributes screen switch to the Test Objects tab.

2. Choose to assign a new Test Object.

3. Choose the specific Test Object from the list provided.




39

4. A new Test Object is now assigned and can be used later on as attribute during test planning.

2.1.3 Check Test Case Coverage of Bu siness Process es

To gain reliable test results it is crucial to ensure transparency during test scope definition and test planning.Checking to what extent your business processes are covered by test cases allows you to identify potentialgaps in your test scope and hence supports the sign-off process for test scope and test planning.To check the completeness of your test scope, proceed as follows:

1. Call up transaction SOLMAN_WORKCENTER to access the work center.


3. From the navigation area on the left of the screen, choose Test Preparation and select the Projects view.

4. From the content area, choose the My Projects query.

5. Click on Refresh to refresh the active query. A list of all projects assigned to you is displayed.

6. From the list of results, highlight the desired project by clicking on the appropriate row.

7. Choose the Evaluate pushbutton.This opens the Evaluate Transactions / TBOMs / Test Cases screen.




40

8. At the bottom of the screen in the Test Cases section, select the Nodes without Test Cases radiobutton.

9. At the top of the screen, choose Execute ( ).The results screen opens.

Select the topmost element in the Project Structure column and choose Expand subtree ( ). All business processes that have no test case assigned to them (no ‘X’ in Test Cases column) are displayed.

This allows you to see at a glance what still needs to be done to complete the test scope definition.

2.2 Test Planning

Once the test focus resulting from the planned changes is known, the relevant test cases can be identified.Based on the test cases, you can generate test plans and test packages. All activities regarding planning of manual tests are supported by the SAP Solution Manager TestWorkbench (TWB).

2.2.1 Create a Test Plan

Test Plans serve as central objects for activities related to planning and coordinating tests.They are used to group all relevant test cases for an actual test cycle. In other words, a test plan containsthe scope of a test cycle, based on the test cases assigned to the business process structure. Hence, all testplans that you create during test planning are based on the Business Blueprint project structure.During test plan generation, the transactions you previously assigned to the process structure are put in thetest plan(s).

The following describes how to create a test plan using the Test Workbench in SAP Solution Manager:



3. From the navigation area on the left of the screen, choose Test Plan Management .

4. In the content area, click on Test Plan and choose Create Test Plan from the context menu.The Create test plan dialog box opens.




41

5. In the new window under Template, make sure the name of the project in scope you previouslydefined is selected in the Project field.

6. Under General Data, in the Test Plan Header Data section, specify a Title for the test plan you areabout to create.

7. Under General Data, in the Release section, select an entry from the Status Profile dropdown box,e.g. DEFAULTS.

Note: Using a release status schema is required if you want to use the workflow functionality and BIReporting.

8. In the area of Planning Data you can provide information about the effort calculation level for theTest Plan to be defined. Provide data for the start and end date as indicator for your testers about

expected timelines to increases transparency. Go to the next page using the button.

9. Under Defaults, in the Settings section, select the Only Released Test Documents checkbox to

indicate that only released test documents shall be taken into account during generation of the test




42

plan.

10. Confirm your entries by choosing the button to move to the Test Plan for further editing.

11. On the test plan creation screen, choose the Expand All pushbutton ( ) to expand the Test PlanStructure on the left of the screen.

12. In the Test Plan Structure, select the test cases that shall be in scope of the test plan. At this pointyou can reuse the business process attributes as well as the test case attributes defined before. The

button opens additional screen elements allowing you to filter on multiple criteria.

13. Once you have defined the scope, choose the Generate Test Plan pushbutton ( ).

14. In the Create Object Directory Entry dialog box, choose e.g. Local Object .You will automatically be returned to the Test Plan Management area within the Test Management work center.

15. Back in the Work Center for Test Management; choose the My Test Plans query.

16. Click on Refresh to refresh the active query.The test plan you have just created is displayed in the table.




43

17. In the Test Plan column, click on your test plan.The Test Plan Attributes screen opens.

18. Choose the Change pushbutton ( ) to switch to edit mode.

19. In the System Role field, make sure the correct entry is selected.The system role defines which system is used as the system under test (e.g. Quality Assurance).

20. Select the Workflow Active checkbox to enable the workflow function for your test plan. The workflowfunctionality can specify and start actions at specified events in the test management process orduring testing. Sending an E-mail is the default value.When the Workflow Active checkbox is selected, automatic e-mail notifications are sent to therelevant testers when packages are assigned to them or the status of the test plan changes.

Note: You can only activate the workflow if you are using a release status schema.

21. Choose Save.

22. Choose the Exit pushbutton ( ) to return to the work center.




44

2.2.2 Create a Test Pack age

Test packages are used to assign manual test cases to selected testers. A test package contains all the testcases that a tester is to perform within a specific time period. One and the same test package can be

assigned to various testers.Test packages can be created based on the test cases that are included in the test plan.Once a test package has been assigned to a tester, the tester can see his or her assignment(s) and therelevant test cases in the Tester Worklist.




4. Choose the My Test Plans query.

5. Highlight the desired test plan.

6. Choose Test Package Management .

The Test Package Management – Test Organizer screen opens.

7. Choose the Create Test Package pushbutton ( ).The project structure underlying your test plan is displayed.

8. Choose the Expand All pushbutton ( ) to expand the structure.

9. Select the nodes that are relevant for your test package.




45

10. Once you have made your selection, choose the Generate pushbutton ( ).The Create Test Package dialog box opens.

11. In the Title field, enter a short description for the test package.

12. Choose Continue.

13. In the Create Object Directory Entry dialog box, choose Local Object .You will automatically be returned to the Test Package Management – Test Organizer screen whereyou can assign the newly generated test package to one or more testers (see next chapter).

2.2.3 Ass ign Test Package(s) to Tester(s)

A test package is usually assigned to one tester. The tester finds this test package as a work list in the TestManagement work center. You can also lock or delete a test package for a tester.

Note: Test package assignments are client-specific.






6. Choose Test Package Management .

The Test Package Management – Test Organizer screen opens.

7. Select the test package to be assigned.

8. Choose the Assign Tester pushbutton ( ).




46

The Restrict Value Range dialog box opens.

9. In the User field, enter the user name of the tester to whom you want to assign the test package.

10. Choose Continue.

11. Select the appropriate entry from the Hit List.

12. Choose the Copy pushbutton ( ).

The tester assignment is put in the hierarchy.

Note: If you use different test packages to assign one and the same manual test case to multiple testers, itmay happen that their results differ. In that case, the worst result is applied as the overall status ofthe test case. If the different statuses are OK , OK with Reservations, and Untested , the overall statusis set to OK .




47

Once a test plan is released, the test packages that are included in the test plan can be executed by theassigned testers.

2.2.4 Setup Test Sequences

You can sort the test cases in a test package into a specified sequence – a test sequence. This is useful, forexample, when a test case in a business process depends on the results of another test case.The test sequence specifies that a test case is only available for testing when the predecessor test case hasbeen completed. The Ready for Testing flag indicates whether a tester may perform the test. Perform thefollowing activities to setup a sequence.



3. Select Test Plan Management from the navigation menu.

4. Select Test Plan in scope and choose Goto – Sequences.

5. A new browser window is displayed: Sequences – Test Organizer

6. Select the test package in scope and switch to change mode.

7. Provide the user information for each single Test Case indicating the required sequence.




48

8. Select all test cases you want to define as a sequence and select Sequences Create.

9. Provide a unique SequenceID and hit OK .

10. Save you sequences. The sequences should be ready to use.

2.2.5 Check As signment of Test Cases to Test Plan and Test Packages

The Test Workbench functions helps you to find out whether there are test cases which are not included in atest plan or test package.To create a negative list of test cases that are not assigned to a test plan or test package, proceed asfollows:



3. From the navigation area on the left of the screen, choose Reports.




49

4. In the content area, go to the Description column and drill down to Test Project Status Analyses.

5. In the Type column, click on Report .This opens the Test Case Status Analysis screen.

6. In the Project field, make sure the correct project name is entered.

7. In the System Role field, verify that the desired system role is selected.

8. In the Status Attributes section, select the Not Assigned to a Test Package and Test Case in No TestPlan checkboxes.

9. At the top of the screen, choose Execute ( ).The results screen opens.

10. Select the topmost element in the Project Structure column and choose Expand subtree ( ). A list of test cases without assignment to test plans or test packages is displayed.




50

A remark in the Status Text column indicates what kind of assignment is still missing for the relevant

test case.

2.2.6 Effort Calculat ion

When Test Planning is finalized SAP Solution Manager can automatically calculate the expected effort for

the Test Plan in scope. The effort calculation is part of the Test Plan attributes. This activity is not mandatoryfor the BI Reporting effort reporting later on!






6. Choose Goto Attributes.

The Test Plan Attributes screen opens.


8. Switch to tab Planning Data.

9. Choose Level Test Case for effort planning and reporting.

10. Use the Summary button to sum up the expected efforts based on the Test Plan/Test Package

setup done.




51

2.2.7 Release yo ur Test Plan

Before the testers are able to test their assigned test packages, the relevant test plan needs to bereleased. This is usually done via the Release Status Schema assigned to the test plan.The following describes how to release a test plan. For the purposes of our example, the release statusprofile ‘DEFAULTS’ is used.






6. Choose Goto Attributes.

The Test Plan Attributes screen opens.




52


8. On the General Data tab, place the cursor in the Status field.

9. Press F4 to call up the input help.

10. Select the entry RELEASED.

11. Choose the Copy pushbutton ( ) to confirm your selection.

12. Choose Save.The test plan is released and thus no longer locked for test execution.If the Workflow Active checkbox has been selected, e-mail notifications are automatically sent toassigned testers to inform them that their test packages are available and ready for testing.

If the Workflow Active checkbox has been selected, e-mail notifications are automatically sent toassigned testers to inform them that their test packages are available and ready for testing.




53

2.3 Test Execution

As soon as the tests have been planned and the test systems are available and contain adequate test data,

actual testing can start.The Test Workbench in SAP Solution Manager provides functions that enable you to perform tests, enterproblem messages, create test logs, and handle test status management as well as status reporting.The test case description provides testers with all information they need to carry out the (manual) tests.

After performing a test, testers can log and document the test results (including screenshots, if required) in atest note.The test activities are completed by setting the appropriate test status, which serves as the basis for the testcoordinator’s test reporting activities.

2.3.1 Perform a Manual Test

The Tester Worklist ensures access to both the test cases and the transactions in the system under test(managed system). It contains an overview of all test packages that have been assigned to you for testing.

As a test organizer, you are authorized to view all test packages.

The following describes how to perform a test from the tester worklist within the Test Management work

center:



3. From the navigation area on the left of the screen, choose Tester Worklist .

4. Choose the My Assigned query.

5. Click on Refresh to refresh the active query.




54

6. Highlight the desired test package in the list of test packages that are assigned to you. In the lowerpart of the screen a new table shows up containing the Test Cases assigned to the Test Cases.

Choose an appropriate Test Case from the list; hit Run Test for the Test Case you want to perform.

The Manual Test Screen opens.

7. In the new screen, the Test Case description is automatically opened on the left hand side andshows the document provided on business process structure level.






56

7. A new screen appears containing already all relevant information about the system environment liketarget systems, client and component.

8. In the Priority field, choose the dropdown box and select the appropriate entry.

9. In the Reported by field, check whether the correct business partner/name is displayed.By default, the user creating the message is automatically entered in this field.

10. If desired, make entries in the Processor , Category , and Subject fields.

11. In the Description Tex t field, enter a short description of the problem you want to report.

12. In the Details area, enter a detailed description of the error into the text box.

Basic information, such as the names of the relevant test plan, test package, and test case are alreadypre-filled on the Description tab.

13. If desired, upload a file attachment using the Attachments tab.

14. Choose Save.The message is now listed on the message tab of the appropriate Test Case.

15. When you close the Manual Test Case screen and refresh the Work Center for Test Management, thenumber of reported errors is now visible.




57

2.3.4 Create a Test Note

Test Notes are used to document the test results, thus ensuring transparency and traceability. Apart from that, in many companies an accurate and thorough documentation of test results is required forlegal reasons (e.g. in the pharmaceutical industry).Test Notes can also be used to handover data that is needed for subsequent testing activities.

The following describes how to create a test note:

16. In the Manual Test Case screen choose the button to call a new pop-up.

17. Define a document title and provide a document status.

18. Choose whether you want to use a new document to store relevant information to or copy the existingTest Case description.

19. Continue with OK and a new window appears:




58

20. Provide the relevant information in the document, save when finished and close the window.

Note: You can also add screenshots to the test note.

6. Back in the Work Center for Test Management the Test Note is now accessible.

2.4 Test Reporting

Throughout the test cycle, test coordinators monitor the test status and progress. In addition, they keep aneye on the processing status of problems that have been reported.The Test Workbench provides a wide range of hierarchical and list-based reports that help you control thetest execution status. As a test coordinator you can use these reports to track the progress of testing at alltimes – even if tests are being conducted in different locations around the world.

In addition, you can analyze the number and priority of problems that have occurred during testing.




59

Further reporting capabilities are enabled by the integration between Test Workbench and SAP NetWeaverBusiness Intelligence (BI).

Each role involved in a project (such as test coordinator, quality manager, project lead, CIO) is interested in

different pieces of information and requires a different level of granularity when it comes to data on teststatus, test progress, and error messages. A quality manager, for example, might be interested in theprogress of error message solving, whereas a project lead probably wants to know what the overall testingprogress looks like.To meet the needs of all project members, SAP Test Workbench offers a range of tools and functions thatprovide information on both aggregated and detailed level.

Test reporting capabilities in SAP Solution Manager comprise the following:

Different entry levels (Project, Solution, Test Plan)

Drill-down capabilities to access individual test cases and error messages

Status Analysis featuring both absolute values and percentages

Integration with SAP BI that allows for graphical representation of test progress etc.

The following describes the most common use cases for test reporting and explains how to use theappropriate Test Workbench functions to obtain the requested information:

2.4.1 Check Status for Current Test Phase

The Status Info System within SAP Solution Manager offers an efficient and flexible way of getting asnapshot of current test activities and related messages.To get an overview of the latest test-relevant information, proceed as follows:



23. From the navigation area on the left of the screen, choose Test Evaluation.The view that opens contains an overview of all test plans and the status of the corresponding testcases on an aggregated level. To evaluate the test plans on a more granular level, various tools areavailable, which will be explained in more detail below.

Note: The Test Evaluation area within the Test Management Work Center is the central place to accessmost of the test reporting tools. The Work Center provides a high degree of flexibility when it comes topersonalization and the definition of own queries.




60

24. In the content area, search for the desired test plan and highlight the appropriate row.If required, use the filter functionality to find your test plan.

25. Choose Goto Status Overview .

This takes you to the Status Overview – Test Organizer screen.

This view provides you with high-level status information on the results of the selected test plan and itsassociated test packages. It also indicates whether problem messages have been created for the testphase.

Recommendation: You can toggle between absolute values and percentages:From the menu bar, choose Utilities Settings Status… and select the desired radio button.

Further Options - Detailed Status A nalys is :

26. To obtain more detailed information place the mouse pointer on either the test plan (top level node) ora test package in the structure.

27. Choose the Status Analysis pushbutton ( ).This opens the Status Analysis screen for the selected test plan/test package.

The Status Analysis screen provides you with all kinds of test-related data (such as test status, result




61

documentation, availability of messages and notes, etc.) and allows you to drill down to individual testcases.

2.4.2 Check Messages for Test Plan

To obtain on overview of all messages related to your test plan/test package proceed as follows:



30. From the navigation area on the left of the screen, choose Test Evaluation.

31. In the content area, search for the desired test plan and highlight the appropriate row.If required, use the filter functionality to find your test plan.

32. Choose Goto Message Overview .This takes you to the Message Overview screen

The Message Overview screen provides you with detailed information, such as message status,priority, reporter, etc.

33. To display all details of a specific message, select the desired entry and choose the Details pushbutton ( ).

To get an overview of the latest test-relevant information, proceed as follows:

2.4.3 Create a Test Repo rt

The test report function uses an MS Word macro that allows you to comprehensively document the currentresults of a test plan. All relevant data (such as test case descriptions, test notes, etc.) are downloaded to alocal directory and then consolidated in a central document. The structure of the document is based on thebusiness process structure of the underlying project.The test report function is particularly useful for companies that have an obligation to produce supporting

documents, as the test report reflects a “frozen” status of test activities at a specific point in time. Therefore,the test report helps you meet legal requirements for test documentation.




62

To create a Test Report, proceed as follows:






6. Choose Goto Create Test Report .

7. In the Test Report Display Options dialog box, specify what pieces of information shall be included inthe report by selecting or deselecting the various checkboxes.




63

8. Choose Execute.The Download Test Report dialog box opens.

9. Confirm the message by choosing Continue.The test report document automatically opens provided that you have Microsoft Word installed on yourmachine.

10. In MS Word, make sure you have macros enabled.

11. As soon as macros are enabled, run the Macro SAP_GENERATE_TESTREPORT.




64

The complete test report is displayed. You can now save the document on your harddrive or print itand have it signed.

2.4.4 Use Test Report ing Features Based on SAP BI

You can analyze test management using the BI reporting analyses which allow you to access variousgraphic overviews and extensive filter capabilities. You also have access to the functions of the BI system.These tools are particularly useful for quality managers and test organizers.




65

2.4.4.1 Status Report

The Status Report shows an overview of the status of selected test plans including a message overview for

priority 1 – 3 messages.This report provides an efficient and flexible way to visualize the test status on a day-to-day basis.To call up the BI-based status report, proceed as follows:




4. In the content area, select the test plan for that you want to perform the status reporting.

5. Choose the Status Report pushbutton and, from the context menu, select the option Test Plans.The BI report for the current status of the selected test plan is displayed in a new window. The reportalso includes a message overview for priority 1 – 3 messages.

By default, data is displayed for the date of the last data extraction.






67

In addition, detailed information is displayed in a tabular overview at the bottom of the screen.

2.4.4.3 Messages Report

The messages report shows an overview of the number and status of test-related messages at a certaintime. By default, the data of the last data extraction is set as the filter.The messages report can be displayed for selected projects or test plans. The messages reflected in thisreport can directly being accessed throughout the table on the bottom of the screen provided.

To call up the BI-based messages report, proceed as follows:





5. Choose the Messages Report pushbutton and, from the context menu, select the option Test Plans.

2.4.4.4 Test Effort Report




68

Based on the information provided for expected test efforts, either centrally or for the single Test Case, andthe information provided for the actual test effort, either manually by the tester or automatically recorded, thetest effort report is created.

The report allows comparing the current status regarding actual and expected efforts and shows the amountof effort above or below plan. Additionally you can compare the efforts spend with the overall progress of theTest Plans in scope. This could be used as indicator to identify (un)successful testing.

To call up the BI-based effort report, proceed as follows:





10. Choose the Effort Report pushbutton and, from the context menu, select the option Test Plans.

Further Help

For further help please refer to the following links (some of the links are accessible to SAP Customers andPartners only):

SAP Standard for Test Management

o http://service.sap.com/supportstandards List of Available SAP Standards for SolutionOperations Test Management

http://service.sap.com/supportstandards






69

E2E Integration Testingo http://service.sap.com/testing

Ramp-Up Knowledge Transfer - SAP Solution Manager 7.0 - EHP1: Build, Test and Deploy withSAP Solution Manager

o http://service.sap.com/rkt-solman SAP Solution Manager 7.0 - Enhancement Package 1(EHP1) Build, Test and Deploy with SAP Solution Manager

SAP Solution Managero http://service.sap.com/solutionmanager

http://service.sap.com/testing


http://service.sap.com/rkt-solman


http://service.sap.com/solutionmanager







© 2012 SAP AG. Al l rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP

products and services mentioned herein as well as their respective

logos are trademarks or registered trademarks of SAP AG in Germanyand other countries.

Business Objects and the Business Objects l ogo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

www.sap.com