testing with solman40 v11

8/16/2019 Testing With Solman40 v11

1/27

Tes t ing w i th t he SAP So lu t i onManager

R e l eas e 400


2/27

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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

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 theUnited 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World WideWeb 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 fortechnology 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 andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specificationsmay vary.

These materials are subject to change without notice. These materials are provided by SAP AGand its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting an additionalwarranty.

Testing with the SAP Solution Manager 400 2


3/27

SAP 21.12.2005

Contents

1 Testing with the SAP Solution Manager ......................................... 5

1.1 Using the SAP Solution Manager in Projects...........................................................5

1.2

Software Tests .........................................................................................................9

1.2.1 Test case................................................................................................................10

1.2.1.1 Test case description .............................................................................................10

1.2.1.2 General recommendations for creating test cases ................................................10

2 SAP Solut ion Manager Test Support ............................................ 12

2.1 Test Strategy and Planning....................................................................................12

2.2 Test Preparation.....................................................................................................12

2.3 Test Case Types ....................................................................................................13

2.3.1

Attributes ................................................................................................................14

2.4 Test Planning .........................................................................................................16

2.5 Test Environment ...................................................................................................17

2.6 Testing....................................................................................................................17

2.7 Test Analysis..........................................................................................................18

2.7.1 Test report ..............................................................................................................19

2.7.2 Digital Signature of Test Documents and Notes ....................................................19

2.8 SAP Solution Manager Function, Sequence and Integration Test Support...........20

2.8.1 Function test with the SAP Solution Manager........................................................20

2.8.2 Sequence test with the SAP Solution Manager .....................................................20

2.8.3 Integration tests with the SAP Solution Manager...................................................22

2.8.4 Cross-component test cases..................................................................................22

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 Sequence and integration tests with several testers: Data transfer.......................22

3 Appendix ......................................................................................... 23

3.1 Naming Conventions..............................................................................................23

3.1.1

Manual test case (SAP Script) ...............................................................................23

3.1.2 External application test case ................................................................................23

3.1.3 Manual test case (SAP Solution Manager Knowledge Warehouse)......................24

3.1.4 CATT ......................................................................................................................24

3.1.5 eCATT test configurations......................................................................................24

3.1.6 eCATT test scripts..................................................................................................24

3.1.7 Test data container.................................................................................................24

3.1.8 System data container............................................................................................25

3.1.9 Test plan.................................................................................................................25

3.1.10

Test package..........................................................................................................25



4/27

SAP 21.12.2005

3.2 Further Information.................................................................................................25

3.2.1 Training ..................................................................................................................25

3.2.2 SAP Test Management Consulting........................................................................26

3.2.3 Documentation in the SAP Help Portal ..................................................................27

3.2.4

eLearning Materials................................................................................................27



5/27

SAP 21.12.2005

1 Testing with the SAP Solution Manager

Support for function, sequence and integration tests in the SAP Solution Manager.

This document gives an overview of the system and methodological support providedby the SAP Solution Manager for software tests.

1.1 Using the SAP Solut ion Manager in Projects...

The SAP Solution Manager is a new way of supporting the implementation, operationalprocessing and permanent optimization of business software solutions. It runs at thecentre of the customer solution landscape, and supports distributed systems fromthere.

The SAP Solution Manager supports process-oriented design, configuration, test and

system monitoring activities during the implementation and operational processing ofsystem landscapes of any degree of complexity.

This document provides a general overview of the support provided by the SAPSolution Manager for implementation, and then more details of the test phase. It doesnot 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



6/27

SAP 21.12.2005

The SAP Solution Manager helps you perform the following activities during yourimplementation 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-definedbusiness processes; Document business processes

• Realization: Configuration; Compare and distribute customizing; Set-up testsystem; Organize and perform tests; Create, organize and distribute eLearningcontents

The SAP Solution Manager also supports the following cross-phase functions:

• Reporting: Provides information about the project status and the progress ofactivities such as Blueprint creation, configuration and tests, in all projectphases.

• 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. Theycontain the standard SAP implementation methods, and cover the most importantaspects and phases of an SAP implementation. The roadmaps contain links toaccelerators and tools to perform the project tasks.

Business Blueprint

