This question already has an answer here:
After running our normal automated tests against a test area, we releasing the change to production then run some additional tests against production to verify the roll-out ran correctly and to test some conditions that we can reasonably duplicate in testing. This testing is intended to catch errors after they are released, but before too many users see them.
Is there a standard term for this testing? I'm tempted to call it a smoke test, but that term is already used for testing packages.
Looks like this a duplicate of: