Once development has been completed, you can test the solution in the test subaccount that you have previously set up. The software components that make up the solution are imported into a provisioned test system, while any additionally required configuration has to be carried out by you. This may entail creating suitable business roles, maintaining communication arrangements, or other administrative tasks performed via the SAP Fiori launchpad of your ABAP system.
You can also use a CI/CD server and a Jenkins pipeline to automate the test process. This allows you to schedule regular tests and to be notified as soon as issues arise within the solution.
If the solution is successfully tested and works correctly, you can proceed with the add-on build.
- For testing in SAP Fiori launchpad in your ABAP environment, you need a business user in the test system that has the required authorizations to use the Manage Software Components app as well as authorizations that are required as a test user.
- For testing in the ABAP Test Cockpit, you need a developer user using ABAP Development Tools. See Getting Started as a Developer in the ABAP Environment.
- (Optional) For running ATC checks as part of the ABAP environment pipeline, you have to create a pipeline in a Jenkins CI/CD server that is provisioned using the Cx Server tool. See Jenkins and Cx Server.
Import Software Components
Before testing new developments in a software component in the test system, as an add-on admin, you have to import the latest changes from the remote repository. After you have cloned a software component into the test system TST, you can import the latest changes by pulling the software component in the Manage Software Components app. See How to Pull Software Components.
Create and Assign Business Roles
Before creating and assigning business roles, you have to make sure that business users are already available. They can be created manually or automatically. See User Provisioning.
To test the developed business services, as a test user, create business roles from the role templates in the test system and assign them to your user. See Maintain Business Roles.
Create Launchpad Space and Pages for Business Roles
To enable navigation to custom UIs via tiles, enable launchpad spaces and pages. Add spaces to the relevant business roles and add the needed SAP Fiori launchpad tiles to those spaces. Finally, enable spaces for business users in the system launchpad settings. See How to Create Spaces and Pages for a Business Role.
Create Communication Arrangements
To test inbound and outbound communication, create communication arrangements in the test system TST based on the implemented communication scenarios. See How to Create a Communication Arrangement.
Depending on whether you want to use an authentication method for outbound communication that requires a business user context (Oauth2 SAML Bearer Assertion, Oauth2 User Token Exchange, JWT Principal Propagation), you need to configure a destination in a communication arrangement instead of maintaining credentials by using an outbound communication user. SeeSupported Protocols and Authentication Methods and Creating a Destination.
You can integrate the test system TST with on-premise systems. See Integrating On-Premise Systems.
In the subaccount of test system TST, the subaccount for testing, you can assign the Cloud Connector administrator role collection to the Cloud Connector administrator user to operate the data transmission tunnels used by the Cloud Connector.
Create Business Configuration
As a test user, you can adjust business configuration objects in the Maintain Business Configurations app to change and influence the system behavior. See Custom Business Configurations App.
Configure Key User Extensibility
Key user extensibility that is enabled in the SaaS solution can be configured and consumed in test systems.
Key user extensibility provided in a SaaS solution can only be configured in tenants of particular types, for testing purposes in tenants of type Test Tenant.
These tenant types are provisioned in non-development systems, such as test system TST or quality assurance system QAS, where development is not allowed (
is_development_allowed = false). The tenants are created independently from a subscription to the SaaS solution by using the Landscape Portal application. See Manage Test Tenants.
As a test user in a Test Tenant (client >= 200), you configure key user extensibility in a test system.
- See Custom Logic (Deprecated) for guidance on how to use the Custom Logic app to create and maintain custom logic for business add-ins (BAdIs).
- See Configuring Predefined Custom Fields for guidance on how to configure predefined custom fields to customize applications and their UIs.
With the ABAP Test Cockpit, you can run a set of checks (check variants) on software component or package level. See Checking Quality of ABAP Code with ATC and ABAP Test Cockpit in the Cloud – What is already possible.
To fix and revalidate ABAP Test Cockpit findings, as a developer user, you can run ABAP Test Cockpit checks on developed software components explicitly via ABAP Development Tools in the DEV system. See Launching ATC Check Run from the Project Explorer and Launching ATC Check Run Explicitly.
If transport blocking in case of ABAP Test Cockpit findings is configured (see Set Up Add-On Development), ABAP Test Cockpit checks are executed implicitly. See Launching ATC Check Implicitly.
ATC Exemptions
If you can't clear an ABAP Test Cockpit finding by correcting the underlying problem, you can still clear it by requesting an exemption. Exemptions are created as part of a specific software component. See Working with ATC Exemptions.
Continuous Testing using ABAP Environment Pipeline
For in-depth information about the ABAP environment pipeline used for continuous testing, see ABAP Environment Pipeline.
To schedule a regular execution of ABAP Test Cockpit checks for a software component in the test system, you can use a CI server and pipeline to automate this process. You can reuse the previously described setup of a transport from development to test system using the ABAP environment pipeline. See Set Up Transport from Development to Test System.
As a DevOps engineer, configure the ABAP environment pipeline by using a static and preconfigured system. With the pipeline, the following steps are then automated, triggered by the pipeline execution of a Jenkins administrator:
- Pulling the specified software components/Git repositories
- Running the configured ABAP Test Cockpit checks
The continuous testing scenario of the ABAP environment pipeline is described in detail in Continuous Testing on SAP BTP ABAP Environment.