Tricentis’ Director of Load Testing, Tim Koopmans, recently delivered the following talk at SAP SAPPHIRE…
SAP Fiori and User Experience
SAP Fiori has recently placed a lot of emphasis on the user experience. User experience is a term we are all familiar with, but let’s look at what it really means using an example that has nothing to do with software: ketchup.
Heinz’s classic ketchup bottle design – the elegantly shaped glass bottle ubiquitous to so many retro American diners – does not provide for a great user experience. If you have tried using one before, you probably found yourself shaking the bottle, then tapping it, then banging on it, before finally scooping out the ketchup with a knife.
Heinz’s updated ketchup bottle design is made with user experience in mind. The bottle is plastic so you can apply pressure to squeeze the contents out, and the entire bottle is inverted so it stands on its head, collecting the ketchup to the mouth of the bottle.
Ketchup has different properties than other liquids, such as water or oil, however. Even in a bottle optimized for user experience, the user still needs to be aware of the attributes that physics that affect the ketchup – like applied pressure and gravity.
…and Load Testing
Now, what does any of this have to do with load testing?
In load testing, we are always asking ourselves, “what can go wrong?”. Load testing is about identifying and managing risk to applications in production. How does that apply to performance?
The thing about performance is that everyone cares about it. We all have an intuitive feel for response time – and know the pain of when an application, SAP Fiori, for example, does not meet those expectations. This is super frustrating for people who may be relying on these applications to do their job, but find instead that their work is constantly bottlenecked by application performance.
Besides response time, there are other aspects of performance that we care about: concurrency (how many people can use an application simultaneously), transaction rate (how many orders you can process per second), availability, reliability, and scalability.
If you go to the marketecture part of the SAP Fiori website, there are some big hints there that you should be considering load or performance testing. The page talks about planning system landscapes, system requirements, a server calculator, and more. How are you supposed to make sure those system landscapes, requirements, and server configurations are working though? You can’t just plug it in and hope it works. You need to test them, ideally in a development and production environment, to make sure they are performing as needed.
And that’s exactly what you can do with Tricetis Tosca Flood. SAP Fiori promises great user experience on multiple devices, but Tosca Flood promises great performance on many devices. We do that by distributing load across multiple cloud-based resources, simulating the load of hundreds and thousands of users from around the world. Tosca Flood also helps you find bottlenecks before your customers do, and enables you to build reusable test automation. Basically, you can build your automated tests on a functional level, and then reuse them on a performance level, with no re-scripting or team silos involved.
The thing about load testing though is that it’s not a one-off activity. If you only test your application performance once or twice a year, there is a high likelihood that you are shipping a poorly performing product. Instead, you want to be executing continuous load testing, which integrates load and performance testing to equal importance as functional, regression, and end-to-end testing. As the industry’s #1 continuous testing platform, Tricentis Tosca and Tricentis Flood are equipped to help you enable continuous testing of all kinds on your application.
Watch Tricentis’ Director of Load Testing, Tim Koopmans’ full talk at SAP Sapphire here: