QA Checklist

Project Details
Project Name
Notes
Quality Assurance (QA) Checklist
Brief and/or Specification
- Check to see if any brief's and if so check it has been followed.
- Check to see if any technical specifications or any other functionality notes, and if so check it has been followed.
- Check if any other notes, videos etc and if so check they have been followed.
Design
- Check each design against the built page looking for any errors or inconsistencies
- If there is mobile or tablet designs also check these against the build
- Check to make sure the build looks identical to the designs - unless otherwise agreed
Code
- HTML has passed validation (W3C)
- CSS has passed validation (W3C)
- JavaScript is error free
- Check the CSS has been concatenated and compressed.
- Check the JS has been concatenated and compressed
- Check the source code of the website and report anything unusual or any inconsistencies
- Check that images are being resized correctly and fit for purpose (i.e. optimised for size and speed)
- Check that the PHP files follow an indent standard
- Check that the build includes the gulpfile.js, package.json and all original src files are included (.scss files etc)
- Check that all templates are modualised where appropriate
- Check that the theme follows are boilerplate fundamentals
Speed
- Each page has been run through Google Page Speed and ensure the score for both desktop and mobile is ‘good’
- Check for page loading times when navigating the site on desktop, tablet and mobile
- Check the images have been compressed via an App such as Squoosh
Browsers
- Check the website on IE (back to IE10 unless agreed otherwise), Edge (latest version), Chrome (latest version), Firefox (latest version) and Safari (latest version)
- Check the website using physical tablet devices
- Check the website using physical mobile devices
- Check website on desktop, scaling the browser down to check for sizes in-between device sizes. The website should look good at all sizes, and not break at any size whatsoever
Useability
- Browse through each page via the navigation/s in both the header and footer
- If there is a search bar, search the website using terms like ‘the’ to get results, and jibberish like ‘ergferg’ to return no results
- If there is any filters, forms, logins or any other widgets – use them to check the functionality, styling and any errors
- Check the initial page loads, does it look OK or does content show then disappear
CMS (i.e. WordPress)
- Check that the CMS is client friendly, and you can create pages, posts easily
- Create a test page and make sure this formats correctly on the frontend. Use default Gutenberg blocks and put this code in it.
- Check what plugins have been installed, and advise to disable and delete any non-essential ones (i.e. clone posts, fakerpress)
- Check to see if all plugins listed here are installed
- Check to see the user email address is not set to a @abitgooey.com or @gooey.dev address
- Check to see that correct grammer and punctuation has been used on Post Types and Fields (i.e. faqs should be FAQs)
- Check that ‘Add New Plugins’ has been disabled for dev purposes (i.e. /wp-config.php should include define( ‘DISALLOW_FILE_MODS’, true );
- Check that WordPress has been set up using our guidelines
- Confirm that the developer has handed over the work using our handover guidelines
Content
- The site includes a general content page (if no design provided)
- The WYSIWYG fields allow styled usage of lists, blockquotes and H tags
- Favicon created and added
- Device icons created, added and display
- A 404 page has been created
SEO
- Page titles are descriptive and SEO friendly
- Correct use of H tags throughout the site
- Yoast SEO added (if WordPress)
Extras (Gooey specific)
- Check that AOS has been added onto all blocks

Submit a enquiry

QA Checklist

Project Details

Quality Assurance (QA) Checklist