Presentation is loading. Please wait.

Presentation is loading. Please wait.

ECATT VSDK 3.0. SAP AG 2005, Title of Presentation / Speaker Name / 2 Target Group and Prerequisites Target Group Implementation and integration teams.

Similar presentations


Presentation on theme: "ECATT VSDK 3.0. SAP AG 2005, Title of Presentation / Speaker Name / 2 Target Group and Prerequisites Target Group Implementation and integration teams."— Presentation transcript:

1 eCATT VSDK 3.0

2 SAP AG 2005, Title of Presentation / Speaker Name / 2 Target Group and Prerequisites Target Group Implementation and integration teams Quality managers supervising in-house development Prerequisites Experience of software testing An understanding of the architecture of the SAP Web Application Server (as provided in course SAPTEC)

3 SAP AG 2005, Title of Presentation / Speaker Name / 3 Course Goals In this course, you will learn What and when you need to test in the SAP Solution Lifecycle The advantages of eCATT for testing SAP systems compared with other automated test tools How to set up your system environment for testing with eCATT How to create test cases to test various different kinds of SAP applications How to create executable tests, and how these can be managed using the SAP Test Workbench How to migrate CATT objects to eCATT

4 SAP AG 2005, Title of Presentation / Speaker Name / 4 Contents Unit 1 Getting Ready to Test Unit 2 Getting Ready to Test with eCATT Unit 3 eCATT Scripts and the Script Editor Unit 4 Non-UI Testing Unit 5 Testing Transactions - I Unit 6 Testing Transactions - II Unit 7 Testing Transactions - III Unit 8 Building Executable Tests Unit 9 Advanced Topics

5 Unit 1: Getting Ready to Test

6 SAP AG 2005, Title of Presentation / Speaker Name / 6 Unit Objectives In this unit, you will learn: When you need to test in your SAP environment The advantages and disadvantages of manual and automated testing Decision criteria for selecting an automated test tool What can be tested using SAP eCATT

7 SAP AG 2005, Title of Presentation / Speaker Name / 7 Occasions for Testing New SAP installations Addition and integration of new components In-house developments Functional Tests Integration tests with other components Upgrades – regression testing Application of Legal Change Packages

8 SAP AG 2005, Title of Presentation / Speaker Name / 8 Manual or Automated Testing Manual Testing Requires a group of testers who must Have lab space to work in Be trained Be released from their other duties (internal) or bought-in (external) Is time-consuming Offers little potential for reuse of test resources But does have the advantage that manual testers spot errors and issues that are beyond the scope of the test plan Automated Testing Requires fewer people and resources Execution takes less time Parameterization of fields allows replay with any number of different sets of values Offers considerable possibilities for reusing test scripts Makes it easier to reproduce errors that occur during testing

9 SAP AG 2005, Title of Presentation / Speaker Name / 9 The Economics of Testing Automated testing requires good planning and modeling Learning to use a new test tool takes time An automated test script will only give you maximum ROI if it is reusable A switch to automated testing requires investment and commitment Not every test scenario has to be automated If it doesn't have to be repeatable, it doesn't necessarily have to be automated Automation is a means to an end, not an end in itself. If it is taking too long to automate the last 5% of your test scenario, consider running that part manually!

10 SAP AG 2005, Title of Presentation / Speaker Name / 10 Choosing an Automated Test Tool – External Tools Classic automated test tools can test an SAP System by driving the SAP GUI... Automated Test Tool Script SAPGUI Window Frontend Backend... But treat the SAPGUI Window as a standalone desktop application: Generally not aware of the multiple tier solution No access to what is happening on the application server or the database

11 SAP AG 2005, Title of Presentation / Speaker Name / 11 Choosing an Automated Test Tool – SAP CATT CATT – Computer Aided Test Tool Available from Release 3.0 Advantages Shipped free with SAP Basis System Most effective testing method for SAP transactions Disadvantages Control technology not fully supported No support for tabular parameters of function modules Only limited support for distributed system environments Only limited support for external applications

12 SAP AG 2005, Title of Presentation / Speaker Name / 12 Choosing an Automated Test Tool - SAP eCATT The Extended Computer Aided Test Tool (eCATT) is the successor to SAPs CATT. Its design aims were to Enable as many SAP transactions as possible to be tested automatically Provide a simplified concept for testing in a complex system landscape Allow reuse of test data by storing it in separate container objects Leverage the benefits of the existing CATT eCATT is available with Release 6.20 of the SAP Web Application Server With it, you can remotely test any mySAP.com solution that is running R/3 Basis Release 4.6C or higher (see note for details of required support packages)

