Task: Conduct Smoke Testing

Smoke testing is performed to check the code quality at high level.

Purpose

The purpose of Smoke Testing is to ensure the code/build received from development is operable and stable enough to begin testing formally.

Relationships

Roles	Primary: QA Analyst	Additional: Development Lead Project Manager QA Lead	Assisting:
Inputs	Mandatory: Development Hand-Off Confirmation	Optional: None	External: None
Outputs	Smoke Test Confirmation

Main Description

Smoke Testing should be conducted in a Pre-QA/QA environment after development has successfully handed over to QA and the code/build is deployed to the QA environment. Smoke Testing should be successful in order for QA to begin any formal test cycles.

Steps

Conduct smoke testing

A group of testers will perform high level end to end tests to check the overall functionality of the system.

Smoke test results

Communicate the smoke test results to the appropriate stakeholders.

Properties

Predecessor	Hand-Off from Development to QA
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable

More Information

Guidelines	Defect Workflow

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