unit , interation test

[Former Member]

what is unit testing ? how to do

what is integration test

Edited by: shaik shaik on Jan 3, 2008 8:12 AM

[Former Member]

let take an example we had created a sales document type we will check that coreesponing sales order is working or not that is unit testing, suppose if the order is working we will checks that credit management is working properly or not and the MRP is passing to PP or not ,and the financial values are passing to FI or not we check all those in intergatration testing,

unit testing is boundde to ur module where as integaration testing is done in between modules.

[Former Member]

Hi,

In simple words.

Unit testing is performed to check the master data setup, enterprise sturcture... etc are correctly defiend and assigned or not. It will be dne by the respective functional people.

Eg: Creation of sales order, delivery, billing, condition record...etc

Integration testing is performed cross-module wise. Once unit testing is done, then the integration testing will be done to find out the effect on the other areas.

Eg: While doing a PGI, the stock should be reduced from the storae loc (MM), the costs of goods sold accounts should be hit (SD-MM-FI)... etc

Prase

[Former Member]

Dear Shaik,

Testing : the core team members along with endusers 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 mathologies 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 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.

Do award points if you found them useful.

Regards,

Rakesh