You are on page 1of 3

In any SAP Project testing can be happen in 3 phases. Unit testing happens in Dev server.

Integration and User Acceptace Test happens in Quality Server.These all are done manually step by step. We have got standard SAP Test Scripts/prepares based on the Client/company/Project. Unit Testing: it can be tested in bits and pieces (Ex: Sales order Creation). Integration Testing: OTC Flow (Create Sales order to Invoice). User Acceptace done by the Client in "Q", if they are satisifed with the result they will give Sign-off for the project. There is another sort of testing so called Automated Regression Testing. that can be done by eCATT/IBM Rational Tools.

# 2 Unit Testing:When you test every single document is called unit testing. Integration Testing :It is purely with other modules and we have to check whether the FI testing is working with other related modules or not. UAT :When we test any particular document with the user and if it is ok immediately we have to take the signature on the document, which is signed off and can be forwarded to the immediate boss. There are some steps to be followed when we go for user acceptance testing. What kind of testings that are carried out in testing server? 1. Individual Testing ( Individually which we've created) 2. Regressive Testing ( Entire Process) 3. Integration Testing ( Along with other integrated modules) The 3 types of testing is as follows:1. Unit testing (where an individual process relevant to a SD or MM etc is tested) 2. Integration testing (where a process is tested that cuts across all areas of SAP). 3. Stress testing (where lots of transactions are run to see if the system can handle the data) Testing mathologies and types: there are 6 types of testings: 1. Unit Testing 2. System Testing

Functional Unit Testing . Security testing you will be testing different roles and functionalities and will check and signoff. then 3-transfer order.Parallel Testing? Technical Unit Testing= Test of some technical development such as a user exit.3.3. Whrereas System testing you will be testing the full cycle with it's integration.g. and you will be testing using test cases which give a full cyclic test from order to invoice. in SD standard order cycle. So we will be testing 1. which combine various business processes. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed. we do have 1-create order. like e. User Acceptance testing 6. then 4-PGI and then 5-Invoice. We will be incorporating defects that are coming during these testings using different test cases. delivery and TO.IntegrationTesting . This is an automatic tool. Like e. PGI.2. Regression Testing Unit testing is done in bit and pieces. preparing test plan and then recording the progress.4 and 5 seperately alone one by one using test cases and test data. Performance Testing 5. . System Integration security Testing 4. TO and PGI and then invoice. custom program. Mercury Load Runner: is used for performance testing. or interface. Usually it is done using software. Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. What does the following terms means : .g. We will not be looking and checking/testing any integration between order and delivery. The user test model is comprised of a sub-set of system integration test cases. User Acceptance Testing: Refers to Customer testing. then 2-delivery. We use different software during testing. This will be done on each phase of testing. Performance testing is refered to as how much time / second will take to perform some actions.Volume Testing . Most commonly use are Test Director: which is used to record requirement. The UAT will be performed through the execution of predefined business scenarios.Technical Unit Testing . If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second.

The test should examine all data involved across all modules and any data indirectly affected. A successful test shows that the development or configuration works as designed and the data is accurate as a result. development or configuration within the context of any other functions that the process. I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several. development or functionality will touch or integrate . system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas. IntegrationTesting= Testing a process. system resources issues. or any systemic problem. A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized. .Functional Unit Testing= Test of configuration. Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems. Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.