We have a small list of smoke tests we perform on Saturday morning following a CU. These tests ensure all Supply Chain Warehouse functions can continue throughout the weekend. If there was going to be a problem with RSS, MSCM, and Warehouse/Inventory we would identify it through these tests. However, this does not cover Purchasing functions which start early on Monday morning. For Purchasing we just react if a problem is identified by end users. The other tests in this document ensure some basic needs are working such as ISD, cubes, Async, scheduled jobs, Birst, configurations, and personalizations. We do not get into testing for other areas of the business because it would require several hours on Saturday. We complete these tests and feel good enough that no incidents need to be created right away. Then we keep our fingers crossed for Monday morning as other areas of the business open up. Usually, we have a few reported issues. A year ago we were almost guaranteed to open two or three new tickets on what we call, "CU Monday." I would say things have gotten better though and we may create one or two or none. Sometimes we just reset a personalization to solve a problem or it is end users seeing some new layout changes for the first time. CU77 was actually low impact and didn't result in any new tickets being created. We would really like to be able to do a better job of communicating layout changes though before they are seen in PRD. It is hard to know what those changes would look like via the release docs. It would be so much easier if there was a website we could visit to see before and after screenshots with no configurations and personalizations, so we can show those to our end users.
