Are you doing SAP testing? Is it manual or automated? I am working on SAP lately and trying to understand typical challenges related to SAP functional and performance testing, testing of SAP installation and configuration. I am interested in anything you can throw at me (MDM, EP, PI, SCM, SRM, BI).
I posted a similiar question ... SAP is a unknown entitiy to me and I would love to know if there is anyone out there that is an expert SAP tester or test manager.
I don't know whether this really fits but one of our customers is automating a SAP WebDynpro (functional testing via GUI) application. He tried using the eCATT SAP testing tool first which did not work for his application. So he switched to web2test. For certain components he needed to implement resolvers to identify them but succeeded in automating the testing of his application.
Unfortunately I have no information whether eCatt works well for the automated testing of other WebDynpro or different SAP applications. According to the SAP homepage: "eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java".
Ok let us push eCATT aside, the framework for an SAP testing is still not clear to a lot of people out there. There is massive dependence on systems integrators to advise and provide scenarios and test steps for testing to be conducted and completed. This is not useful for the implementing organisation knowing that there would be a lot of interest in ensuring all deliverables are dropped in timely fashion. We independent testers need to do more research and background work in factoring what sort of scenarios are required based on the requirement and not forgeting the SAP process knowledge to be applied.
I particularly find help.sap.com very useful in understanding processes then apply it to those areas of implemented modules.
I have been testing SAP ECC for the past 26months and its quite fair to say that eCATT is not your ideal solution.
Most of the functional testing you could do manually as long as you know what your scenarios are. One of the best approach is to have Transaction user guides (TUGs) to support your test scripts then you can execute what the business really want at the end of the day. The TUGs will detail of the generic screens while executing a transaction for example MIGO (Goods movement) and you can have the testscript with steps referencing sections of the TUGs.
Performance testing is an issue if you do not have automated too like LoadRunner.