In the Business Blueprint, you document the business processes in your companywhich you want to use in your SAP system. You create a project structure in which therelevant business scenarios, business processes and process steps are structuredhierarchically. You can also create project documentation and assign it to scenarios,processes and process steps. Then you assign transactions to each process step, todetermine how the business processes are to run in your SAP systems.



7/27

SAP 21.12.2005

The Business Blueprint is a detailed description of your business processes andsystem requirements, which you can automatically combine into a Business Blueprintdocument. You can reuse the Business Blueprint project documentation and projectstructure during the configuration and test organization.

When you configure your business processes, the system shows you the Business

Blueprint project structure for orientation, and you can display and edit the BusinessBlueprint project documentation during the configuration.

All test plans which you create during the test organization are based on the BusinessBlueprint project structure. The transactions which you assign to process steps in theBusiness Blueprint are put in generated test plans as function tests, to test thetransactions.

When you create the Business Blueprint, you choose preconfigured businessprocesses which you want to implement. The appropriate Business Process Repositorycontents for the selected scope, is provided.

The Business Process Repository is a collection of reusable predefined businessprocess information. It contains:

• Scenario documentation

• Transaction assignments

• IMG assignments

• Configuration guide

• Preconfigured processes in BC Sets

• Predefined test cases

Realization

In this phase, the process requirements specified in the Business Blueprint phase, are

configured in the system. The SAP Solution Manager supports process, rather thancomponent-oriented configuration and testing.



8/27

SAP 21.12.2005

The SAP Solution Manager is a central platform, from which you can go to the differentsystem components, for configuration and test purposes. If your structure containsBusiness Process Repository objects, transactions, BC Sets and test cases mayalready be assigned to them. If you create structures without Business ObjectRepository 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 initialconfigurations in the realization phase.

The first step in test organization is the creation of a test plan. In the Business Blueprintphase, you have created a project structure of business scenarios, processes andprocess steps. Then you have assigned transactions and test cases to the processsteps. The system ofers you this project structure as the basis for your test plan. It alsooffers you the manual and automated test cases which you have already assigned toprocesses or process steps, to select for your test plan.

Going live

When you have completed an implementation project, the SAP Solution Managerprovides a simple way of transferring all information collected during theimplementation, which is required for operational processing, into operationalprocessing.

To make contents from the implementation phase usable for operational processing, itis first put in one or more solutions in the Solution Directory.

Other use scenarios, such as system monitoring, business process monitoring, centralsystem administration, service level reporting and SAP EarlyWatch Alert, can then beconfigured based on this information.



9/27

SAP 21.12.2005

Test plans can also be generated for solutions in the Solution Directory. When youdefined your solution, you created a solution structure from business scenarios,processes and process steps, or copied one from an implementation project. Then youassigned transactions and test cases to the process steps. The system offers you thissolution structure as the basis for your test plan. It also offers you the manual andautomatic test cases which you assigned to processes or process steps, or copied fromthe implementation project, for selection for your test plan.

1.2 Software Tests

Software tests are a methodical procedure to try to ensure system quality by findingerrors.

The main focus of the test activities is the correct performance of previously definedindividual functions (module/unit test), and the correct interaction of individual functionswhich are related within an overall process (integration test). Performance tests arealso required, to test the capacity of a system to perform its tasks. These can be load

tests, which test system response to a large number of users at the same time, orstress tests which, for example, test the behavior when generating bulk data.

The test scope should be derived from the risk, error frequency, which in turn dependson 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 areperformed manually, and the test results are recorded manually. Only test organizationand administration utilities are used.

Automatic

In automatic tests, after the creation of the test cases, all test activities are performedby test automation tools, such as eCATT (Extended Computer Aided Test Tool). In this



10/27

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 anupgrade, where unchanged functions must quickly run as before. Automatic tests canalso be used in rollout projects, in which a centrally-defined template is implemented invarious rollout locations. The SAP Solution Manager template functionality supportsthis project type, and considerably accelerates the test preparation and performance, inthe rollout locations, with test cases integrated into the template.

1.2.1 Test case

A test case is the smallest test entity. The components of a manual test case in an SAPsystem are:

• Object name

• Attributes

• Test case description

Automatic test cases have other attributes, which are not described here. For further

information about eCATT, see the online documentation in the SAP Help Portal, whoseURL you can find at the end of this document.

1.2.1.1 Test case descr iption

The test case description is mainly for testers, whether manual testers or testautomation experts, but it is also of interest for software developers, to help them tounderstand the errors discovered by testers. They are also important for reviewers andauditors, because they document the test scope.

The scope and level of detail of a test case depends on the experience of the targetgroup, but also requirements of norms or legal requirements.

A test description should contain:• Description

Rough description of the test activities to be performed.• Preparation/Prerequisites

Details of all preparation required, and prerequisites of the test.

• ExecutionDetailed test procedure.

• Check/Expected ResultDetails of the expected result of the test, or checks to be performed.

• Notes Additional notes which could be of help to the tester when performing the test.

The SAP Solution Manager contains document templates for manual test cases, whichalready have this basic structure. You can replace them with your own templates.

1.2.1.2 General recommendations for creating test cases

You should use consistent naming conventions and structures to create the test cases.The consistent structure of manual test cases is ensured in the SAP Solution Managerby a document template. There is a proposed test object (test case, test plan, testpackage, etc.) naming convention, at the end of the document. Project-specificguidelines must be made for the naming convention within test cases.

Test cases should also be created using the 4 eyes principal, i.e. the test case creator

and the tester should not be the same person.



11/27

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 savedin the SAP Solution Manager, at the associated Business Process Hierarchy nodes, inthe Project Documentation or General Documentation tabs, which avoids the test casecreator having to search for basic materials. Everything is available centrally, in onesystem. 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) andexternal application test cases) must be saved centrally in the SAP Solution Manager,or in another system, or decentrally in component systems. Saving them centrally inthe SAP Solution Manager is most appropriate for the central test managementsystem.



12/27

SAP 21.12.2005

2 SAP Solution Manager Test Support

2.1 Test Strategy and Planning

Various roadmaps support methodical procedures in SAP Solution Manager projects.Roadmaps give the project teams detailed, step-by-step guidelines about projectactivities to be performed, and thus facilite the successful carrying out of the tasks tobe performed. For example, item 1.2.2.3 of the Implementation Roadmap containsgeneral information about defining a test strategy. Accelerator documents, such as„Testing Strategy White Paper“ (item 3.6.4 of the Implementation Roadmap) providefurther information, which can help you to start a project-specific procedure. Testactivities to be performed are frequently mentioned at other appropriate places in theImplementation Roadmap.

2.2 Test Preparation

Test cases are created, or existing ones are assigned to the project, along the processstructure, to scenarios, processes or process steps, depending on the granularity, inthe Test Cases tab, during the configuration phase (SAP Solution Manager:Configuration, transaction SOLAR02). Material created outside the Solution Managercan also be uploaded.

You must decide, at the latest during test preparation (although even better in theproject definition), whether the test cases are to be saved centrally in the SAP SolutionManager, or in the component systems. You make this setting in the SystemLandscape B Central Objects tab in the SAP Solution Manager project administration(transaction SOLAR_PROJECT_ADMIN). If a central test system is to be used, testcases (eCATT test configuration, manual test cases (SAPscript) and externalapplications) are stored centrally in the SAP Solution Manager System. Manual testcases which are stored in the Knowlege Warehouse, can only be saved centrally in theSAP Solution Manager system. You also do not have to transport the test cases intothe quality assurance landscape component system with this procedure. The testcases are created in the development system landscape, in the configuration phase(transaction SOLAR02), but the test activities are performed in the quality assurancelandscape, so the testers would have no access to the required test cases.



13/27

SAP 21.12.2005

2.3 Test Case Types

The following types of test cases can be used in the SAP Solution Manager:

Manual test case

Test case to give test instructions for manual testing. The test case can be created withMS Office programs, and is saved in the SAP Solution Manager KnowledgeWarehouse. This ensures detailed version management of the documents, andcomfortable processing by the MS Office integration. You can create a new document,copy an existing document, or link to an existing document. You can also put a URL inthe Knowledge Warehouse, instead of a document. The length of the URL is restrictedto 250 characters.

Manual test case (SAPscript)

The test case is created in the SAPscript editor, and in contrast to the previous testcase, this type is saved in the SAP system.

