SAP Testing Dhruv Dalal| Jul 3, 2009 | Comments(23) SAP Testing is same as manual testing but here the

applications are SAP

R/3 and Enterprise portal.Whenever there is change in R/3 and Portal and

You need to design test cases according the changerequest and test the


If you have knowledge in the module (like HR, CRM, SD, SRM), which you

are going to test would behelpful to you.

UAT means USER ACCEPTING TESTING. Suppose end user raised an issues that

we solved and sendto end used it is working fine. then we get

confirmation from him that it is fine. that is call UAT.

UNIT TESTING - This is done by developer and anyone who did any

customizing or any code to ensurewhat they did is working properly

INTEGRATION testing - Done by tester by developing some scenarios which

are most unlikely and getthe result to ensure the integration is correct

UAT is performed by end users or the testing team. System Integration Testing (SIT) which is performed by the SAPteam in the development client. Integration testing and other testing are done by testers/functional depending upon theobject to test. unit testing are done by developers After unit testing. Firstly.Each of this function usually consists of "sub-functions" corresponding to a single method or a group of methods (if you are developing OO-based). functional testing and other cross functional testing are there done bytesters In realization phase. Testing usually follows two paths. Unit Tests are defined and performed by developers. . A process consists usually of several functions.Apart from that. regression testing. and secondly User Acceptance Testing (UAT) which is performed in theQA client after transport from the development client.

it is necessary to test the functions and performance of your solution. SAP provides you with an environment for all test phases.Unit Tests could be described as white-box tests whereas a normal tester (which should be not identicalto the developer) will test entire functions (black-box tests). --. regression tests . With the SAP Test Workbench.During the entire life cycle of a SAP solution.which you can use for testing in the following cases: Implementation of SAP solutions Integration of new components and business scenarios Customer developments Function tests Integration tests with other components Upgrades.

Importing support packages Integration Features Test Preparation Creation of manual and automated test cases Management of manual and automated test cases Creation of test plans Definition and management of test series Test Execution Execution of mass tests using Extended Computer-Aided Test Tool and Computer Aided Test Tool Integration of test cases and test scripts of non-SAP providers Assignment of work lists (test packages) to individual testers .

testresults. UAT is performed by end users or the testing team.Test Evaluation Permanent overview of test progress and test results Complete documentation of test processes in the test plans (test cases. Firstly. error messages) Detailed tabular and graphical evaluation of all test plans Export of test results to Office applications Message processing Testing usually follows two paths. 2------------------------------------------------------ Role of SAP Consultant In Testing . System Integration Testing (SIT) which is performed by the SAPteam in the development client. and secondly User Acceptance Testing (UAT) which is performed in theQA client after transport from the development client. test case descriptions. test case notes.

MM-SD-FICO for example. What is Unit testing and Integration Testing? 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. invoice document are printed in the required format and showing the correct data. Integration testing is also called SIT ( System integration testing) Testing mathologies and types: there are 6 types of testings: 1. Unit testing is refer to the module which are going to implement. Integration testing will be cross the modules.1. Unit Testing 2. Performance Testing 5. MM. FICO etc. SD. there will be test script based on that testing will be performed. User Acceptance testing . System Testing 3. They will test whether the output documents such as purchase order. What is the role of SD Consultant in Testing while implementing the project? 2. System Integration security Testing 4.

Security testing you will be testing different roles and functionalities and will check and signoff.4 and 5 seperately alone one by one using test cases and test data.3. then 4-PGI and then 5-Invoice. We will not be looking and checking/testing any integration between order and delivery. then 3-transfer order. Performance testing is refered to as how much time / second will take to perform some actions. delivery and TO. like e. in SD standard order cycle. Like e.2. Whrereas System testing you will be testing the full cycle with it's integration. we do have 1-create order. then 2-delivery. TO and PGI and then invoice.g. PGI. If BPP defination says 5 seconds for PGI .g.6. and you will be testing using test cases which give a full cyclic test from order to invoice. So we will be testing 1. Regression Testing Unit testing is done in bit and pieces.

preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases. This is an . User Acceptance Testing: Refers to Customer testing. This will be done on each phase of testing.then it should be 5 and not 6 second. The user test model is comprised of a sub-set of system integration test cases. We use different software during testing. Mercury Load Runner: is used for performance testing. Most commonly use are Test Director: which is used to record requirement. which combine various business processes. Usually it is done using software Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. The UAT will be performed through the execution of predefined business scenarios.

Parallel Testing? Technical Unit Testing= Test of some technical development such as a user exit. the test usually consists of a test data set that is processed according to the new program.Functional Unit Testing . A successful test only proves the developed code works and that it performed the process as as designed. What does the following terms means : .IntegrationTesting . 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.Technical Unit Testing . Functional Unit Testing= Test of configuration. or interface.Volume Testing . custom program. A successful test shows that the development or configuration works as designed and the data is .automatic tool.

or any systemic problem. A successful test will show identical results when both the legacy system and new system results are compared. IntegrationTesting= Testing a process. Integration Testing ( Along with other integrated modules) The 3 types of testing is as follows:1. Individual Testing ( Individually which we've created) 2. Unit testing (where an individual process relevant to a SD or MM etc is tested) 2. 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. . Integration testing (where a process is tested that cuts across all areas of SAP). What kind of testings that are carried out in testing server? 1. development or functionality will touch or integrate . development or configuration within the context of any other functions that the process. 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 indicates that the processes will not slow or crash the system due to a full data set being utilized.accurate as a result. Regressive Testing ( Entire Process) 3. 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. system resources issues. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas. The test should examine all data involved across all modules and any data indirectly affected.

3. Stress testing (where lots of transactions are run to see if the system can handle the data) .

Sign up to vote on this title
UsefulNot useful