QA Task Structure

Quality Assurance Testing

This task is used for the QA Manager (or as is current, Liam). It is the length of the QA process and the end is generally 1 day before the final ETA. It provides visibility into what projects are in QA (if they aren't all being done by one person).

It will generally start in "Pending Assignment" and will be changed to "QA - Scheduled" when the project is scheduled.

It will be change to "QA - In Progress" once the "First Pass" task is complete.

It will be changed to "QA - Verified" once the whole QA process is complete.

First Pass

This is where time will be recorded for the initial building of the list of issues.

After scheduling it will be set to "QA - Scheduled". Once Internal QA is completed, the task will be set to "QA - Assigned" which indicated the project is ready to be started in QA.

This should generally take about 4 hours.

Fixing Issues

This task is for the person working on the QA task. They will assign themselves to it when they have finished the first pass. This is also where they will record their time as the review and check the issues they have found.

Back End Issues

This will be used by the BE team if there are any issues for them. The frequency of this being used has gone down over the last couple years, if there are no tasks at the end, please mark as "Omitted".

Front End Issues

All issues found initially will be created as subtasks of this project. The FE devs will generally assign and move issues to BE Issues if they require BE input.

When the full list of subtasks is made, assign this task to Adriane, and change the status to "FE Pending Assignment"

QA Signoff

Once all the proceeding tasks are completed, mark this as "QA - Verified" and notify the PM and Project Scheduling. Adjust the date to whatever the final day was.