External application test cases

Test case to include files or URLs (URL is restricted to 128 characters), which areloaded onto the local presentation host when they run, and can be processed there byexternal programs. Test cases of this type also save test data in the format of externaltest tools. This test case type is a subtype of Manual test case (SAPscript).

eCATT test configurations

The test configurations are maintained in the test configuration editor. A testconfiguration contains a reference to a test script which contains the test logic. It can,but need not, contain a reference to a system data container (contains informationabout the systems to be tested), and references to several test data containers. Forfurther information about eCATT, see the SAP help portal, the direct link to the eCATT

documentation is at the end of the document.CATT scripts



14/27

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 areabove all useful for function tests.

2.3.1 AttributesThe 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 caseselection criteria.

The test case attributes of manual test cases (SAPscript) and external application testcases 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 furtherinformation about eCATT, and the direct link to the eCATT documentation is in theappendix):

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 assignedto this field. If the creator is not the contact person for this test case, the entry can bechanged.

Release: If the test case is only for a particular release, you can enter a validity rangehere.

Component: Name of the component from the SAP Solution Manager applicationhierarchy. If the test cases are stored centrally in the Solution Manager, the local SAPSolution 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 testcases are stored centrally in the SAP Solution Manager, you can choose a localpackage (e.g. $TMP), because the test cases do not need to be transported. You canchange the package later.

Addi tional 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 functionmodules (type F). Enter the name of the test object in the Name field. If the test testsseveral test objects, you can specify several test objects. This field is fordocumentation only, you cannot call the test object.

Assigning t ransactions



15/27

SAP 21.12.2005

You can assign a transaction to each test case assigned to the project, in the TestCases tab, in the configuration phase (transaction SOLAR02), in the SAP SolutionManager. 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 RFCconnection. Alternatively, you can access the transactions directly when the test plan isgenerated, without assigning it to a test case first, but in this case, the testers find thetransactions in their worklist without a test description, so this procedure is only suitablein exceptional cases.

Restrictions

Language: Flag for a language-dependent test case. Enter the language for the test ortest module, in the associated field. If the test case of type CATT is performed inanother 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 isperformed.

Test Environment: You can specify here, the customizing with which the test can beperformed, if your test case is customizing-dependent.

Database: You can specify here, the database for which the test case was created, ifyour test case is database-dependent.

Platform: You can specify the platform for which the test case was created, forplatform-dependent test cases.

Frontend: You can specify the frontend for which the test case was created, forfrontend-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.



16/27


17/27

SAP 21.12.2005

Test plans and test packages can be designed so that applications, interfaces and thedata used by the applications can be tested.

2.5 Test Environment At this point at the latest, real systems for performing quality assurance measures(SAP Solution Manager system landscape, transaction SMSY; tab SystemLandscape/Systems, system roles: quality assurance), must be assigned to the logicalsystems. The testers access the component system centrally, and perform the testactivities from the SAP Solution Manager.

2.6 Testing

The testers verify the business processes by working through the worklists assigned tothem (Tester Worklist, transaction STWB_WORK). Errors and their causes can belogged in the integrated problem message system, as well as in the status feedback. Amessage template can be put in the SAP Solution Manager, for the messages createdby testers (see central Test Workbench settings, transaction STWB_SET). It specifiesthe basic structure of the message contents, which makes it easier for the tester toprovide all the information required to solve the problem. Information about where (testplan, test package, test case) the error message was issued is also generated into themessage. The messages are then further processed in the SAP Solution ManagerService Desk.



18/27

SAP 21.12.2005

After testing, each tester can record the results of the test in detail, by writing test notesfor each test case. These notes can be written in SAPscript or as MS Officedocuments, in the SAP Solution Manager Knowledge Warehouse.

2.7 Test Analysis

The SAP Solution Manager contains various analyses to see and accept test results:

You can analyse the status of all test plans assigned to a project, in the SAP SolutionManager Project Analysis (transaction SOLAR_EVAL: Test→ Status Analysis TestPlans). You go to the Test Workbench status info system, where you can analyze alltest plans assigned to the project, in detail. These status results can be exported forfurther processing.

