Skip to Content

 eCATT : Extended Computer Aided Test Tool

Creation of Test Scripts

In my last weblog on “eCATT : An Introduction” I introduced the subject of eCATT and discussed the capabilities and features of the same . In this weblog I will be going a step further and explain the creation of Test Scripts , the first step in the creation of Test Cases using eCATT .

Before creating Test Scripts using eCATT we need to have some system setting done .

1. Maintaining Table T000
    a. Start transaction SM31.
    b. In the Table/View field, enter T000.
    c. Choose Maintain.
    d. In the Change View “Clients”: Overview screen, select the relevant client and choose.
    e. In the Restrictions when Starting eCATT field, select an entry that allows eCATT.

2. Enabling Scripting at the front End .
( Check whether SAP GUI Scripting component is installed. There is an option for installing this component when installing the SAP GUI.)
    a. On any screen, choose Customizing of local layout.
    b. Choose Options….
    c. Choose the Scripting tab.
    d. Select Enable Scripting.
    e. Choose Apply.

3. Enabling Scripting on application server .
    a. Start transaction RZ11.
    b. On the Maintain Profile Parameters screen, enter sapgui/user_scripting.
    c. Choose Display.
    d. In the Display Profile Parameter Attributes screen, choose Change value.
    e . Enter TRUE in the New value field.
 

Now we will start with creation of Test Scripts :
The first step in the Creation of Test Case is Creation of Test Scripts .

A test script consists of three principal parts-

  • Its attributes
  • The script commands
  • The parameters

      

We will be creating a Test Scripts for Sales Order Scenario .

Step1 : Goto Transaction SECATT :

image

image

image

Now the Recording for the Transaction VA01 will start .We will Record and save the Transaction .

image

image

image

After Recording is saved TCD Command Appears in the Command Editor.

image

Now Define Parameters . Only those parameters should be defined which are expected to take values at runtime.

image

On clicking the Toggle Option : The Command Editor Appears .

image

On clicking the “Command Interface” Option the interface appears in left bottom corner of the screen .
For each screen traversed screen name and screen number appears . Within each screen all the Input values that were entered during Recording are parameterized .

When all the screen input fields are parameterized , save the Script .

This Creates the Test Script for the Sales Order Scenario.

In the next Weblogs I will be discussing Test Data Containers , System Data Containers and Test Configurations to complete the Test Case for the Sales Order Scenario.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply