Fiori is SAPs current-generation platform with a rich web-based user interface that is suitable for both desktop and mobile users. There are thousands of pre-built apps, and custom Fiori applications can be built using SAP’s UI5 framework. Fiori was first announced in mid-2013, but many SAP customers are deploying it for the first time in 2020. Load and performance testing helps SAP projects ensure that their new system can support their business-critical processes without being frustratingly slow, or grinding to a halt under heavy load.
Slow by default
While the Fiori user interface is more user-friendly for infrequent users, heavy users in the back-office are generally used to the speed of the desktop SAP GUI application. Fiori must be fully optimized for performance to be acceptable for these staff.
The default platform settings for any SAP system are suitable for a small dev/test environment, rather than a full-sized production environment. It’s nobody’s fault that the defaults are not performant, they will be updated as load and performance problems are found and notes are applied. There may be more pain depending on the amount of customization.
One component that requires optimization on every project is the Fiori Launchpad (FLP). Different tiles will be displayed to a user depending on their role and profile. Intelligently changing the tile settings can have a dramatic improvement on login times, and can reduce load on the back-end servers.
Load testing tools
Business as usual
Despite the additional scripting effort in load testing Fiori, it has much the same challenges as load testing on any SAP project.
- There will probably be integrations with other systems both SAP (SuccessFactors, Concur, Hybris, Ariba, etc.) and non-SAP (via EDI, etc.). Traffic from these systems must be accounted for in the load test.
- There will probably be a batch component. Data must be generated to measure the running time of the jobs. If an “overnight” operation mode has been set up, these settings must be verified too.
- There may be a cloud-based deployment…and it may be the organization’s first cloud project.
- It will be necessary to organizing bulk test data for volume testing (users, roles, and profiles, master data, etc.). It will be necessary to manage “use once” data like purchase orders that must be approved.
- It will be necessary to set up monitoring for key infrastructure components (NetWeaver, HANA, etc.)
- It will be necessary to work with different teams, from Business Analysts, to Basis, to the SAP MaxAttention team.