Alternatively, you can monitor the progress of tests in your project, process-specifically,and test plan-independently, with the analysis Project Status Analyses (transaction

SOLAR_EVAL Test→ Project Status Analyses). You see in which test plan and testpackage a test case is used, and whether a test case has not yet been used in a testplan or test package. These status results can also be exported for further processing.

The Test Workbench status info system (transaction STWB_INFO), can also be usedto analyse the test progress. You can create a list of relevant test plan results andinformation, such as test case descriptions, notes, messages, and the status changehistory, to accept the test (view Hierarchy List, menu: Settings→ AdditionalInformation). You cannot, however, display information from Solution ManagerKnowledge Warehouse documents, in this view. Use the test report to put thisinformation in a document.



19/27

SAP 21.12.2005

2.7.1 Test report

To document the scope of a test plan in detail, before a test, or its results, you cangenerate a test report, in the test plan management (test plan: transaction STWB_2,menu: Goto B Test Report; test package: transaction STWB_2, key „Test Package“,menu: Goto B Test Report). This report is created automatically by the system, and

contains all information about the test plan, such as test plan attributes, informationabout the systems used, overview of the test packages, assignment of test packages totesters, test plan structure, test case descriptions, and details of the test packages,such as test case status, test case status change history, test notes, and messages.

2.7.2 Digital Signature of Test Documents and Notes

The authenticity of test cases of type test document, and of test notes, in the SAPSolution Manager Knowledge Warehouse, can be guaranteed by a digital signature.The digital signature also protects documents from changes.

To be able to use this function, you must have performed all configuration steps in thepath SAP Solution Manager B Scenario-Specific Settings B Implementation B Document Management B Digital Signature and Document Status, in the IMG.

The following schema gives a brief overview of the steps to be performed and theschematic context.

You can, for example, specify a release procedure for test notes in this way. Thisrelease 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, toconfirm its authenticity. When it has been signed, the document is locked againstfurther changes. A quality manager can then give the document final approval with hissignature. When he has done so, the document is given the status „Approved“, and is



20/27

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 TestDocument.

2.8 SAP Solut ion Manager Function, Sequence andIntegration Test Support

2.8.1 Function test with the SAP Solution Manager

You can prepare a function test in the SAP Solution Manager, with the transactionSOLAR02 (Configuration). You can start and check all transactions in a businessscenario, by processing all transactions in the Transactions tab. You can also createand perform test cases for function tests, in the Test Cases tab. You should use thestandard Test Workbench functionality, and create test plans and test packages, todocument the function tests completely.

2.8.2 Sequence test with the SAP Solution Manager

The SAP Solution Manager allows you to create process-oriented test plans. Thescenario structures which were created for Business Blueprint and configuration, in thetransaction SOLAR01, are reused to create test plans with the transaction STWB_2.You can copy all transactions and test cases (SOLAR02) assigned to the structure, intotest plans, as proposals. This supports sequence tests.

Sequence tests can be manual or automatic. An automatic sequence test, based onCATT or eCATT technology, is a CATT procedure or an eCATT test configuration,



21/27

SAP 21.12.2005

which comprises modules which test individual transactions automatically. Data ispassed from one module to the next to create a sequence test:

CATTs and eCATTs should be designed to test a business process, or at least ,important steps in it. You can save these test cases at process level, in the transactionSOLAR02.

Depending on the procedure, the project could use automatic and manual test cases,or only manual test cases. This is a question of principle which must be decided beforethe start of the project, and depends partly on the reuse of test cases. Experiencesuggests that automatic test cases are justified if a test case is used more than aboutfive times. After this point, the time saved by running the automatic test case is usuallygreater than the effort required to create and parameterize the automatic test case.

A manual sequence test is created, like function tests, in SOLAR02: the integration teststeps are manual test cases, and are assigned to the process steps. A test plan is thengenerated on this basis, in the transaction STWB_2. For a sequence test, you should,as a guideline, create one test plan per typical end user (e.g. buyer), component andcycle (baseline, cycle 1, ...) (example: a test plan for cash purchase – baseline –

buyer). This test plan can usually be put in test package, and assigned to a tester.To create variations for sequence tests with various data, create generic test cases atfunction level, assign them at process step level, in SOLAR02, and then create ahigher-level test case at process level, in STWB_2, whose test case descriptioncontains the data for a variation of the sequence test. The generic test cases atfunction level and a higher-level test case with data are then combined into a testpackage and tested, in STWB_2.

