Skip to Content

eCATT : Creating a Test Case for a Web Dynpro Application

In my previous Welogs on eCATT , I discussed topics starting from “Introduction to eCATT” to “Executing a Test Case using eCATT “. This Weblog will go a step further and discuss how to create a Test Case for a Web DynPro Application. This is one of the major features of eCATT that allows users to test business processes that cross system boundaries. The scenario for Test is as follows : Scenario The goal is to create a Test Case for a Web Dynpro Application that is on java Stack . The application is for Purchase Order Creation. The application will be tested for different set of data . The url is : http://:/webdynpro/dispatcher/local/PO/CreatePO Procedure: The first step towards creating a Test Case for a Web Dynpro Application is to create a RFC destination in SAP . Tcode : SM59 RFC Destination : WEBDYNPRO2 , Type : G Target Host : Service : image Now , create a System data Container assigning HTTP RFC destination created above . Tcode : SECATT image After creation of Test Data Container , Create Test Script . ( the creation of the same has been discussed at length in my previous weblogs ) In pattern option under UI control Group select WEBDYNPRO command . Entering System data Container and Target System . image The Application in our case is “/webdynpro/dispatcher/local/PO/CreatePO” image Recording starts . The application starts in the browser . image Entering appropriate Header Info in the fields . image Adding item details . image Creating Purchase Order . image The PO is created in SAP and the PO number is reflected in top right corner . image Now , click “Stop Recording” Option . image Below we can see a WEBDYNPRO command is created for each page of application. image Now Parameterize the Input values image Creating Test Data Container . image 2 Variants for are created . The Company code data is different in both cases . For Test Variant 1 : Company Code is 1000. For Test Variant 2 : Company Code is 3000. image Now Creating Test Configuration and attaching Test Data Container . image Executing Test Configuration . image Examining Log we see that : PO can be created with var1 ( Company Code :1000 ) PO cannot be created with var2 ( Company Code :3000 ) image Thus we were able to successfully Create a Test Case for a “Web Dynpro Application” deployed on Java Stack using eCATT.
You must be Logged on to comment or reply to a post.
  • Hello Sumeet,

    great Web Log, in fact. This is exactly what the user needs for starting: a step-by-step introduction how to create his first recording.

    There is only one thing you forgot to mention: if the Web Dynpro application requests user authentication, you have to apply additional settings in your SM59 destination:
    1. Go to the tab Logon/Security
    2. Chose Basic Authentication
    3. Supply Username and Password for the Web Dynpro application in the fields at the lower end of the window

    Best regards,

  • hi i want to know difference between ecatt and qtp

    i have seen in some blogs that ecatt does not support for web transactions

    If only SAPGUI based transactions are involved in testing than eCATT is the best tool to be used. And if web based transactions are also involved, forced to go for QTP.

  • Hi Sumeet Kaul,

    It is great job.
    I am also working for Webdynpro for Abap , I want to some clarifications about my test case, While recording I am getting the following error message from webdynpro application(ABAP) “Unable to interpret

    Thank you,
    Raghava Vakada.

  • It is great job.
    I need  using ecatt testing for Web Dynpro application Abap.
    Could you hep me with some documentation that shows process step by step as you did for Java stack?

    Best regards,
    Giuseppe Michienzi