QA Process

Each day a person will spend half of the day going through closed cases to look for mistakes.

• Closed cases can be found here: https://systemadmin.dealercarsearch.com/web/Cases/Default.aspx
• The View dropdown has built in filters for Closed Yesterday and Today.
• The filter can be changed at the bottom of the grid to change dates, etc.
• Coordinate with previous week’s QA person to find out where they left off.
• Pick up from that point and start with Build cases.
  • Go through the build notes and make sure they were all completed.
  • Verify that logo is properly sized and design is not ugly.
  • Check the DCS Toolbox to ensure the website and module style is set correctly.
  • Check the DCS Toolbox to ensure that the window sticker header information is added correctly and checked.
  • If the dealer has Hi-Res photos, ensure that this is checked in the DCS Toolbox .
  • Check for misspellings/grammar errors on any custom content.
  • If dealer has REP Management and doesn't have any Customer Testimonials, delete the Testimonials module.
  • If Dealer has SEO product, verify:
  • Verify all pages have just one keyword rich H1 title. Do not use duplicate titles.
  • Verify the blog page is active under 'Our Store'. Make sure blog setting is checked in DCS toolbox.
  • Verify site has a favicon installed.
  • If applicable, bring over meta titles and descriptions and page content from previous site provider.
  • Ensure images and .psds are uploaded to shared directory.
  • Run Lighthouse in Chrome or pagespeedinsights to make sure scores are green.
  • If scores are below green value and they match the template site, note the CMS Improvements sheet CMS Improvements.xlsx.
  • After Builds, spot check various changes to ensure all steps were completed and no errors are apparent on site. If the changes are content changes, ensure that pagespeed scores are green and accessibility standards are followed.