Unit testing is a type of testing that involves testing a single unit or group of units. It is performed by domain and configuration experts who know the functionality of each unit in a system, to test the functionality of a SAP system and its various components.
Suppose the task is to create a sales order and save it. To perform unit testing for this task, the tester should know that the sales order can be saved using the SAP organization elements like customer master data, partner functions, material master data, company code, credit control area, sales organization, etc.
In ABAP development, Unit testing can be performed to check if a report can be created from developer-generated data. It requires assistance from the domain expert.
System testing involves testing the enire system as per the requirement and specification. It is the the integration of elements of a SAP system to ensure that related SAP functionality are linked together in the development environment.
If you say a cash flow for a quotation in an organization would show that a quote can be used to create a sales order, a delivery can be created and processed from the order, the delivery can be billed, the billing released to accounting, and a customer payment applied against the accounting invoice.
Each unit is tested like this and then the test results are combined using system testing.
Scenario testing is performed as per specific business cases.
Suppose there are a few tasks that are specific to a customer segment or a given product line or a set of services. For these specific line of target, you have different scenarios that you need to test. This testing is also performed in the development environment.
This testing method is used when multiple systems are combined together to test the output of the integrated system. In this testing, testing data comes from a real data extraction source. Data is known to business end-users.
Interface testing ensures that a business process on a SAP system runs automatically, the events are triggered, and the results are transferred to the receiver system. Interface testing involves execution on the sending system followed by automatic generation of the interface output, and then the receiving system consuming that file and proving that a business process continues on the receiver.
Ideally, interface testing involves larger testing activities as a project progresses. Interface testing shows that triggering works, the data selection is accurate and complete, data transfer is successful, and the receiver is able to consume the sent data.
This type of testing is used to ensure that the end-users are able to perform the assigned job functions with the new system. The important aspect of this testing is to understand the business requirement and to ensure that the expected features, functions and capabilities are available.
Performance testing checks the following aspects −
Performance testing identifies bottlenecks and coding inefficiencies in the SAP system. It is not likely that system performance tuning is perfectly set up and the program is running with optimized code.
Load Testing id done to test the load handling capacity of the system. Here, the tester applies maximum load on a system, either online users or periodic batch processing, and identifies whether the system is capable enough to handle the load. If not, it finds out the steps needed to improve performance.
This type of testing is used to ensure that users are only able to execute transactions and access appropriate data that is relevant to their project.
As with the implementation of Security standards, this is really important to test if security and authorization is placed in a system. Test IDs for job roles are created and used to both confirm what a user can do and what a user cannot do.
Cutover testing is usually performed once in a project lifecycle. Here a full-scale execution is done of all the tasks involved to extract data from legacy systems. Then, to perform any kind of data conversion, load the results into the SAP system and fully validate the results, including a user sign-off.
Regression testing is used to find new functionalities and to test previous functionalities in a system when it is upgraded or a new system is set up. The key role of regression testing is to test the existing functionality and newly updated configuration and codebase.
When you upgrade your SAP system or apply a patch, it shouldn’t affect the functionality that is expected to be performed by the users. In addition, it should not affect the new features that are supposed to be introduced in a new release.
SAP Testing Related Interview Questions
|SAP CRM Interview Questions||SAP SD Interview Questions|
|SAP CRM Functional Interview Questions||SAP FICO Interview Questions|
|QTP Interview Questions||Manual Testing Interview Questions|
|SAP FI Interview Questions||Database Testing Interview Questions|
|Automation Testing Interview Questions||Software Development Lifecycle (SDLC) Interview Questions|
|Test Estimation Interview Questions||Test Manager Interview Questions|
|HP QuickTest Professional Interview Questions||Test Plan Interview Questions|
All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.