Skip to Content
author's profile photo Former Member
Former Member

Xi integration testing

Hi All,

what are the main things we do in integartion testing...

Can some one brief me...

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Jul 24, 2008 at 04:52 PM

    1) Connectivity with your partners if your's is a B2B Scenario.

    2) Basic functionality of your mappings and configuration.

    3) Simulate the productive environment as closely as possible and minimize the errors when gone live.

    Regards,

    ravi

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 24, 2008 at 07:15 PM

    any more details guys....

    Add a comment
    10|10000 characters needed characters exceeded

    • SAP's definition of integration testing:

      "Integration Testing

      An orderly progression of testing in which software elements, hardware elements or both are combined and tested until the entire system has been integrated.

      Integration tests deal mainly with the testing of cross-application process chains in addition to transactions and business processes. The process models and the test cases derived from these form the basis of these tests. "

      Regards,

      Ravi

  • Posted on Jul 24, 2008 at 05:19 PM

    Hi

    In addition to Ravi's answer :

    Usually a limited set of master data is loaded for integration testing and unit testing. Many projects will develop a list of materials and releated data to be used for unit testing and integration testing.

    In addition, many projects use the various testing stages to test their loading procedures of master data. So just before unit testing you load a small subset of master data for the load programs you might use, sometimes a lot of this is manually loaded. Then for integration testing a larger quantity of data is loaded via the various load programs. Usually, especially in larger implementations, each testing cycle is done in different client or box. That way all the stages of the cut-over process are tested and practiced. So hopefully at go-live the implementation goes smooth.

    Hope this is usefull

    Thanks

    Saiyog

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      You may want to test the following too.

      1, The data from the legacy is going to the right dtaa places in SAP and viceversa.

      2. Check if the data sent between legacy and SAP make enough sense or any translation might be required.

      3. Partner profile creation, business systems, business services creation shall be tested.

      4. IDOC confirmation messages receipt could be tested.

      5. Any specific logic for an interface implemented should be tested.

      6. All possible business scenarios could be tested.

      7. Exception handling mechanism could be tested.

      8. Alert mechanism could be tested whihc includes notification to right ppl in cases of any failures shoudl be tested.

      8. An excercise to be done to get the list of contact to whom the notifications should go should be performed.

      The list goes, but all these could be spilt into multiple groups and each group could be thoroughly tested as each integration cycle.

      Hope this helps....

      Thanks,

      Valli.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.