Testing challenges
Testing application workload can be a huge effort for users, developers and consultants alike. Also, things do not get easier on a large scale, especially for moving from one revision or SPS of SAP HANA to another.
The common approach to this is using customized scripts for database access or executing test scenarios in client applications. Of course, developing such scenarios and test cases is a large and therefore very costly development effort – all of it just to ensure the solution still works correctly with the new SAP HANA software.
For regression testing a new SAP HANA SPS across a whole system landscape with multiple application stacks the complexity increases even more since now the interoperation between SAP HANA and the various client applications or reporting tools needs to be tested. The outcome of all this effort are hand-crafted tests that may only resemble the actual workload to a certain degree.
Testing application workload can be a huge effort for users, developers and consultants alike. Also, things do not get easier on a large scale, especially for moving from one revision or SPS of SAP HANA to another.
The common approach to this is using customized scripts for database access or executing test scenarios in client applications. Of course, developing such scenarios and test cases is a large and therefore very costly development effort – all of it just to ensure the solution still works correctly with the new SAP HANA software.
For regression testing a new SAP HANA SPS across a whole system landscape with multiple application stacks the complexity increases even more since now the interoperation between SAP HANA and the various client applications or reporting tools needs to be tested. The outcome of all this effort are hand-crafted tests that may only resemble the actual workload to a certain degree.
