9 Replies Latest reply: Aug 28, 2007 2:19 PM by MOHAMMED NABEEL RSS

SAP SD Testing

Smitha Reddy
Currently Being Moderated

Hello Experts

 

Greetings !

 

1 ) Can anyone kindly tell me what types of testing is done in SD Module ?

2 ) Can anyone kindly explain me Sales order cycle End to End?

 

Can email me any information to smithareddy@consultant.com

 

Points will be rewarded to helpful answer.

 

Cheers

Smitha

  • Re: SAP SD Testing
    Shesagiri G
    Currently Being Moderated

    <b>HI

    MAIL SENT REWARD IF HELPS</b>

  • Re: SAP SD Testing
    y v. s. reddy
    Currently Being Moderated

    Hi,

     

    Generally SD Consultant will do Unit testing,Integration testing and some times regression testing to test the changes done in Configuration.

     

    General sales order cycle starts with Inquiry - > Quotation -> Order -> Delivery -> Picking -> Goods Issue - > Billing.

     

    i think this will help u.

  • Re: SAP SD Testing
    madhu kumar
    Currently Being Moderated

    hi smitha

    1. unit testing

    2. integration testing

    3. regression testing

     

    are the 3 testings done.

     

    reward points if helpful

    madhu

  • Re: SAP SD Testing
    Ahmad Ali Shaik
    Currently Being Moderated

    Hi Smitha,

     

    mail sent.

     

    Regards

     

    Ali

  • Re: SAP SD Testing
    Naveen Bathini
    Currently Being Moderated

    Dear Smitha,

     

    Testing

    : the core team members along with endusers will test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data.

    Unit testing

    is refer to the module which are going to implement. SD, MM, FICO etc. there will be test script based on that testing will be performed.

    A unit test is a procedure used to validate that a particular module of source code is working properly. The procedure is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. Ideally, each test case is separate from the others; constructs such as mock objects can assist in separating unit tests. This type of testing is mostly done by the developers and not by end-users

    eCATT: extended Computer Aided Test Tool (BC-TWB-TST-ECA)
    Use extended Computer Aided Test Tool (eCATT) to create and execute functional tests for software. The primary aim is the automatic testing of SAP business processes. Each test generates a detailed log that documents the test process and results.

    eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java. In order to offer a complete test solution that covers other GUIs, eCATT has interfaces to third party tools.

    Test cases usually make database changes. Therefore, you should not normally run them in productive systems.

    In general, do not use eCATT to manipulate data in a productive system: eCATT is a test tool. Instead, use techniques such as Batch Input.

    eCATT can be used with the Test Workbench.

    You can migrate test cases from Computer Aided Test Tool (CATT) to take advantage of the better features of eCATT.

    eCATT is also integrated with the Object Navigator (SE80).

    You can:
    · Test transactions, reports, and scenarios
    · Call BAPIs and function modules
    · Test remote systems
    · Check authorizations (user profiles)
    · Test updates (database, applications, GUI)
    · Test the effect of changes to customizing settings
    · Check system messages

    eCATT runs in a system based on SAP Web Application Server 6.20 or higher. However, you can use this system to test systems with Release 4.6C or higher.

    You can find a step by step introduction to eCATT in the eCATT Tutorial.
    http://help.sap.com/saphelp_nw04/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htm




    http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm
    http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap3/sap144.htm

    Integration testing

    will be cross the modules. MM-SD-FICO for example. Integration testing is also called SIT ( System integration testing)

    Testing mathologies and types: there are 6 types of testings:
    1.

    Unit Testing


    2. System Testing
    3.

    System Integration security Testing


    4. Performance Testing
    5. User Acceptance testing
    6. Regression Testing

    Unit testing

    is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.

    Whrereas

    System testing

    you will be testing the full cycle with it's

    integration

    , and you will be testing using test cases which give a full cyclic test from order to invoice.

     

    Security testing you will be testing different roles and functionalities and will check and signoff.

     

    Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI.  If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second.  Usually it is done using software.

     

    Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality.  This will be done on each phase of testing.

     

    User Acceptance Testing:  Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.

     

    We use different software during testing. Most commonly use are

     

    Test Director:  which is used to record requirement, preparing test plan and then recording the progress.  We will be incorporating defects that are coming during these testings using different test cases.

     

    Mercury Load Runner:  is used for performance testing.  This is an automatic tool.

     

    What does the following terms means :

    - Technical Unit Testing

    - Functional Unit Testing

    - IntegrationTesting

    - Volume Testing

    - Parallel Testing?

     

    Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program.  A successful test only proves the developed code works and that it performed the process as as designed.

     

    Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.

     

    IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.

     

    Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.

     

    Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.

     

    I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.

     

    What kind of testings that are carried out in testing server?

     

    1. Individual Testing ( Individually which we've created)

    2. Regressive Testing ( Entire Process)

    3. Integration Testing ( Along with other integrated modules)

     

    The 3 types of testing is as follows:-

     

    1. Unit testing (where an individual process relevant to a SD or MM etc is tested)

     

    2. Integration testing (where a process is tested that cuts across all areas of SAP).

     

    3. Stress testing (where lots of transactions are run to see if the system can handle the data)

     

    Regards,

    Naveen.

     

  • Re: SAP SD Testing
    Dasari Narendra
    Currently Being Moderated

    hi

     

    Sap Testing Links

     

    /people/sapna.modi/blog/2006/04/10/ecatt--an-introduction-part-i

    /people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation-150-tcd-mode-part-ii

    /people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation--sapgui-mode-part-iii

    /people/sapna.modi/blog/2006/04/18/ecatt-logs-part-vi

    http://help.sap.com/saphelp_47x200/helpdata/en/20/e81c3b84e65e7be10000000a11402f/frameset.htm

     

    http://help.sap.com/saphelp_nw04/helpdata/en/12/6efc3f8fc2c542e10000000a1550b0/content.htm

     

    http://www.thespot4sap.com/Articles/SAP_Testing_Lessons_Learned.asp

     

    http://www.sap-img.com/sap-catt.htm

     

    Role of sap Consultant in Testing

    http://www.sap-img.com/general/role-of-sap-consultant-in-testing.htm

     

    http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm

     

     

    Sd process chk ur mail

     

    Reward if USeful

    Thanx & regards.

    Naren..

    • Re: SAP SD Testing
      Smitha Reddy
      Currently Being Moderated

      Hello Naren/Naveen/Ali/Madhu/Reddy

       

      Thanks for the your wonderful information.

       

      I really appreciate that.

       

      Anyone can provide me a Small example of Unit testing and Integration testing.

       

      Like Scenario,Test Case,Test Data etc etc

       

      Thanks in Advance,

      Smitha

      • Re: SAP SD Testing
        Dasari Narendra
        Currently Being Moderated

        hi

         

        http://infolab.stanford.edu/~burback/watersluice/node19.html

         

        http://msdn2.microsoft.com/en-us/library/aa292128(VS.71).aspx

         

        Unit testing deals with testing a unit   as a whole. This would test the interaction of many functions but confine the test within one unit. The exact scope of a unit is left to interpretation. Supporting test code, sometimes called scaffolding, may be necessary to support an individual test. This type of testing is driven by the architecture and implementation teams. This focus is also called black-box testing because only the details of the interface are visible to the test. Limits that are global to a unit are tested here.

         

        In the construction industry, scaffolding is a temporary, easy to assemble and disassemble, frame placed around a building to facilitate the construction of the building. The construction workers first build the scaffolding and then the building. Later the scaffolding is removed, exposing the completed building. Similarly, in software testing, one particular test may need some supporting software. This software establishes an environment around the test. Only when this environment is established can a correct evaluation of the test take place. The scaffolding software may establish state and values for data structures as well as providing dummy external functions for the test. Different scaffolding software may be needed from one test to another test. Scaffolding software rarely is considered part of the system.

         

        Sometimes the scaffolding software becomes larger than the system software being tested. Usually the scaffolding software is not of the same quality as the system software and frequently is quite fragile. A small change in the test may lead to much larger changes in the scaffolding.

         

        Internal and unit testing can be automated with the help of coverage tools. A coverage tool analyzes the source code and generates a test that will execute every alternative thread of execution. It is still up to the programmer to combine these test into meaningful cases to validate the result of each thread of execution. Typically, the coverage tool is used in a slightly different way. First the coverage tool is used to augment the source by placing informational prints after each line of code. Then the testing suite is executed generating an audit trail. This audit trail is analyzed and reports the percent of the total system code executed during the test suite. If the coverage is high and the untested source lines are of low impact to the system's overall quality, then no more additional tests are required.

         

        http://www.acm.org/ubiquity/views/t_burns_1.html

         

        Integration Testing

        http://en.wikipedia.org/wiki/Integration_testing

         

        http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci1243430,00.html

         

        http://www.bitpipe.com/tlist/Integration-Testing.html

         

        ===

        http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm

        ===

         

        Reward if USeful

        Thanx & Regards.

        Naren

  • Sales Cylce
    MOHAMMED NABEEL
    Currently Being Moderated

    Hi,

     

    <u><i><b>Sales Cycle</b></i></u>

     

    Inquiry -


    Quotation -


    Sales Order -


    Delivery -


    Picking -


    PGI -


    Billing.

    <u><i><b>Important Steps</b></i></u>

    Sales Order --- Delivery -- PGI---- Billing

Actions