Hmmm - sounds similar to Post Production Testing - this is a term we use to run a smoke/sanity test to verify that what we promoted to our production region is working and is a okay.
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!
Its a set of tests designed to verify that the software installed correctly in production and operates correctly in production. The level that you can test to will have logistical and operational limitations but you should try to do as much as possible, especially examples of pushing through end-to-end transaction.
In the old days we called this installation and set to work.
No, the focus is far more technical, in that does it function correctly in the production environment, did the install/configuartion work properly prior to going live.
Where this gets confused is in a greenfield installation where a product is UAT'd in the target environment. even in this case the data has to be cleared out and may require re-configuaration before going live.
Robert, I agree with you on this one. It also must verify that the application can coexist with other applications running in that target system, for example. Any time you install any software it is recommended you perform a product verification test, even on your PC, and to never install many new applications at once so that you cannot go back to the previous proven configuration. What you need to do is to perform a basic UAT test to process a reasonable proxy of your future usage, which may not be according to what the vendor had in mind when they wrote the software. And more to Robert's point, make sure you backup before you start so that you have something to recover to if the new application does not work out.