In this case, the testers can record the results in individual tester notes. If the results ofsequence test are to be passed from one tester to the next, this can be done by usingan external application test case. The test case contains a URL to a document on acentral server, to which all testers participating in the test must have access. The

testers can exchange data by putting information in this document.



22/27

SAP 21.12.2005

Sequence tests can be manual or automatic, or a combination of manual andautomatic test cases. The tester must ensure that he uses the parameters fromautomatic tests in manual tests, and vice versa.

2.8.3 Integration tests with the SAP Solut ion Manager

As the SAP Solution Manager supports both process-oriented testing and testingacross several SAP components, the SAP Solution Manager test organization currentlyprovides the best support for integration tests. Integration tests are similar to sequencetests, but their test plans include several end users and several SAP components. TheSAP Solution Manager functionality allows customer reports and transactions andexternal systems (called by URL) to be included, as well as SAP transactions.

Usually, two integration tests are performed in the ASAP methodology:

• Integration test 1 with only SAP components

• Integration test 2 with customer reports and transactions, and external systems

The technical and organizational considerations for the sequence test also apply here.

2.8.4 Cross-component test cases

From SAP Solution Manager Release 3.10 you can define a central system as therepository for manual test cases, eCATT test configurations, and external applicationtest cases. This supports cross-component tests, because all test materials are in onecentral place, and not distributed across the system landscape.

2.8.5 Existing restr ictions in the use of the Test Workbench inthe SAP Solut ion Manager, and work-arounds

2.8.5.1 Sequence and integration tests w ith several testers: Data transfer

These test packages are tested either by one tester, or by several. In this case, the testpackage should be assigned to all these testers, and which tester performs which testis determined organizationally. The test coordinator must determine how and when onetester passes to the next, in a sequence test. The data (input parameters used, outputparameters received, which are used in the next transactions) can be passed in testcase notes, which is also useful for subsequent tracing of the test. Alternatively, datacan be transferred in an external application test case (or KW test case), which cancontain the URL of a document in a central server, which contains all the input andoutput parameters used by all the testers of the process.



23/27

SAP 21.12.2005

3 Appendix

3.1 Naming Conventions

Test management is a very complex process, often involving countless test plans forthe various test phases, such as unit test or integration test. You must managehundreds or even thousands of manual and automatic test cases, possibly indistributed system landscapes. This is why you need professional test managementwith an unambiguous and detailed naming convention.

In the SAP Solution Manager, the project replaces the test catalog, familiar from theSAP Basis, and contains all test cases required for the project, which were createdduring the configuration phase.

An example naming convention for the test phase is presented below. It allows you toput all test contents (as well as the organization criterion project) in the SAP SolutionManager, in a structured way.

3.1.1 Manual test case (SAP Script)

Naming convention: Z_M _type_(NR_)(TA_)descript ion

