A. Space
B. Subaccount
C. Organization
A. Heterogenic
B. Tightly coupled
C. Monolithic
D. Highly distributed
E. Monolithic
A. Maven
B. Node.js Packet Manager
C. SAP Cloud SDK
D. GitHub
A. performanceTests
B. failThreshold
C. staticCodeChecks
D. dockerImage
E. checkJMeter
F. testPlan
A. 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.
B. 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.
C. 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.
D. They are run when the application is deployed to production, to verify that the deployment was successful.
A. Do performance testing
B. Enable more logging and traceability features along deployment
C. Detect violations of relevant quality standards and SAP guidelines
D. Increase deployment cycles
E. Rapid delivery of extension app projects
A. 1) Configure Hibernate for multi-tenancy2) Configure a data source3) Persisting and accessing the data4) Tenant onboarding and offboarding
B. 1) Configure a data source2) Configure Hibernate for multi-tenancy3) Tenant onboarding and offboarding4) Persisting and accessing the data
C. 1) Tenant onboarding and offboarding2) Configure a data source3) Configure Hibernate for multi-tenancy4) Persisting and accessing the data
D. 1) Configure Hibernate for multi-tenancy2) Configure a data source3) Tenant onboarding and offboarding4) Persisting and accessing the data
A. Communication Arrangements
B. Other UIs
C. Reports
D. Service interfaces
E. Business Scenarios
F. Forms
A. The watch feature, which automatically redeploys Javascript upon changes in the source code.
B. The debug feature, so you can set breakpoints and stop program execution when required
C. The ability to use either JavaScript or TypeScript
D. The watch feature, so when you change the source code of the running application this is automatically recognized, the application is automatically rebuild and restarted.
E. The ability to use Java and JavaScript
A. Loose coupling with core business processes
B. Reduction of complexity through a single IT provider
C. Strict tool-based approach
D. Software lifecycle of extensions coupled to stable systems of records
E. Monolithic Architecture