13 SAP AG 2005, Title of Presentation / Speaker Name / 13 What Applications Can Be Tested Using eCATT? Transactions in SAP GUI for WindowsTransactions in SAP GUI for JavaWeb-based TransactionsDesktop-based transactionsFunction Modules and BAPIs... Using Built-In eCATT Means... Using eCATT Together With a Certified External Tool

14 SAP AG 2005, Title of Presentation / Speaker Name / 14 What Does Testing an Application Mean? Recording the application so that it can be replayed Parameterizing the application to allow it to be replayed with varying values Setting checks on the application to make the test react to different circumstances Making the test reusable

15 SAP AG 2005, Title of Presentation / Speaker Name / 15 What Systems Can Be Tested Using eCATT? You require at least one SAP Web Application Server 6.20 to operate as a test server From this central test system, you can test any other system that is running the component SAP_BASIS with Release 4.6 Support Package 32 or higher Web AS 6.20 eCATT R/3 CRM APO

16 SAP AG 2005, Title of Presentation / Speaker Name / 16 Unit Summary In this unit, you have learned Some of the issues you have to consider in deciding a test strategy The functional test tools that are available from SAP The scope of eCATT The applications that you can test with it The system landscape in which you can test

17 Unit 2: Getting Ready to Test With eCATT

18 SAP AG 2005, Title of Presentation / Speaker Name / 18 Unit Objectives In this unit, you will learn: How a finished eCATT test case is put together The different object types used in eCATT How to set up a system for use with eCATT Some of the security aspects that you need to consider

19 SAP AG 2005, Title of Presentation / Speaker Name / 19 A Finished Example Test Instructions System Landscape Description Data to drive the test Test Configuration Results Archive

20 SAP AG 2005, Title of Presentation / Speaker Name / 20 The Different Object Types Test Script The set of commands that forms the test Test Data Container Reusable sets of data that can be used to run tests System Data Container A list of systems that are addressed during the execution of a test script Test Configuration A test script, combined with data from one or more test data containers, plus a system data container that describes the correct system landscape

21 SAP AG 2005, Title of Presentation / Speaker Name / 21 Constructing an Automated Test Series What applications am I going to test? What does my system landscape look like? How can I best create an automated test for my applications? What data do I need to drive the tests? How can I organize my test cases? System data container Test script Test data container Test Workbench

22 SAP AG 2005, Title of Presentation / Speaker Name / 22 Setting Up the System Support Package Levels Each system in which you want to test must have at least the following support package level 4.6C: Support Package D: Support Package : Support Package 17 Client Settings In each client in which you want to test, you must ensure that the CATT/eCATT flag is set to allow tests to run GUI Scripting In order to use the new GUI Scripting functions, the following settings have to be made: Profile parameter sapgui/user_scripting must be set to TRUE SAP GUI must be Version 6.20 with patch level =>18 and GUI Scripting installed

23 SAP AG 2005, Title of Presentation / Speaker Name / 23 Mapping the System Landscape R/3CRMAPO Business Process Web AS 6.20 eCATT 1.Test CRM transaction 2.Check table entries in R/3 3.Run transaction in R/3 4.Call function module in APO RFC

24 SAP AG 2005, Title of Presentation / Speaker Name / 24 Defining RFC Destinations Source System Target System RFC Destination Client: 100 Lang: EN User: tester Pwd: letmein Target Transaction Direct but unsafe Client: 100 Lang: EN User: RFC Destination Target Transaction Safe but cannot run unattended

25 SAP AG 2005, Title of Presentation / Speaker Name / 25 Function of System Data Containers Command With Logical Target Test Script Target System System Data Container Target RFC Dest. The logical target describes the function of the system – for example R/3. The system data container maps the logical name to a particular RFC destination.

26 SAP AG 2005, Title of Presentation / Speaker Name / 26 Creating a System Data Container SAP Web AS 6.20 System under test Relationship described by RFC destination XYZ System Data Container Target system RFC Destination... R3 XYZ

27 SAP AG 2005, Title of Presentation / Speaker Name / 27 Advantages of System Data Containers Consistency One container can serve a whole project The RFC destinations can contain the client, language, and user name for the logon – eliminates sources of errors Access to SM59 and the authorization to create system data containers can be restricted to project leads Reuse Using logical system names in a script means that the execution environment of the script can be changed by switching system data containers. Changes in the script coding are not required.

28 SAP AG 2005, Title of Presentation / Speaker Name / 28 Unit Summary In this unit, you have learned The different object types with which you work in eCATT How these object types support you in the various stages of planning an automated test project How to set up a system to enable eCATT How to define secure RFC destinations How to create a system data container

29 Unit 3: eCATT Scripts and the Script Editor

30 SAP AG 2005, Title of Presentation / Speaker Name / 30 Unit Objectives In this unit you will learn: The structure of an eCATT script The essential features of the eCATT script editor The main aspects of the eCATT scripting language How to work with parameters

31 SAP AG 2005, Title of Presentation / Speaker Name / 31 Design Considerations for a Script Definite Goal Before you write your script, work out exactly what you want it to do Reusability Try to create small self-contained script modules. This will make them more easily reusable.

32 SAP AG 2005, Title of Presentation / Speaker Name / 32 Structure of a Script Test Script Attributes Commands Parameters Importing Exporting Local variables

33 SAP AG 2005, Title of Presentation / Speaker Name / 33 Script Attributes Administrative data about the script Search terms: Can be used in Infosystem Attaches system data container to script, allowing access to other systems

34 SAP AG 2005, Title of Presentation / Speaker Name / 34 The Script Editor Command Editor Structure Editor Parameter List

35 SAP AG 2005, Title of Presentation / Speaker Name / 35 Simple Parameters Creation Use I_IMPORT = 'LH'. CHEVAR ( I_IMPORT <> 'UA' )....

36 SAP AG 2005, Title of Presentation / Speaker Name / 36 Structured Parameters Use I_STRUCTURE-CARRID = 'LH'. I_ITAB[2]-CONNID = '0400'. GETLEN ( I_ITAB, VAR ).

37 SAP AG 2005, Title of Presentation / Speaker Name / 37 Script Language Recording and playback of applications Conditions Loops Checks Calculations Reading table values Simulation of Customizing settings Blocks of ABAP coding

38 SAP AG 2005, Title of Presentation / Speaker Name / 38 Commands for Recording Applications Recording and playback of applications FUN calls a function module TCD allows you to record and replay SAP transactions SAPGUI allows you to record sequences of screens containing controls An interface allows you to integrate test tools from third-party vendors with SAP eCATT

39 SAP AG 2005, Title of Presentation / Speaker Name / 39 Choosing the Right Driver Is the application a function module or BAPI? Yes Use FUN No Does the application run under SAP GUI for Windows or Java? No Use ext. tool Yes Does the application use controls? No Use TCD Yes Are the controls essential within the transaction? No Yes Use SAPGUI No single driver provides the best solution for every application

40 SAP AG 2005, Title of Presentation / Speaker Name / 40 Special Variables &SZBRC - Return code &TIME - Current time &DATE – Current date &YEAR – Current year &YEARA – Next year &YEARB – Last year &LPC – Loop counter &MSX – Number of messages returned by a transaction &USER – User name &CLIENT – Current client

41 SAP AG 2005, Title of Presentation / Speaker Name / 41 Pattern Function The Pattern function is similar to the statement pattern in the ABAP Editor. It allows you to build individual eCATT commands. A command consists of: The command keyword Argument (the target object) Interface (parameters that need to be passed) Target system

42 SAP AG 2005, Title of Presentation / Speaker Name / 42 Command Interface Most eCATT commands have a command interface, which corresponds to: The interface of a function module (for FUN) The screen and field structure of a transaction (for TCD) A list of user interactions (for SAPGUI) The importing and exporting parameters of a referenced script Command interfaces are stored in XML format in the local system, even if the object that they describe only exists in a remote system.

43 SAP AG 2005, Title of Presentation / Speaker Name / 43 Unit Summary In this unit, you have learned The various areas of the eCATT Test Script Editor The features of the eCATT script language How to create eCATT parameters How to use the pattern function in the eCATT Script Editor Which driver to use for various kinds of applications

44 Unit 4: Non-UI Testing Function Modules and BAPIs Table Operations Inline ABAP

