Important Concepts

Overview

<aside> 💡 Project Managers are especially encouraged to read this.

</aside>

This document details how QA Engineers interact with the process of creating a new build, but can also be applied to Support Projects.

A summary of the basic life cycle for a new project generally follows:

• Lay Foundation (Prep for the Project)
• Design (and Design Audit)
• Create Site Documentation
• Development
• QA
• Launch
• Support (or Closure)

Accordingly, this article will walk through most of those steps from the QA engineer’s perspective.

<aside> ☝ For an actual description of the build process, refer to ‣

</aside>

Foundation

<aside> 🔑 As mentioned in QA Engineers and Emergencies, QA Engineers are per-project, not per-team.

</aside>

• QA engineers are assigned to a project once the client signs off and the project begins.
  • When a new project starts, the Strategist and PM on the project determine who the lead QA Engineer will be.
  • Ideally the QA engineer should be involved as early as Discovery, so they know what they will be checking when, and understand the full context by the time they start testing stuff.
• QA Engineers have access to all projects within Cantilever so that we can easily cover for one another in case of emergency. However, QA Engineers unsubscribe from projects that they are not the Lead on so as to minimize unnecessary inbox notifications.
  • If a support or substitute QA engineer is needed to work on a project, the engineer must be tagged within a to-do comment thread to be notified of being needed within project. It would also be good practice to send them a message to ensure they've seen the assignment.
  • QA Engineers are also encouraged to check their List of Assignments to be aware of any tasks that may pop up unexpectedly.

Design Audit