Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Manager
Release 400
SAP
21.12.2005
Copyright
Copyright 2005 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,
OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere,
Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the
United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide
Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These materials are provided by SAP AG
and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
400
SAP
21.12.2005
Contents
1
1.1
1.2
1.2.1
Test case................................................................................................................10
1.2.1.1
1.2.1.2
2.1
2.2
Test Preparation.....................................................................................................12
2.3
2.3.1
Attributes ................................................................................................................14
2.4
2.5
2.6
Testing....................................................................................................................17
2.7
2.7.1
2.7.2
2.8
2.8.1
2.8.2
2.8.3
2.8.4
2.8.5
Existing restrictions in the use of the Test Workbench in the SAP Solution Manager,
and work-arounds...................................................................................................22
2.8.5.1
Appendix ......................................................................................... 23
3.1
3.1.1
3.1.2
3.1.3
3.1.4
CATT ......................................................................................................................24
3.1.5
3.1.6
3.1.7
3.1.8
3.1.9
Test plan.................................................................................................................25
3.1.10
Test package..........................................................................................................25
400
SAP
21.12.2005
3.2
Further Information.................................................................................................25
3.2.1
Training ..................................................................................................................25
3.2.2
3.2.3
3.2.4
eLearning Materials................................................................................................27
400
SAP
21.12.2005
The SAP Solution Manager is a new way of supporting the implementation, operational
processing and permanent optimization of business software solutions. It runs at the
centre of the customer solution landscape, and supports distributed systems from
there.
The SAP Solution Manager supports process-oriented design, configuration, test and
system monitoring activities during the implementation and operational processing of
system landscapes of any degree of complexity.
This document provides a general overview of the support provided by the SAP
Solution Manager for implementation, and then more details of the test phase. It does
not describe support for operational processing.
The SAP Solution Manager supports you in all phases of your implementation project.
The phases are based on the five phases of the Implementation Roadmap:
Project Preparation
Business Blueprint
Realization
Production Preparation
Go Live & Support
400
SAP
21.12.2005
The SAP Solution Manager helps you perform the following activities during your
implementation project:
Project Preparation: Define project and system landscape
Business Blueprint: Determine customer-specific solution, based on predefined
scenarios from the Business Process Repository, and customer-defined
business processes; Document business processes
Realization: Configuration; Compare and distribute customizing; Set-up test
system; Organize and perform tests; Create, organize and distribute eLearning
contents
The SAP Solution Manager also supports the following cross-phase functions:
Reporting: Provides information about the project status and the progress of
activities such as Blueprint creation, configuration and tests, in all project
phases.
Roadmaps: Lead the implementation team step by step through the project;
they contain methods and supporting accelerators.
The SAP Solution Manager is delivered with the most recent available roadmaps. They
contain the standard SAP implementation methods, and cover the most important
aspects and phases of an SAP implementation. The roadmaps contain links to
accelerators and tools to perform the project tasks.
Business Blueprint
In the Business Blueprint, you document the business processes in your company
which you want to use in your SAP system. You create a project structure in which the
relevant business scenarios, business processes and process steps are structured
hierarchically. You can also create project documentation and assign it to scenarios,
processes and process steps. Then you assign transactions to each process step, to
determine how the business processes are to run in your SAP systems.
Testing with the SAP Solution Manager
400
SAP
21.12.2005
400
SAP
21.12.2005
The SAP Solution Manager is a central platform, from which you can go to the different
system components, for configuration and test purposes. If your structure contains
Business Process Repository objects, transactions, BC Sets and test cases may
already be assigned to them. If you create structures without Business Object
Repository objects, you can make the following assignments yourself:
Transactions in the Business Blueprint transaction (SOLAR01)
BC Sets, IMG objects and test cases, in the Configuration transaction
(SOLAR02)
You organize tests when you have created a Business Blueprint and have made initial
configurations in the realization phase.
The first step in test organization is the creation of a test plan. In the Business Blueprint
phase, you have created a project structure of business scenarios, processes and
process steps. Then you have assigned transactions and test cases to the process
steps. The system ofers you this project structure as the basis for your test plan. It also
offers you the manual and automated test cases which you have already assigned to
processes or process steps, to select for your test plan.
Going live
When you have completed an implementation project, the SAP Solution Manager
provides a simple way of transferring all information collected during the
implementation, which is required for operational processing, into operational
processing.
To make contents from the implementation phase usable for operational processing, it
is first put in one or more solutions in the Solution Directory.
Other use scenarios, such as system monitoring, business process monitoring, central
system administration, service level reporting and SAP EarlyWatch Alert, can then be
configured based on this information.
400
SAP
21.12.2005
Test plans can also be generated for solutions in the Solution Directory. When you
defined your solution, you created a solution structure from business scenarios,
processes and process steps, or copied one from an implementation project. Then you
assigned transactions and test cases to the process steps. The system offers you this
solution structure as the basis for your test plan. It also offers you the manual and
automatic test cases which you assigned to processes or process steps, or copied from
the implementation project, for selection for your test plan.
The test scope should be derived from the risk, error frequency, which in turn depends
on how often functions are used, and the overall scope of the project.
There are two software test procedures:
Manual
In manual tests, after the creation of the test case descriptions, all test activities are
performed manually, and the test results are recorded manually. Only test organization
and administration utilities are used.
Automatic
In automatic tests, after the creation of the test cases, all test activities are performed
by test automation tools, such as eCATT (Extended Computer Aided Test Tool). In this
Testing with the SAP Solution Manager
400
SAP
21.12.2005
case, the test results are recorded automatically. Automatic testing is especially useful,
for example, for tests after importing Support Packages (regression tests) or after an
upgrade, where unchanged functions must quickly run as before. Automatic tests can
also be used in rollout projects, in which a centrally-defined template is implemented in
various rollout locations. The SAP Solution Manager template functionality supports
this project type, and considerably accelerates the test preparation and performance, in
the rollout locations, with test cases integrated into the template.
400
10
SAP
21.12.2005
Test cases can be based on concept papers, process descriptions, training materials,
etc. from the Business Blueprint or configuration phases. These documents are saved
in the SAP Solution Manager, at the associated Business Process Hierarchy nodes, in
the Project Documentation or General Documentation tabs, which avoids the test case
creator having to search for basic materials. Everything is available centrally, in one
system. The test cases created are also saved centrally in the SAP Solution Manager,
in the Test Cases tab at the corresponding process structure nodes.
In the SAP Solution Manager project administration, you can specify for each project,
whether test cases (eCATT test configurations, manual test cases (SAPscript) and
external application test cases) must be saved centrally in the SAP Solution Manager,
or in another system, or decentrally in component systems. Saving them centrally in
the SAP Solution Manager is most appropriate for the central test management
system.
400
11
SAP
21.12.2005
400
12
SAP
21.12.2005
400
13
SAP
21.12.2005
Automatic test case to test R/3 transactions, created by the Computer Aided Test Tool
(CATT). The R/3 system can run automatic test cases without user dialog. They are
above all useful for function tests.
2.3.1 Attributes
The test case attributes contain both important organizational (e.g. tested components)
and technical information (e.g. test case type). The attributes can be used as test case
selection criteria.
The test case attributes of manual test cases (SAPscript) and external application test
cases are classified in four groups (the attributes of eCATT test configurations and
CATT scripts are not discussed in this document. The SAP help portal contains further
information about eCATT, and the direct link to the eCATT documentation is in the
appendix):
General data
Test case: Name of the current test case.
Title: A short description of the test case.
Type: Test case type
Person Responsible: The name of the creator of the test case is automatically assigned
to this field. If the creator is not the contact person for this test case, the entry can be
changed.
Release: If the test case is only for a particular release, you can enter a validity range
here.
Component: Name of the component from the SAP Solution Manager application
hierarchy. If the test cases are stored centrally in the Solution Manager, the local SAP
Solution Manager System application hierarchy is available to structure them.
Package: When you save, you are prompted for a package, in a dialog box. If the test
cases are stored centrally in the SAP Solution Manager, you can choose a local
package (e.g. $TMP), because the test cases do not need to be transported. You can
change the package later.
Additional data
Duration: How long the test case will take.
Priority: Test case priority
Test Objects: Test objects can be transactions (type T), reports (type R) or function
modules (type F). Enter the name of the test object in the Name field. If the test tests
several test objects, you can specify several test objects. This field is for
documentation only, you cannot call the test object.
Assigning transactions
400
14
SAP
21.12.2005
You can assign a transaction to each test case assigned to the project, in the Test
Cases tab, in the configuration phase (transaction SOLAR02), in the SAP Solution
Manager. You can select from the structure element transactions in the Transactions
tab. In this case, the testers can start the transaction directly from their test package,
and logon directly in the satellite system in the quality assurance landscape, by RFC
connection. Alternatively, you can access the transactions directly when the test plan is
generated, without assigning it to a test case first, but in this case, the testers find the
transactions in their worklist without a test description, so this procedure is only suitable
in exceptional cases.
Restrictions
Language: Flag for a language-dependent test case. Enter the language for the test or
test module, in the associated field. If the test case of type CATT is performed in
another language, the test case is logged as with errors, and the test case is cancelled.
Country: Flag for country-dependent test cases. Enter the country for the test or test
module, in the associated field. This flag is not checked when the test case is
performed.
Test Environment: You can specify here, the customizing with which the test can be
performed, if your test case is customizing-dependent.
Database: You can specify here, the database for which the test case was created, if
your test case is database-dependent.
Platform: You can specify the platform for which the test case was created, for
platform-dependent test cases.
Frontend: You can specify the frontend for which the test case was created, for
frontend-dependent test cases.
Use as: You can specify the areas in which the test case is to be used, in this group.
Status: The status is automatically set when you save (active or inactive).
Release: You can specify information about the release status here.
400
15
SAP
21.12.2005
Search terms/Keywords
Search terms/keywords can be assigned to the test case. If they are manual test cases
in the SAP Solution Manager Knowledge Warehouse, the keywords must first be
defined in the project administration. Define and assign identical keywords for the test
cases in the Web Application Server. These search terms can be used in the test plan
generation, to collect the test cases required for a test phase, efficiently and simply,
and to generate test plans. You can assign up to 10 search terms to a test case in the
SAP system basis.
400
16
SAP
21.12.2005
Test plans and test packages can be designed so that applications, interfaces and the
data used by the applications can be tested.
2.6 Testing
The testers verify the business processes by working through the worklists assigned to
them (Tester Worklist, transaction STWB_WORK). Errors and their causes can be
logged in the integrated problem message system, as well as in the status feedback. A
message template can be put in the SAP Solution Manager, for the messages created
by testers (see central Test Workbench settings, transaction STWB_SET). It specifies
the basic structure of the message contents, which makes it easier for the tester to
provide all the information required to solve the problem. Information about where (test
plan, test package, test case) the error message was issued is also generated into the
message. The messages are then further processed in the SAP Solution Manager
Service Desk.
400
17
SAP
21.12.2005
After testing, each tester can record the results of the test in detail, by writing test notes
for each test case. These notes can be written in SAPscript or as MS Office
documents, in the SAP Solution Manager Knowledge Warehouse.
400
18
SAP
21.12.2005
You can, for example, specify a release procedure for test notes in this way. This
release procedure is illustrated schematically in the following graphic. A tester edits a
Test Note document and gives it the status To be Approved, when he is finished.
When he saves the new status value, the tester is prompted to sign the document, to
confirm its authenticity. When it has been signed, the document is locked against
further changes. A quality manager can then give the document final approval with his
signature. When he has done so, the document is given the status Approved, and is
Testing with the SAP Solution Manager
400
19
SAP
21.12.2005
still locked against changes. The document can only be edited again after it has been
Unlocked, which requires special authorization.
You can also set-up a similar release procedure for the manual test cases of type Test
Document.
400
20
SAP
21.12.2005
400
21
SAP
21.12.2005
400
22
SAP
21.12.2005
3 Appendix
3.1 Naming Conventions
Test management is a very complex process, often involving countless test plans for
the various test phases, such as unit test or integration test. You must manage
hundreds or even thousands of manual and automatic test cases, possibly in
distributed system landscapes. This is why you need professional test management
with an unambiguous and detailed naming convention.
In the SAP Solution Manager, the project replaces the test catalog, familiar from the
SAP Basis, and contains all test cases required for the project, which were created
during the configuration phase.
An example naming convention for the test phase is presented below. It allows you to
put all test contents (as well as the organization criterion project) in the SAP Solution
Manager, in a structured way.
400
23
SAP
21.12.2005
3.1.4 CATT
A CATT script (C) is performed by the Computer Aided Test Tool.
Naming convention: Z_C_type_(NR_)TA_description
Z: Customer namespace
C: Automatic test case of type CATT
Type: Test case type, e.g. UNI (unit test), INT (integration test), etc.
(NR_): Sequence number for integration tests (optional).
(TA_): Transaction to be tested (e.g. ME21) (optional)
Description: Concise description of the aim of the test case.
400
24
SAP
21.12.2005
3.1.10
Test package
A test package is based on a test plan, and contains all test cases intended for a tester.
Naming convention: Z_TPK_type_(NR_)description
Z: Customer namespace
TPK: Test package
Type: Test plan type, e.g. UNI (unit test), INT (integration test), REG (regression test),
LOD (load test), STR (stress test), etc.
Description: Concise description of the use of the test package.
(NR): Optional sequencing criterion number, in sequence tests.
Put test cases in test projects, and manage them with the Test Workbench (status
monitoring and Issue Management)
400
25
SAP
21.12.2005
Overview of the most important SAP Solution Manager concepts and components
Complete configuration and documentation activities with the SAP Solution Manager as
the central platform of all component systems
Supporting ongoing management of the production environment with the SAP Solution
Manager
SAP University training: USMF50 SAP Solution Manager Support Desk Functions
Course contents:
Customizing the SAP Solution Manager system for the Service Desk function, and the
Issue and Problem Management processes
Solution database
Master data
Service contracts
Enterprise Intelligence
Interaction Center
Monitoring
400
26
SAP
Functional tests
21.12.2005
400
27