45 SAP AG 2005, Title of Presentation / Speaker Name / 45 Unit Objectives In this unit you will learn: How to test function modules and BAPIs How to read from and test against the database How to use blocks of ABAP coding to enhance your test scripts

46 SAP AG 2005, Title of Presentation / Speaker Name / 46 Choosing the Right Driver Is the application a function module or BAPI? Yes Use FUN

47 SAP AG 2005, Title of Presentation / Speaker Name / 47 Non-UI Testing: Function Modules Function Module Unit Test Function Module Function Module Function Module Whole Backend Process Function Module Transaction Utility Within a Script Transaction

48 SAP AG 2005, Title of Presentation / Speaker Name / 48 Testing Function Modules FUN (,, [ ] ). Command Interface Importing Exporting Changing Tables Exceptions Function Module

49 SAP AG 2005, Title of Presentation / Speaker Name / 49 Parameterizing the Interface or INTERFACE-IMPORTING-PARAMETERNAME = value. INTERFACE-IMPORTING-STRUCTURE-FIELDNAME = value. INTERFACE-TABLES-TABLE[idx]-FIELDNAME = value.

50 SAP AG 2005, Title of Presentation / Speaker Name / 50 Trapping Exceptions DATA_INCOMPLETE CREATE_FAILED Exceptions Interface DATA_INCOMPLETE CREATE_FAILED Exceptions Interface

51 SAP AG 2005, Title of Presentation / Speaker Name / 51 Table Operations Test Script Database Application Table Customizing Table GETTAB ( TAB, INTF, [DEST] ). CHETAB ( TAB, INTF, [DEST] ). SETTAB ( TAB, INTF, [DEST] ). RESTAB ( TAB, [DEST] ).

52 SAP AG 2005, Title of Presentation / Speaker Name / 52 Using Inline ABAP ABAP. * Any ABAP Coding that is allowed in a subroutine * may appear here ENDABAP. Parameters Name DescriptionValue I/E/VRef Type V_TAB SFLIGHT-table V SFLIGHT[] ABAP. SELECT * FROM sflight INTO TABLE v_tab WHERE carrid = LH AND connid = ENDABAP. Expecting a result set of more than one line. No corresponding function module available. Once-off query

53 SAP AG 2005, Title of Presentation / Speaker Name / 53 Unit Summary In this unit you have learned: How to test function modules and BAPIs How to read from and test against the database How to use blocks of ABAP coding to enhance your test scripts

54 Unit 5: Testing Transactions - I Testing conventional transactions using the TCD command

55 SAP AG 2005, Title of Presentation / Speaker Name / 55 Unit Objectives In this unit you will learn: What transactions are suitable for testing using the TCD command How to record a transaction using the TCD command How to set input fields, read output fields, and perform fields checks with the TCD command

56 SAP AG 2005, Title of Presentation / Speaker Name / 56 Choosing the Right Driver Is the application a function module or BAPI? No Does the application run under SAP GUI for Windows or Java? Yes Does the application use controls? No Use TCD Yes Are the controls essential within the transaction? No

57 SAP AG 2005, Title of Presentation / Speaker Name / 57 Characteristics of the TCD Command The TCD command is the recording technique that was used to test transactions in CATT It is based on the Batch Input Interface It allows you to record a transaction, parameterize its input fields, and read or set checks against its output fields

58 SAP AG 2005, Title of Presentation / Speaker Name / 58 Background: The Batch Input Interface Background: Data-consistency checks in SAP transactions are often implemented within the coding of the screen flow logic (Process After Input) Batch Input is a technique originally developed for data transfer from legacy systems into an R/3 System that processes transactions in the background CATT used this technique for unattended transaction testing. It is a very efficient testing method, and has consequently been retained in eCATT

59 SAP AG 2005, Title of Presentation / Speaker Name / 59 The TCD Command TCD ( transaction, interface, [sys] ) Same system Different system

60 SAP AG 2005, Title of Presentation / Speaker Name / 60 How TCD Really Works - Recording ENTER FIELDVALUE VBAK-AUARTAF VBAK-VKORG BDC_OKCODEENT2 FIELDVALUE KUAGV-KUNNR1280 VBAP-MATNRP BDC_OKCODESICH

