testing

[Former Member]

what is unit testing? and integration testing

[former_member290897 · Accepted solution]

Hello Srinivas,

to say it in simple words:

- Unit testing can be imagined as one product which will be tested. Assume you have a EMail program and you test all the functionality it provides.

- Integration testing is when you have a product which connects in some way with another product. This interconnection also needs to be tested in so called integration scenarios where the essential functionality between these two product are tested. An example to this would be a Email client which connect against an EMail Server.

Hope this information is helpful for you.

Have fun,

Juergen

[Former Member]

Hi Srinivas

<b>Unit test issues</b>

The unit tools test all SAP development work that handles business object processing for the connector. Also, the unit test tools enable you to test the interaction of your work with the ABAP components of the connector. The test tools allow you to test your development work as an online user (real-time) only.

check this link

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

check this link for integration test

http://www.purdue.edu/onepurdue/contribute_pdf/sap_integration_testing_orientation.pdf

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

http://whitepaper.techweb.com/search/keyword/cmptechweb/Sap%20Integration%20Testing%20Software/Sap%2...

Reward all helpfull answers

Regards

Pavan

[Former Member]

Hi Srinivas,

1.Unit or Component or White Box Testing : "Component Testing", sometimes called Unit Testing. Unit Testing involves checking that each feature specified in the "Component Design" has been implemented in the component.

In theory an independent tester should do this, but in practise the developer usually does it, as they are the only people who understand how a component works. The problem with a component is that it performs only a small part of the functionality of a system, and it relies on co-operating with other parts of the system, which may not have been built yet. To overcome this, the developer either builds, or uses special software to trick the component into believing it is working in a fully functional system.

2.Interface or Integration Testing: As the components are constructed and tested they are then linked together to check if they work with each other. It is a fact that two components that have passed all their tests, when connected to each other produce one new component full of faults. These tests can be done by specialists, or by the developers.

Interface Testing is not focussed on what the components are doing but on how they communicate with each other, as specified in the "System Design". The "System Design" defines relationships between components, and this involves stating:

What a component can expect from another component in terms of services.

How these services will be asked for.

How they will be given.

How to handle non-standard conditions, i.e. errors.

Tests are constructed to deal with each of these.

The tests are organised to check all the interfaces, until all the components have been built and interfaced to each other producing the whole system.

Hope this helps.

Please reward if useful.

Thanks,

Srinivasa

[Former Member]

Hi Srinivas,

In simple terms unit testing is a method used to validate individual units of source code are working properly. A unit is the smallest testable part of an application.

Integration testing is the process of s/w testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.

Check this SAP doc on Unit & Integration testing in SAP:

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

Regards,

Subhasha