Integration test

[Former Member]

What are the different tests we do in implementation? in unit testing and integration testing( Relization phase) what is SD consultants role?

[Former Member · Accepted solution]

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.

Hope this helps you.

Regards,

Rajesh Banka

Reward points if helpful

[Former Member]

Hi ,

Unit Testing means testing Your Object as a unit, with out considering any dependencis of other objects;

Testing the object for the functionality and testing with some test cases , testing the output based on the various inputs.

Integration Testing: testing the object w.r.t to other modules also;

if the data into your object is related to other modules, if the change in business scenario in one module is going to effect in other modules, so the integration between the functionality of all objects will be checked.

After the required Configurations and Customizations are done, the testing is done by the functional consultants to see if it is in line with the business requirement. Found good, the end users also test it in the test server. Then they are moved to the production system.

Please reward if useful.

Thanks & Regards

Sadhu Kishore

[Former Member]

HI.,

Unit Testing

A unit test is a procedure used to validate that a particular module of source code is working properly from each modification to the next. 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.

Integration testing

Integration testing can proceed in a number of different ways, which can be broadly characterized as top down or bottom up. In top down integration testing the high level control routines are tested first, possibly with the middle level control structures present only as stubs. Subprogram stubs were presented in Section 2 as incomplete subprograms which are only present to allow the higher level control routines to be tested. Thus a menu driven program may have the major menu options initially only present as stubs, which merely announce that they have been successfully called, in order to allow the high level menu driver to be tested.

Top down testing can proceed in a depth-first or a breadth-first manner. For depth-first integration each module is tested in increasing detail, replacing more and more levels of detail with actual code rather than stubs. Alternatively breadth-first would proceed by refining all the modules at the same level of control

throughout the application. In practice a combination of the two techniques would be used. At the initial stages all the modules might be only partly functional, possibly being implemented only to deal with non-erroneous data. These would be tested in breadth-first manner, but over a period of time each would be

replaced with successive refinements which were closer to the full functionality. This allows depth-first testing of a module to be performed simultaneously with breadth-first testing of all the modules.The other major category of integration testing is bottom up integration testing where an individual module is

tested from a test harness. Once a set of individual modules have been tested they are then combined into a collection of modules, known as builds, which are then tested by a second test harness. This process can continue until the build consists of the entire application.

In practice a combination of top-down and bottom-up testing would be used. In a large software project being developed by a number of sub-teams, or a smaller project where different modules were being built by individuals. The sub-teams or individuals would conduct bottom-up testing of the modules which they were

constructing before releasing them to an integration team which would assemble them together for top-down testing.

REWARD if helpfull

Thanks & Regards

Narayana

[Former Member]

Visit the following link:

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

[Former Member]

HI.,

Give your mail id i will send a test case,mainly theses testing is done in FINAL PREPARATION phase., We test the fucntionality,

Ex- Unit test means,Ilke we check the fucnctionality of order,Delivery Billing,As it is relates to SD module,We check the inputs & study whether the fuunctionality is working fine

Integration test is of 2 types

1)With in SAP- Means We ccheck the functinality of SAP,That all the modules are working fine or not

Ex- After billing the accounting doccument should get updated which is relates to finance,So we check here all the transactions right from raising a purchase order till the payment of the amount by the customer

2) we check the SAp with other interfaces

REWARD if helpfull

Thanks & Regards

Narayana

[Former Member]

Dear Narayana Sir

Kindly send me some test cases to my mail id sairanjan_124@sify.com