61 SAP AG 2005, Title of Presentation / Speaker Name / 61 How TCD Really Works - Replay No SAP GUI session FIELDVALUE... BDC_OKCODE FIELDVALUE KUAGV-KUNNR1280 VBAP-MATNRP BDC_OKCODESICH VBAK-AUARTAF VBAK-VKORG1000 Field values ENT2 Function code

62 SAP AG 2005, Title of Presentation / Speaker Name / 62 The Command Interface Transaction Screen Field

63 SAP AG 2005, Title of Presentation / Speaker Name / 63 Parameterizing Input Fields Double-click Field name Value You can replace the recorded values with either literals or variables

64 SAP AG 2005, Title of Presentation / Speaker Name / 64 Reading and Checking Output Fields To... Read a value Check a value MODE must be... 'G' 'C' Field name in VALIN column Will contain value from output field at the end of the transaction Contains the value that must be present in the screen field at runtime

65 SAP AG 2005, Title of Presentation / Speaker Name / 65 Message Handling Location of message (program and screen) Message attributes (type, ID, number) Message variables (up to four) Full text of message (in logon language) MSG Internal Table Number of messages &MSX TCD Command Interface

66 SAP AG 2005, Title of Presentation / Speaker Name / 66 Reading Message Contents Addressing the Last Message -MSG[&MSX]- Looping Through All Messages DO &MSX. -MSG[&LPC]- ENDDO.

67 SAP AG 2005, Title of Presentation / Speaker Name / 67 Testing Messages ON_LAST_MESSAGE_CHECK ( 031 ). TCD ( EC_TUTORIAL_TCD, EC_TUTORIAL_TCD_1 ). ON_LAST_MESSAGE_CHECK ( * ). TCD ( EC_TUTORIAL_TCD, EC_TUTORIAL_TCD_1 ). Require that a particular message is sent Tolerate all messages

68 SAP AG 2005, Title of Presentation / Speaker Name / 68 Troubleshooting the TCD Command

69 SAP AG 2005, Title of Presentation / Speaker Name / 69 Unit Summary In this unit you have learned: What transactions are suitable for testing using the TCD command How to record a transaction using the TCD command How to set input fields, read output fields, and perform fields checks with the TCD command

70 Unit 6: Testing Transactions - II Testing control-based transactions using the SAPGUI command

71 SAP AG 2005, Title of Presentation / Speaker Name / 71 Unit Objectives In this unit, you will learn: Why the TCD driver is not suitable for testing all transaction types How GUI Scripting works How to use the eCATT SAPGUI command to record a transaction How to set input fields, read output fields, and perform field checks in a SAPGUI recording

72 SAP AG 2005, Title of Presentation / Speaker Name / 72 Choosing the Right Driver Is the application a function module or BAPI? No Does the application run under SAP GUI for Windows or Java? Yes Does the application use controls? Yes Are the controls essential within the transaction? Yes Use SAPGUI

73 SAP AG 2005, Title of Presentation / Speaker Name / 73 Why TCD Cannot Test Everything SAP GUI Window Frontend Backend TCD Recorder Application Logic Control ALV Tree Calendar OCX control under Windows Bean under Java Action leads to local processing in SAP GUI Action leads to event handler on application server New recording component eCATT

74 SAP AG 2005, Title of Presentation / Speaker Name / 74 Introducing GUI Scripting Scripting host in GUI (Requires SAP GUI 6.20) eCATT at backend

75 SAP AG 2005, Title of Presentation / Speaker Name / 75 Recording the SAPGUI Command – Procedure 1. Select SAPGUI(Record) 2. Set the scripting granularity

76 SAP AG 2005, Title of Presentation / Speaker Name / 76 Recording the SAPGUI Command - Procedure 3. Confirm that you want to record 4. Pick the relevant initial states to record

77 SAP AG 2005, Title of Presentation / Speaker Name / 77 Scripting Granularity Action Session Action Transaction Action Screen S S T T: New TransactionS: New Screen

78 SAP AG 2005, Title of Presentation / Speaker Name / 78 Making Sense of the Command Interface - 1 One ProcessedScreen node per screen UserChangedState describes the user actions on the screen

79 SAP AG 2005, Title of Presentation / Speaker Name / 79 Parameterizing an Input Value Field name Double-click Enter parameter name in this field

80 SAP AG 2005, Title of Presentation / Speaker Name / 80 Recording the SAPGUI Command – Initial State

