Hi, I have a question for the forum.  Has anyone explored having  test users and associated test data in PROD for the purpose of doing post-change validation.   Please advise with any information or ideas how to accomplish this.  

------------------------------
Mitch Simon
------------------------------

Hello Mitch,

Ideally. production is not meant for testing. Every testing has to happen in lower environments and the change/functionality needs to promoted to PROD.

My suggestion would be to refresh the PROD data in the lower environment immediately and perform the testing.

If you still want to have a testing in the PROD, You may have the dedicated org/site created for testing, so that it won't impact the working org/sites. Request to keep the test records creation limited in PROD.

------------------------------
Tinnokesh AP
------------------------------

As Tinnokesh AP says Production shouldn't be used for testing.

If there are problems then you risk corrupting the production data.

It also shows a lack of confidence in the release process.

The best way forward is to:

• Copy the production data to a non-production environment
• Implement the changes there
• Implement real world checks / processes
• Check the data / system in the non-produuction environment
  • You should gain confidence because the system is a recent copy of the production system
  • Any problems can be handled safely

------------------------------
Mark Robbins
Technical Design Authority / IBM Champion 2017 - 2025
Cohesive (previously Vetasi Limited)
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
------------------------------