You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now

To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered.
For more information, please refer to this announcement explaining best practices for getting answers to questions.

Testing Fusion HCM Talent Patch Releases

edited Apr 27, 2016 7:16PM in Performance Management 2 comments

Summary

Looking for best practices in monthly patch testing

Content

I'm trying to understand how Fusion Talent, Performance, or Compensation customers are testing their monthly patch releases.  Are you using a risk based approach testing only critical functions?  Doing full regression testing? No testing other than for patches relevant to your usage?   Currently we are fairly spare with our testing, doing very targeted tests each month. What do you do for monthly testing?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!