Website Quality Assurance Task List

Complete Pre-Launch Checklist

During the QA process, Support, MM, CSM, and CSM Team Lead must all four review the site before it is approved to launch. DO NOT confirm a launch date with the customer unless you have received approval to launch from CSM Team Lead.

Here Are the Steps to Completing the Pre-Launch QA Checklist & Getting Team Lead Approval to Launch:

Support Team:
  1. Create a copy of the appropriate QA Process Workbook from Sharepoint for the new customer. 

    1. BB & HIL QA Workbook
    2. VR QA Workbook.
  2. Before you begin the QA, please copy the Device QA Document (via this link) and provide any feedback here.
  3. Start your QA at the homepage by comparing to the approved mockup.
    1. Anything you see that’s “wrong” or not in line should be noted in the above document.
  4. Review the site like a user and make sure you move through all appropriate conversion funnels easily.
  5. Address them yourself or note them in the Device QA Document.
  6. @ chat the MM, the CSM, and the CSM Team Lead in Jira that you’ve completed your QA. 
    1. This comment should include the QA Workbook and the Device QA Document. 
  7. Initial and date the Onboarding Project Management Sheet for this customer.

MM:

  1. Open the QA Workbook and Device QA Document, found in Jira.
  2. Ensure all pages have the appropriate calls to action for the content.
    1. Things to do: Vacation Guide
    2. Accommodations/Rentals: Book Direct Language
  3. Review the site like a user and make sure you move through all appropriate conversion funnels easily.
    1. If you note any new issues not documented, note them in a different color on the Device QA Document.
    2. Resolve any top/mid/low-funnel conversion-hindering issues prior to website launch.
    3. Make sure all menu items are optimized with SEO in mind.
  4. @ chat the CS team member to address any front-end or back-end issues with the DEV team. CC: the CSM and the CSM Team Lead to keep them in the loop. 
  5. Initial and date the Onboarding Project Management Sheet for this customer.
CSM:
  1. Follow up in Jira if you have not been @ chatted to check on the status of any updates.
  2. Review the site high-level to ensure there are no development issues, calls to action missing, etc. – once the CS team member @ chats you in Jira.
    1. You should not find any issues.
    2. If you do, comment at the CS and MM team members in the QA Workbook to re-complete certain sections of the QA.
  3. Alert the CSM Team Lead to review the site in the Jira ticket.
  4. Initial and date the Onboarding Project Management Sheet for this customer.
CSM Team Lead:
  1. Once this task has been assigned to you, review the website for issues. Cross-reference the Device QA Workbook, as needed. 
  2. Post any items to address in the comments and @chat the CSM and CS team members in Jira and have them coordinate with DEV. 
  3. Once all items have been addressed and the site is free of issues, grant finall approval to launch
After CSM Team Lead approves the site to launch, CS and CSM may move forward with scheduling a launch date with the customer.

Pre Launch: Test All Forms and Confirm Delivery

Pre Launch: Check for Errors in Other Browsers/Devices

    1. Google Chrome Desktop
    2. Google Chrome Mobile & Landscape
    3. Internet Explorer Desktop
    4. Microsoft Edge Desktop
    5. Mozilla Firefox Desktop
    6. Safari Desktop
    7. Safari Mobile & Landscape

Complete Post-Launch Checklist

  1. CS: Follow the same process you completed for the pre-launch checklist and review the Post-Launch tab of the QA Workbook.
    1. Once completed, alert the MM via email once completed.
    2. Initial and date the Onboarding Project Management Sheet.
  2. MM: Follow the same process and alert the CSM it’s been completed.
  3. CSM: This project should now be completed. Any follow up items need to be addressed separately for the CS or MM Teams.

CS: Test All Forms and Confirm Delivery

Change the contact us form info

Update the contact form info before launching the website  

  1. Login to the backend of the Q4 website
  2. Left Side Menu > Contact > Contact Forms
  3. Click “Contact form 1”
  4. Click Mail tab
  5. To and From lines needs to be an email with the same domain as the website and the same email for both line
    1. That email will be what the customer decides one here they want contact form emails to go. Typically its the general email for the business
Update Settings so the customer does not get Spam emails when we launch 
  1. Here is a SUPER helpful KB article on how to complete this.
  2. Follow the institutions on that page.
  3. Also, ensure Askimet is enabled on each form.

MM: Verify Ecommerce Tracking

  1. Check this 7 days after website launch…or if not doing a Q4 website, check 7 days after turning on e-commerce.
    1. If already turned on and not doing a Q4 website, make sure it is tracking during the onboarding process.
  2. If not, alert the CSM and have them put in a Jira to have DEV investigate.

Leave a Reply