A.The idea is to simulate a typical user workflow. An automated web browser clicks through the application's web interface and verifies that the expected screens appear. Tests at this level show that the application's features work. However, these tests are expensive to create and run because, for example, interacting with the browser consumes many resources. In addition, it is usually difficult to specify the interaction with the browser so that it can handle minor changes in the structure of the application's user interface.

B.They have the smallest granularity. They can be defined directly at the programming level, for example by calling methods of your Java classes. Dependencies on other modules or systems can be mocked to ensure they run quickly and test only the code under test. These tests are usually inexpensive. You should use them to verify that your software modules, such as classes, behave as expected.

C.They are run when the application is deployed to production, to verify that the deployment was successful.

D.They have reduced complexity. They skip the user interface and work directly on the defined backend APIs. They test the integration between software modules or systems. Although they have reduced complexity, they still have medium cost. They still have overhead, such as network communication or spawning a small server to make the backend APIs available. You should use them to verify that your backend services can communicate with your SAP S/4HANA system and to test that the services behave as the user interface expects.

A.Based on business library best practice forms

B.As a copy of an SAP standard form

C.Based on an existing data source (SOAP)

D.Based on an extended OData service using already existing fields and associations from published CDS views

E.Based on an existing data source (OData service)