| Testing applications after applying a patch [message #95334] |
Tue, 22 July 2003 12:27  |
Anne Simms
Messages: 163
Registered: May 2002
Location: San Francisco, CA
|
Senior Member |
|
|
Does anyone have good documentation of testing Oracle applications like (AP, GL, CM, GL etc.)after applying a patch? Basically, what to test for in the applications after applying a patch.
Thanks
Anne
|
|
|
|
|
|
| Re: Testing applications after applying a patch [message #95387 is a reply to message #95334] |
Mon, 13 October 2003 09:35  |
john hebert
Messages: 5
Registered: February 2002
|
Junior Member |
|
|
Anne,
Patches and testing is a thorn in our side. We don't have any automated testing tools, so unless it is a one off patch that targets a specific issue, patching can turn into a project. We need to get multiple user areas to commit time to testing. Outside the context of a major upgrade or critical issue that isn't easy. (Receivables, Payables, and General Ledger staff aren't necessarily eager to commit to testing because Purchasing wants a patch to gain certain functionality.)
What we end up doing is reviewing the readme of each desired/needed patch and trying to see what modules are impacted and try to coordinate testing accordingly.
Anyway we rely on a combination of test scripts that users put together when we first upgraded from 10.7 to 11i as well as testing historically documented failure points. It is tedious and not necessarily comprehensive.
Oracle financials 11.5.3 left us very negative on oracle applications - the volume of patches/testing was overwhelming. For the last year we've been on 11.5.7 haven't had nearly the problems with the application. (Heck, I only have 4 'limited cross module impact' patches waiting to be applied. We also have the same number 'major cross module patches' that we simply won't apply - we will live with the problems until our next upgrade).
jh
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