Z: Customer namespaceM: Manual test caseType: Test case type „T“ for transaction or „P“ for process(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.

3.1.2 External application test case

Naming convention: Z_EX _type_(NR_)(TA_)descript ion

Z: Customer namespaceEX: External application test caseType: Test case type „T“ for transaction or „P“ for process(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.



24/27

SAP 21.12.2005

3.1.3 Manual test case (SAP Solution Manager KnowledgeWarehouse)

A technical key is generated for this test case when it is created in the KnowledgeWarehouse, so no naming convention is required here, but there should be a

meaningful description of the test case.

3.1.4 CATT

A CATT script (C) is performed by the Computer Aided Test Tool.

Naming convention: Z_C _type_(NR_)TA_descript ion

Z: Customer namespaceC: Automatic test case of type CATTType: 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.

3.1.5 eCATT test configurations

An eCATT test configuration (ETC) is performed by the Extended Computer Aided TestTool, and comprises a test data container (TDC), a system data container (SDC) and atest script (ETS).

Naming convention: Z_ETC _type_(NR_)(TA_)descript ion

Z: Customer namespaceETC: eCATT test configuration

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.

3.1.6 eCATT test scripts

Give the main test script of an eCATT test configuration the name of the testconfiguration.

For other test scripts, use the following naming convention.

Naming convention: Z_ETS _type_TA_descr iption

Z: Customer namespaceETS: eCATT test scriptType: Test case type, e.g. UNI (unit test), INT (integration test), etc.(TA_): Transaction to be tested (e.g. ME21) (optional)Description: Concise description of the aim of the test case.

3.1.7 Test data container

Naming convention: Z_TDC _type_descript ion

Z: Customer namespaceTDC: eCATT test data containerType: Test case type, e.g. UNI (unit test), INT (integration test), etc.

Description: Concise description of the aim of the test data container.



25/27

SAP 21.12.2005

3.1.8 System data container

Naming convention: Z_SDC _type_descript ion

Z: Customer namespaceSDC: eCATT system data container

Type: Test case type, e.g. UNI (unit test), INT (integration test), etc.Description: Concise description of the use of the system data container.

3.1.9 Test plan

A test plan contains all test cases (manual test cases, CATTs and eCATT testconfigurations), which are required for a specific test phase.

Naming convention: Z_TPL _type_component_descript ion_YYYY.MM.DD

Z: Customer namespaceTPL: Test planType: Test plan type e.g. UNI (unit test), INT (integration test), REG (regression test),LOD (load test), STR (stress test), etc.

Component: The first level of the application component hierarchy (ACH). You can alsospecify down to subcomponent level, e.g. HR_PA.Description: Concise description of the use of the test plan.YYYY.MM.DD: Test plan creation date

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_)descr ip tion

Z: Customer namespaceTPK: 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.

3.2 Further Information

3.2.1 Training

SAP University training: CA611 Test Management with the New eCATT and theTest Workbench

Course contents:

• Test Workbench overview

• Put test cases in test projects, and manage them with the Test Workbench (statusmonitoring and Issue Management)

• Introduction to automatic testing of SAP systems

• Set-up system landscape for eCATT

• eCATT environment (scripts and script language)

• Testing applications (what? how?)



26/27


27/27

SAP 21.12.2005

• Functional tests

• Load and stress tests

• Solution Manager use cases

• Project-specific service packages

For further information about the services, see http://service.sap.com/tmc → Services,in the SAP Service Marketplace

3.2.3 Documentation in the SAP Help Portal

SAP Solution Manager 4.0:

German:

http://help.sap.com/saphelp_sm40/helpdata/de/ae/64c33af662c514e10000000a114084/frameset.htm

English:

http://help.sap.com/saphelp_sm40/helpdata/en/ae/64c33af662c514e10000000a114084/frameset.htm

The Test Workbench in the R/3 System:

German:

http://help.sap.com/saphelp_nw04s/helpdata/de/3c/aba1d2413911d1893d0000e8323c4f/frameset.htm

English:

http://help.sap.com/saphelp_nw04s/helpdata/en/3c/aba1d2413911d1893d0000e8323c4f/frameset.htm

eCATT: Extended Computer Aided Test Tool:

German:

http://help.sap.com/saphelp_nw04s/helpdata/de/1b/e81c3b84e65e7be10000000a1140

2f/frameset.htmEnglish:

http://help.sap.com/saphelp_nw04s/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htm

3.2.4 eLearning Materials

There are SAP Solution Manager eLearning materials in the SAP Service Marketplaceunder http://service.sap.com/rkt-solman

http://service.sap.com/tmchttp://help.sap.com/saphelp_sm40/helpdata/de/ae/64c33af662c514e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_sm40/helpdata/de/ae/64c33af662c514e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_sm40/helpdata/en/ae/64c33af662c514e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_sm40/helpdata/en/ae/64c33af662c514e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://service.sap.com/rkt-solmanhttp://service.sap.com/rkt-solmanhttp://help.sap.com/saphelp_nw04s/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/1b/e81c3b84e65e7be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/en/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_nw04s/helpdata/de/3c/aba1d2413911d1893d0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_sm40/helpdata/en/ae/64c33af662c514e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_sm40/helpdata/en/ae/64c33af662c514e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_sm40/helpdata/de/ae/64c33af662c514e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_sm40/helpdata/de/ae/64c33af662c514e10000000a114084/frameset.htmhttp://service.sap.com/tmc