Artifact: Smoke Test Confirmation

Notification to development to indicate a successful smoke test.

Relationships

Roles	Responsible: QA Analyst	Modified By: QA Analyst
Tasks	Input To: Execute Testing	Output From: Conduct Smoke Testing

Description

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.

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
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014