81 SAP AG 2005, Title of Presentation / Speaker Name / 81 Active and Inactive Checks Active Checks Record the initial states of the selected screen element types On replay, check that the values in the fields correspond to the recorded initial states Inactive Checks Record the initial states of the selected screen element types so that they can be placed into script parameters and used in the rest of the script

82 SAP AG 2005, Title of Presentation / Speaker Name / 82 Making Sense of the Command Interface - 2 One InitialState node per processed screen Are checks active? Field name Field value during recording

83 SAP AG 2005, Title of Presentation / Speaker Name / 83 Retrieving an Output Value Double-click Enter parameter name in this field

84 SAP AG 2005, Title of Presentation / Speaker Name / 84 Activating and Deactivating Field Checks

85 SAP AG 2005, Title of Presentation / Speaker Name / 85 Message Handling – MESSAGE Stipulate that certain messages must/must not occur in order for the script to be a success Find out what messages occurred during a particular block of SAPGUI commands

86 SAP AG 2005, Title of Presentation / Speaker Name / 86 Message Handling - ENDMESSAGE MIDX MODE MSGTYP MSGID MSGNR MSGV1 MSGV2 MSGV3 MSGV4 FEECDEMO 003 LH AEECDEMO AS XY 100 E_MSG_1 E_MSG_1[1]-MIDX contains the total number of messages in the table

87 SAP AG 2005, Title of Presentation / Speaker Name / 87 Creating Rules in the MESSAGE Statement Rule = What to do + Message qualification What to do R: Require E: Expect A: Allow F: Fail Mode Exit Continue processing or jump directly to ENDMESSAGE? Message qualification Any combination of Message Type Message Class Message Number

88 SAP AG 2005, Title of Presentation / Speaker Name / 88 Some Sample Message Rules Tolerate all error messages Mode Exit MSGTYPIDNumber 'A' 'E' Fail script and jump to ENDMESSAGE on error message ZJM 001 Mode Exit MSGTYP IDNumber 'F' 'X' 'E' 'ZJM' '001'

89 SAP AG 2005, Title of Presentation / Speaker Name / 89 Default Message Handling Rules User-defined Rules Allow Success Information messages Warning Fail and Exit Error Termination messages Dump

90 SAP AG 2005, Title of Presentation / Speaker Name / 90 Message Processing New Message Process according to rule Look up in user-defined rules Process according to rule Look up in default rules Discard

91 SAP AG 2005, Title of Presentation / Speaker Name / 91 The SAPGUI Command Interface 4 System Information

92 SAP AG 2005, Title of Presentation / Speaker Name / 92 Activating and Deactivating Screens Active = X: Screen active Active = : Screen inactive Active = O: Screen optional Screen 1 Screen 2 Screen 3 Join OK?

93 SAP AG 2005, Title of Presentation / Speaker Name / 93 Troubleshooting in the SAPGUI Command Set automation queue behavior Run commands with stops at various granularity levels Close GUI sessions or leave them open for inspection

94 SAP AG 2005, Title of Presentation / Speaker Name / 94 Unit Summary In this unit, you learned: Why the TCD driver is not suitable for testing all transaction types How GUI Scripting works How to use the eCATT SAPGUI command to record a transaction How to set input fields, read output fields, and perform field checks in a SAPGUI recording How to activate and inactivate screens in a script, and the things that you have to consider when doing so

95 Unit 7: Testing Transactions - III Testing Web- and Desktop-based Applications Using an External Tool

96 SAP AG 2005, Title of Presentation / Speaker Name / 96 Unit Objectives In this unit, you will learn: When to use TCD and SAPGUI, and when you have to use an external tool Why SAP chose to work with external tools The advantages of the external tool integration How the integration works

97 SAP AG 2005, Title of Presentation / Speaker Name / 97 Choosing the Right Driver Is the application a function module or BAPI? No Does the application run under SAP GUI for Windows or Java? No Use ext. tool

98 SAP AG 2005, Title of Presentation / Speaker Name / 98 Configuring The System for an External Tool Run function module SET_EXTERNAL_TOOL in test mode Run program ECATT_GENERATE_ET_USER to generate service user Regenerate authorizations in role SAP_ECET

99 SAP AG 2005, Title of Presentation / Speaker Name / 99 External Tool Integration - Architecture eCATT Script with Attributes Application Server Database Scripts stored in SAP database Frontend External Tool Physical script commands Application Under Test

