Scribd Logo
Upload

Welcome to Scribd!

  • 804 views

    SAP Testing Roles and Responsibilities

    Uploaded by

    Anonymous 0wXXmp1
    The document discusses roles and responsibilities in SAP testing. It defines various types of testing including unit testing, integration testing, system testing, security testing, performance testing, user acceptance testing, and regression testing. It explains that unit testing involves testing individual modules or processes separately, while integration testing checks how processes integrate across modules. Performance, security, and regression testing are also examined, along with the tools used for testing like Test Director and Mercury LoadRunner. Technical unit testing, functional unit testing, integration testing, volume testing, and parallel testing are defined. The key types of testing carried out on the testing server are individual testing, regression testing, and integration testing.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    SAP Testing Roles and Responsibilities

    Uploaded by

    Anonymous 0wXXmp1
    804 views3 pages
    The document discusses roles and responsibilities in SAP testing. It defines various types of testing including unit testing, integration testing, system testing, security testing, performance testing, user acceptance testing, and regression testing. It explains that unit testing involves testing individual modules or processes separately, while integration testing checks how processes integrate across modules. Performance, security, and regression testing are also examined, along with the tools used for testing like Test Director and Mercury LoadRunner. Technical unit testing, functional unit testing, integration testing, volume testing, and parallel testing are defined. The key types of testing carried out on the testing server are individual testing, regression testing, and integration testing.

    Original Description:

    roles and responsibilities.

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses roles and responsibilities in SAP testing. It defines various types of testing including unit testing, integration testing, system testing, security testing, performance testing, user acceptance testing, and regression testing. It explains that unit testing involves testing individual modules or processes separately, while integration testing checks how processes integrate across modules. Performance, security, and regression testing are also examined, along with the tools used for testing like Test Director and Mercury LoadRunner. Technical unit testing, functional unit testing, integration testing, volume testing, and parallel testing are defined. The key types of testing carried out on the testing server are individual testing, regression testing, and integration testing.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    804 views3 pages

    SAP Testing Roles and Responsibilities

    Uploaded by

    Anonymous 0wXXmp1
    The document discusses roles and responsibilities in SAP testing. It defines various types of testing including unit testing, integration testing, system testing, security testing, performance testing, user acceptance testing, and regression testing. It explains that unit testing involves testing individual modules or processes separately, while integration testing checks how processes integrate across modules. Performance, security, and regression testing are also examined, along with the tools used for testing like Test Director and Mercury LoadRunner. Technical unit testing, functional unit testing, integration testing, volume testing, and parallel testing are defined. The key types of testing carried out on the testing server are individual testing, regression testing, and integration testing.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 3

    SAP testing roles and responsibilities

    1. What is the role of SD Consultant in Testing while implementing the project?


    2. What is Unit testing and Integration Testing?
    Testing : the core team members along with end users 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.
    Integration testing will be cross the modules. MM-SD-FICO for example. Integration
    testing is also called SIT (System integration testing)
    Testing methodologies 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 SAP SD standard order cycle; we do
    have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5Invoice. So we will be testing 1, 2, 3, 4 and 5 separately 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.
    Whereas 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 sign-off.
    Performance testing is referred to as how much time / second will take to perform
    some actions, like e.g. PGI. If BPP definition says 5 seconds for PGI then it should be
    5 and not 6 second. Usually it is done using software.

    Regression testing is referred to a test which verifies that some new configuration
    does not adversely 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.
    SAP Functional unit testing
    What does the following terms means :
    - Technical Unit Testing
    - Functional Unit Testing
    - Integration Testing
    - 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.
    Integration Testing = 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 SAP 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)

    You might also like