| Work Product (Artifact): Smoke Test Confirmation |
 |
 |
|
Relationships
| Roles | Responsible: | Modified By: | |
|---|---|---|---|
Main Description
| Once Smoke testing is complete and there are no significant bugs/errors reported, QA Lead should send an email to Dev and PM about the outcome/test result(s). This email should be considered as an official communication/sign-off from QA. At this point code/build can be deployed to a formal QA env if Smoke Testing is done in a Pre-QA env and QA can begin formal test cycle(s) on the project. |
Properties
| Optional |  |
|---|---|
| Planned | |
Tailoring
| Impact of not having | No proper communication to the stakeholders about QA starting the test cycles formally. |
|---|---|
| Reasons for not needing | Required for all projects (in-house development) unless development and QA share the same environment for both development and testing purposes. |
Version and Release
Unified Life Cycle (ULC): 5.1, November 3, 2014 |