Testing

[Former Member]

hi friends,,

what is Regression Testing & System Integration testing?

anyone can give the idea of these testings..

thank you

manu

[Former Member · Accepted solution]

hi,

pl check this info.

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.

What does the following terms means :

- Technical Unit Testing

- Functional Unit Testing

- IntegrationTesting

- Volume Testing

- Parallel Testing?

Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. 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.

Functional Unit Testing= Test of configuration, 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 shows that the development or configuration works as designed and the data is accurate as a result.

IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.

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, 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.

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.

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.

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)

regards

sadhu kishore

[Former Member]

hi friends,

what is individual orders and how to it configure?

thanks

manu

[Former Member]

Testing is normallly done by manually, but lot of automatic tools &methods also available in the market.

Regression testing is referred to a test which verifies that some new configuration doesn’t adversely impact existing functionality. This will be done on each phase of testing.

System integration is nothing but testing the integration parts like creating the order and creating the delivery with reference to that order, checking whether Transfer order is created from WM, like that. It addresses about the integration issues.

Also there are other type of testings like unit testing, performance testings and User acceptance testings are also available.

Hope it is useful

Reward if useful..

[Former Member]

hi,

anybody tell me ,

what is the procedure of testing in landscape?

thanks

manu

[Former Member]

Type of Testings:

• Configuration testing - The configuration testing ensures that all the requirements supported by standard SAP are properly configured and verified.

The main objective of the testing is to test the functioning of the individual SAP transactions after baseline configuration is completed and to identify any configuration related defects.

• Development Unit Testing - Development Unit Testing is performed for all the identified GAPs in requirements.

The objective of the Development Unit Testing is to ensure that the development objects are performing as per the requirement and design specifications.

• Interface Testing - The Interface testing includes the testing of the SAP interface programs, external interface programs and all related middleware settings.

The objective of interface testing is that the interface meets the technical and functional requirements and the data transfer requirements between the applications.

• Batch Testing - Batch testing tests that all the batch processes required are performing as per expectation and the scheduler is working as expected.

• Conversion Testing - Conversion testing includes the testing of the SAP data migration programs and all related middleware settings which will load the data from the existing system to the SAP system.

The objective of this testing is to check that all the developed conversion programs are performing as expected.

• Security Testing - Security testing ensures the SAP security roles and authorization based on the defined requirements.

• Regression Testing - Each time any new patch comes in or any fix has been applied in any of the system components, regression testing needs to be done to ensure that any changes applied to the system does not impact any of the existing functionalities or cause any undesirable results from the system. During multiple releases, regression testing needs to be done whenever a new release is installed to ensure that the new functionality does not impact any of the existing functionalities.

• Integration Testing - Functional Integration testing is performed to verify proper execution of the entire application including interfaces to external applications. This ensures that the integrated components of the configured transactions and the development objects for the GAPs are functioning properly according to the requirements and specifications.

The objective is to perform the end to end process integration between all the SAP components and all external application systems are functioning properly. Functional Integration Testing ensures that all the business scenarios have been tested prior to the User Acceptance Testing.

• User Acceptance Testing - User Acceptance testing is conducted in by a group of business end users in order to validate that the system meets requirements relevant to their functional areas. This testing will ensure that the system is acceptable from the user’s perspective and is performing as per the requirement as well as the expectation from the users.

• Performance and Load Testing - The performance testing is performed to verify whether the performance of each operation is as per expectation. The objective is to verify the response time of the transactions under different conditions.

• Backup and Recovery testing - This is to test the system backup processes. Also the restoration process is verified here.

• Cutover Testing - This testing is performed to ensure that all the required activities (Data Migration, quality check, manual update and data synchronization) can be completed prior to go live within identified cut over window. The objective of this testing is to ensure that the data conversion, dependencies of cutover activities and timing match with the cutover plan.

• Pre Production Testing - Pre-production testing is to verify that the application and its interfaces can operate in the production environment. Its focus is on the operational aspects of the system but not a thorough functional test but a subset of it.

This testing is generally the final part of a testing exercise prior to go live.

Regards,

Rajesh Banka

Reward points if helpful.