Large Scale Process

1. The PM asks Project Scheduling (Currently Adriane, GA, and Liam) to assign the project and set the ETA,
2. We verify that the correct materials have all been submitted (Project Profile, Dev Notes, Comps)
3. Project then goes through the proceeding steps to QA (Slicing, Integration, Internal QA)
4. QA then performs a first pass on the site generating content as necessary to fully test
   • This generally creates a ticket of between 10 and 30 issues to be resolved
   • These issues are created as subtasks of the Project Name - State - Front End Issues
5. That task is then assigned to Adriane to be assigned to Front End developer to fix (status changed to FE Pending Assignment)
6. The FE dev will identify issues that require BE, and will assign those to GA so he can have them fixed.
7. The ticket is then assigned back to me for Regression testing (making sure things are actually fixed)
8. Repeat steps 4-6 as needed to ensure all issues are dealt with
9. The QA Signoff ticket is marked complete and the PM is notified.

Specific Process

1. A notification will be sent from a FE dev when Internal QA is completed.
   
   • Liam will update the First Pass task to be marked QA - Assigned, which indicated it is ready to be worked on.
   • If the gap from the First Pass to the ETA is less then 5 days, notify the PM that the project could be late
2. Read and understand all functionality that is expected on the homepage. If you have any questions, ask the PM now.
3. Create a test page template
   • The page template should have:
     • Use the three column layout
     • All box widgets
     • Content filter widget
     • List view of your choice (I prefer the Staff as it has the contact popup that occasionally has issues)
     • Image Rotate Widget
   • Limit the Facebook and Twitter Box widgets to 1 item after making sure the repeating styling looks good
   • Update the Mobile view of the template to ensure that that is also working
4. Create an interior page with the template you have created
   • Use the test page content
   • Mark down any widgets that do not have content (RFPS and Jobs generally don't at the least)
5. Create all test items you will need, make sure you push the limits of the homepage
6. Follow the QA Guide and QA Checklist to make sure that you have checked everything. Generate a wrike task for each issue.
7. Assign the Front End Issues task to Adriane and set it's status to FE pending assignment.
8. Update the First Pass task to be "QA - Verified" and change the "Quality Assurance Testing" parent task to "QA - In Progress"
9. When the ticket comes back, make sure all issues are resolved
   • If they are not, assign back to the Front End developer working on the ticket
10. Once all issues are resolved, notify the PM and Project Scheduling, the QA phase is done