be_ixf;ym_201911 d_22; ct_200
SAP - Agile Testing

SAP/Packaged App Testing

Testing SAP Fiori for SAP S/4HANA: Are You Up for the Challenge?

SAP has stated that “most of the business innovations of SAP S/4HANA — those that bring the best digital transformation benefits — are delivered in SAP Fiori.”  However, ensuring that the “SAP Fiori experience” is a positive one requires testers to address a new set of challenges in the already-complex domain of SAP test automation.   Here are the top SAP S/4HANA testing challenges.

The Top 5 SAP S/4HANA Testing Challenges 

1. Complex Infrastructures 

Let’s face it: SAP can be quite complex. SAP transactions typically span multiple SAP and third-party components and encompass a variety of technologies, including your own custom code. This complexity can make it difficult to track and test changes across the entire landscape. 

2. More Frequent Releases 

SAP used to have one or two new releases every year, but that’s changing. With S/4HANA, SAP delivers new releases on a quarterly or even monthly basis, and more frequent releases require more rapid and more frequent testing. Specifically, every time SAP delivers a new release, your team needs to ensure your updated system is working and stable – and you need to do so in a very short timeframe to ensure your business processes are not at risk. 

3. Overloaded Business Users 

Business users have little time to do manual testing, but they are often the ones tasked with ensuring business processes work after an update. The landscape of complex infrastructures and the need to test new releases quickly and frequently only exacerbate this challenge. 

4. Version Control 

SAP is increasing the frequency of updates for both S/4HANA and SAP Fiori. Within the past few years, we’ve seen SAP Fiori release versions 1.38.x, 1.44.x, 1.52.x and S/4HANA release systems 1511, 1610, 1709, and 18xx. This creates challenges when your organization decides to upgrade either S/4HANA or Fiori, as it raises questions around whether work done for one will carry over to the other. For example, every time you upgrade S/4HANA, you need to ensure your Fiori test cases remain valid and that your regression portfolio stays intact. Depending on the changes in the update, you may need to rebuild from scratch. 

5. Technical Obstacles for Test Automation Tools 

Finally, SAP Fiori presents many technical obstacles for test automation. When automating SAP Fiori testing, these obstacles include: 

  • A lack of standard HTML controls 
  • Presence of multiple technologies, including SAPUI5 Native and WebDynpro 
  • Massive amounts of data stored on a single page, which can get unwieldy 
  • Movement or changes in objects with every release, creating an inconsistent environment and overall experience 
  • Highly dynamic IDs for objects, since the ongoing changes mean that what worked yesterday could stop working at any time 
  • Regular updates to control libraries (e.g. buttons, drop downs), once again due to the ongoing changes in the system 

Combined, these challenges can make it very difficult to maintain your regression test suite – especially if you don’t have the right test automation strategy in place. 

Making Your Migration A Success 

The challenges associated with testing SAP Fiori are very real, but with the right processes and tools, they’re not insurmountable. It’s critical that organizations start upgrading their quality processes now, both to reduce business risks and to meet the needs of SAP’s accelerated release timelines and increasingly complex infrastructures. 

Watch the webinar, Testing SAP Fiori for SAP 4/HANA: How to Solve the Top Challenges, to learn more.