We are currently creating a test-plan for one of our new systems. As such we are looking for the right term to describe the following
<xxx>test takes place immediate after the deployment on production. It covers the vital functions of the system and the new release. But it will only skim these functions, as they have been thoroughly tested before during internal test and UAT phase.
Aim of this test is to assure that
- the new features are available
- old core features did not break
We are considering
In computer programming and software testing, smoke testing (also confidence testing, sanity testing) is preliminary testing to reveal simple failures severe enough to reject a prospective software release. A subset of test cases that cover the most important functionality of a component or system is selected and run, to ascertain if crucial functions of a program correctly work. When used to determine if a computer program should be subjected to further, more fine-grained testing, a smoke test may be called an intake test.
I have set the part that matches our scenario to bold. What hinders us to use this term is that this kind of test shall take place before the actual release on production.
The Operational Qualification Protocol is a collection of test cases used to verify the proper functioning of a system. The operational qualification test requirements are defined in the Functional Requirements Specification. Operational Qualification is usually performed before the system is released for use.
We are not sure if this is the right term either. For one as it is taken from the validation aligned with 21 CFR Part 11 and for the other that it lacks the character of a rough test.
The Production Test takes place immediate after the deployment on production. It covers the vital functions of the system and the new release. But it will only skim these functions, as they have been thoroughly tested before during internal test and UAT phase.
This would be to roll our own definition. As we have not found a source that defines this kind of test ... or probably our google-fu just was not good.