100 SAP AG 2005, Title of Presentation / Speaker Name / 100 Using Compuware TestPartner to Record a Script Recording VBA Functionality Checks Parameterization

101 SAP AG 2005, Title of Presentation / Speaker Name / 101 Passing Arguments To and From TestPartner – Argument Container TestPartner Script Argument Container eCATT

102 SAP AG 2005, Title of Presentation / Speaker Name / 102 Passing Arguments To and From TestPartner – Script Coding NameTypeDirection... I_NameStringIMPORT... E_ValueStringIMPORT... Argument Container Script: VBA Coding Sub Main () Dim ImportParam As String, ExportParam As String ImportParam = GetEcattArg("I_NAME")... SetEcattArg "E_VALUE", ExportParam End Sub

103 SAP AG 2005, Title of Presentation / Speaker Name / 103 Uploading Scripts Script name and version Administrative settings Projects for upload

104 SAP AG 2005, Title of Presentation / Speaker Name / 104 Calling External Scripts REFEXT ( SCRIPT, INTERFACE, VERSION ).

105 SAP AG 2005, Title of Presentation / Speaker Name / 105 Unit Summary In this unit, you have learned: When to use TCD and SAPGUI, and when you have to use an external tool Why SAP chose to work with external tools The advantages of the external tool integration How the integration works

106 Unit 8: Building Executable Tests Calling Other Test Objects Test Configurations and Test Data Containers The Test Workbench

107 SAP AG 2005, Title of Presentation / Speaker Name / 107 Unit Objectives In this unit, you will learn: How you can modularize tests at script level The difference between a test script and a test configuration How to create test configurations How to manage test data

108 SAP AG 2005, Title of Presentation / Speaker Name / 108 Modularization at Script Level There are two reasons for modularization: To split up parts of a process into separate eCATT scripts to increase the possibility of reusing them To allow the integration of non-eCATT objects, that is External scripts Existing CATT procedures

109 SAP AG 2005, Title of Presentation / Speaker Name / 109 REF Scripts can call other scripts: REF ( SCRIPT, INTERFACE, [TARGET]). REF Create Order ATP Check Manufacturing Billing

110 SAP AG 2005, Title of Presentation / Speaker Name / 110 REFCATT From eCATT, you can call CATT procedures residing in the same system: REFCATT ( CATT, INTERFACE, [TARGET] ). REFCATT ( CATT, INT, TGT ). CATT Procedure TGT

111 SAP AG 2005, Title of Presentation / Speaker Name / 111 REMOTECATT You can also call CATT procedures that reside in a remote system: REMOTECATT ( CATT, INTERFACE, TARGET ). REFCATT ( CATT, INT, TGT ). CATT Procedure in TGT EXE

112 SAP AG 2005, Title of Presentation / Speaker Name / 112 Test Configuration Importing Parameters Script Command,. System mapping System data container Data - Variants

113 SAP AG 2005, Title of Presentation / Speaker Name / 113 Manual Variants Quick entry for a few variants Cut and paste possible from delimited text file (Excel) Variants bound to a single configuration – not reusable

114 SAP AG 2005, Title of Presentation / Speaker Name / 114 Reusing Test Data: Test Data Containers Importing Parameters Script Command,. System mapping System data container Variants Test data container

115 SAP AG 2005, Title of Presentation / Speaker Name / 115 Test Data Container Parameters Name Value Ref System ABAP Type Length Airline LH S_CARR_ID Date D 8 Variants VariantDescriptionAirlineDate Var1Data AA Var2Data LH

116 SAP AG 2005, Title of Presentation / Speaker Name / 116 Managing Test Data 1 Test Script Parameters P1 P2 P3 Test Data Container Parameters P1 P2 P3

117 SAP AG 2005, Title of Presentation / Speaker Name / 117 Managing Test Data 2 Test Script Parameters P1 P2 P3 Test Script Parameters P1 P4 P5 Test Script Parameters P2 P5 P6 Test Data Container Parameters P1, P2, P3, P4, P5, P6

118 SAP AG 2005, Title of Presentation / Speaker Name / 118 Managing Test Data 3 Test Script 20 Parameters Test Script 15 Parameters Test Script 24 Parameters Test Data Container Parameter Group 1 Test Data Container Parameter Group 2 Test Data Container Parameter Group n...

119 SAP AG 2005, Title of Presentation / Speaker Name / 119 Variant Wizard Test Data Container Configuration Variants Variants Start variant wizard

120 SAP AG 2005, Title of Presentation / Speaker Name / 120 Managing Test Data - Example I_CARRID I_CONNID I_FLDATE I_FARE I_CURR I_TYPE I_MAX_E I_MAX_B... LH EUR LH EUR LH EUR QF AUD QF AUD

121 SAP AG 2005, Title of Presentation / Speaker Name / 121 Managing Test Data - Example Test Data Container AIRCRAFT Test Configuration Maximize reuse Minimize redundancy Data for a particular test case Test Data Container AIRLINES

122 SAP AG 2005, Title of Presentation / Speaker Name / 122 Modularization at Test Organizer Level Test CatalogTest PlanTest Configuration User Test Package

123 SAP AG 2005, Title of Presentation / Speaker Name / 123 Unit Summary In this unit, you have learned: How you can modularize tests at script level The difference between a test script and a test configuration How to create test configurations How to manage test data

124 Unit 9: Advanced Topics Versioning of Scripts Migrating CATT Procedures

125 SAP AG 2005, Title of Presentation / Speaker Name / 125 Unit Objectives In this unit, you will learn Why script versioning is necessary How to create different versions of a script How the system picks the correct version of a script for execution How to migrate CATT procedures to eCATT

126 SAP AG 2005, Title of Presentation / Speaker Name / 126 Versioning For different implementations of the same test (for example, transaction with / without controls), you can create different versions of the same script.

127 SAP AG 2005, Title of Presentation / Speaker Name / 127 How Versioning Works Test Configuration Script EC_DEMO Sys. Data EC_DEMOSYSTEMS Target Sys. R3 Version 1: SAP_APPL 46C Version 2: SAP_APPL 470 R/3 Rel. 4.6C Release? 4.6C Version 1: SAP_APPL 46C

128 SAP AG 2005, Title of Presentation / Speaker Name / 128 Specifying the Validity of a Version Target System

129 SAP AG 2005, Title of Presentation / Speaker Name / 129 Backup Versions Version 1 SAP_BASIS 610 Version 2 SAP_BASIS 620 Version 3 SAP_BASIS 620 Version 2 SAP_BASIS 620 Backup

130 SAP AG 2005, Title of Presentation / Speaker Name / 130 Test System eCATT Migration Function Migration Target System X CATT Module New eCATT Script With target system X

131 SAP AG 2005, Title of Presentation / Speaker Name / 131 Migrating Variants Target System X CATT Module Variants Test System New eCATT Script with target system X Test Configuration Target System X Variants Script

132 SAP AG 2005, Title of Presentation / Speaker Name / 132 Recursive Migration Target System X CATT ModuleREF… Test System New eCATT Script with target system X REF… New eCATT Script New eCATT Script with target system X

133 SAP AG 2005, Title of Presentation / Speaker Name / 133 Unit Summary In this unit, you have learned Why script versioning is necessary How to create different versions of a script How the system picks the correct version of a script for execution How to migrate CATT procedures to eCATT

134 SAP AG 2005, Title of Presentation / Speaker Name / 134 Course Summary In this course, you have learned What and when you need to test in the SAP Solution Lifecycle The advantages of eCATT for testing SAP systems compared with other automated test tools How to set up your system environment for testing with eCATT How to create test cases to test various different kinds of SAP applications How to create executable tests, and how these can be managed using the SAP Test Workbench How to migrate CATT objects to eCATT

135 SAP AG 2005, Title of Presentation / Speaker Name / 135 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. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages Copyright 2005 SAP AG. All Rights Reserved

136 SAP AG 2005, Title of Presentation / Speaker Name / 136 Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der 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, und Informix sind Marken oder eingetragene Marken der IBM Corporation in den USA und/oder anderen Ländern. Oracle ist eine eingetragene Marke der Oracle Corporation. UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc. HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java ist eine eingetragene Marke von Sun Microsystems, Inc. JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages Copyright 2005 SAP AG. Alle Rechte vorbehalten


Download ppt "ECATT VSDK 3.0. SAP AG 2005, Title of Presentation / Speaker Name / 2 Target Group and Prerequisites Target Group Implementation and integration teams."

Similar presentations


Ads by Google