12-08-2009 3:05 PM
Dear Security Experts,
Our security team will be doing an update to our 7.0 SAP version to implement another SAP Support Pak, and any patches, they want us to test every transaction before and after, as a user I think this is unnecessary, SAP must give a way to ensure everything is working fine before and after, how would you be able to test any customize tcode, batch jobs, customized reports etc...
Your suggestion will be greatly appreciated,
Regards,
Frank
12-08-2009 3:13 PM
Two usefull approaches (which can be used in combination) are to use eCATT test cases for the recordable scenarios and use the switch framework to test your existing configuration, upgraded roles in SU25, etc, etc on the SAP updates, and then selectively switch your own business enhancements off to isolate the origin of any errors or difference in behaviour (some of which will be intentional..).
Cheers,
Julius
12-08-2009 3:53 PM
Thank You Julius,
I have used ECATT before to update fields, but not sure how this will help for this instance can you elaborate more?
Thank You,
12-08-2009 4:15 PM
Pretty much the same, except it is in the TEST system and not in PROD...
It also doesn't relieve the users completely from their testing responsibilities, but you can club the lion's share of the boring repetitive stuff with it.
CATT = Computer Aided Testing Tool.
Cheers,
Julius
12-08-2009 5:18 PM
Although you can automate some of the tests using ECATTs, there really is no getting away from the fact that you just need to perform regression testing.
You certainly cannot just take SAP's word that the patches will all work fine as they will not be able to test for every eventuality that a client may come across.
You can get a good idea of what is likely to be impacted through the list of objects which have been updated (SPAU list).
You will need to execute as much testing as you think will give you sufficient coverage on your key functions as with any key change to your system.
Simon