CTP Coordination between Prod, Test and Dev

 3 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Dean Rochester
New Member Send Private Message
Posts: 0
New Member
Hi All
I have read the few threads related to CTP best practices... but there is a question I do not see an response to...

What is the best practice for coordinating CTPs between Prod, Test and Dev?

mark.cook
Veteran Member Send Private Message
Posts: 444
Veteran Member
We utilize a standard change control process. We put patches into DEV for individual unit testing, once successful and email or documentation of the successful test, allows us to put in CERT for integrated testing. Sign off there allows for a IT ticket to be entered to track the change to the system. This IT ticket ties the testing results to the change for audit purposes.
Dean Rochester
New Member Send Private Message
Posts: 0
New Member
“what if the CTP (procurement) is applied in test per user request but the user doesn’t have time to test it right away, so it sits in test untested. And another CTP for a different suite (like PR) is needed in test. Do they allow the users a certain amount of time to test and then if not tested by the end of that time, the CTP is uninstalled?”
mark.cook
Veteran Member Send Private Message
Posts: 444
Veteran Member
We have taken the approach of letting it sit. We have mulitple product lines in DEV so they don't impact each others unit testing.

We try to coordinate in that manner, then in CERT (our pre-production integrated test productline) we do patch preview, send out the changes that need to be validated to all. If they can't agree on the timing, them we escalate to the directors of each area to determine timing. We will uninstall in CERT if it will not match PROD for an extended period of time.

I should say DEV and CERT are different LPARS which also lets us do the same type of testing with ESS/RSS changes