SAP landscape is huge and volatile. Support packs and patches are regularly applied to any installation so also migrations, upgrades & EhP. It is important that despite these, the mission critical business processes are not affected in any way.
Many times SAP testing cycles get shortened or reduced due to release pressures even though testing is business critical. We often run the risk of low test coverage due to unavailability of bandwidth.
As per the 2008 Panorama ERP reports, the cost of testing activities is between 30-45% of a global SAP deployment project and around 80% of a migration project. Also, around 93% of the ERP projects are extended and only 35% are within budget.
Efficient test automation and developing re-usable components is the key to mitigate the above issues. However, following are some of the primary concerns which arise because of the way SAP test automation is mostly done:
– Creation of automated test cases is time consuming and expensive to maintain
– Requires special programming skills by QA specialists
– The automated test scripts get damaged by changes and require time consuming repair effort
In this blog series, I will discuss a few key SAP test automation challenges and then list out approaches to address these challenges. I will consider HP QTP for our discussion based on its popularity for SAP test automation, but the challenges are applicable irrespective of the tool selected.
I will also share with you a few practical examples that will help you better appreciate these issues. To keep this discussion interactive, please do drop in your thoughts and experiences on the challenges you faced and how you have overcome them.