"UAT Stage - deploying Docker Images to UAT Environment, running Smoke Tests, so that then QA Engineers can do Manual QA Testing."
If I only run UAT stage on a docker image that has only passed acceptance stage. Then do we still need to do smoke test? because acceptance stage will do it anyway in acceptance envirā¦
"UAT Stage - deploying Docker Images to UAT Environment, running Smoke Tests, so that then QA Engineers can do Manual QA Testing."
If I only run UAT stage on a docker image that has only passed acceptance stage. Then do we still need to do smoke test? because acceptance stage will do it anyway in acceptance environment. Then running them again in UAT stage or other stages is like running same test twice. Can we skip that?
Good question. Yes, for Smoke Tests we do it per environment. So this means:
- When we deploy to Acceptance Environment, we run Smoke Tests on Acceptance Environment
- When we deploy to UAT Environment, we run Smoke Tests on UAT Environment
- When we deploy to Production Environment, we run Smoke Tests on Production Environment
(If we have additional environments, such as Security Testing Environment, Performance Testing Environment, as soon as we deploy, we run Smoke Tests)
--------------
"If I only run UAT stage on a docker image that has only passed acceptance stage. Then do we still need to do smoke test? because acceptance stage will do it anyway in acceptance environment. Then running them again in UAT stage or other stages is like running same test twice."
Exactly, we are running the *same* test on *different* environments.
"Can we skip that?"
Cannot skip, because of environment differences. There might be non-intentional environmental differences, whereby the Smoke Test passes on Acceptance Environment, but fails on UAT Environment, or fails on Production Environment.
So just because the Smoke Test passes on one environment, it does *not* mean that it will pass on the other environments, that's why we run it per environment, to know that the application is up-and-running on each environment.
Hi Valentina, a question :
"UAT Stage - deploying Docker Images to UAT Environment, running Smoke Tests, so that then QA Engineers can do Manual QA Testing."
If I only run UAT stage on a docker image that has only passed acceptance stage. Then do we still need to do smoke test? because acceptance stage will do it anyway in acceptance environment. Then running them again in UAT stage or other stages is like running same test twice. Can we skip that?
Hi MY,
Good question. Yes, for Smoke Tests we do it per environment. So this means:
- When we deploy to Acceptance Environment, we run Smoke Tests on Acceptance Environment
- When we deploy to UAT Environment, we run Smoke Tests on UAT Environment
- When we deploy to Production Environment, we run Smoke Tests on Production Environment
(If we have additional environments, such as Security Testing Environment, Performance Testing Environment, as soon as we deploy, we run Smoke Tests)
--------------
"If I only run UAT stage on a docker image that has only passed acceptance stage. Then do we still need to do smoke test? because acceptance stage will do it anyway in acceptance environment. Then running them again in UAT stage or other stages is like running same test twice."
Exactly, we are running the *same* test on *different* environments.
"Can we skip that?"
Cannot skip, because of environment differences. There might be non-intentional environmental differences, whereby the Smoke Test passes on Acceptance Environment, but fails on UAT Environment, or fails on Production Environment.
So just because the Smoke Test passes on one environment, it does *not* mean that it will pass on the other environments, that's why we run it per environment, to know that the application is up-and-running on each environment.