Xi integration testing

[Former Member]

Hi All,

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

Can some one brief me...

[former_member181962 · Accepted solution]

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

[Former Member]

any more details guys....

[former_member181962]

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

[former_member193376]

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

[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.