Image may be NSFW.
Clik here to view.
Having completed the site's development prototype stage and received approval from the client, it is important to proceed with certain Quality Assurance (QA) check points in mind. Working "backwards" this way ensures a higher quality of the final website.
Needless to say, upon completion of the website design, the first round of testing should check off the following points:
Please note that the website QA check list below, while applicable to all types of websites, applies to Joomla websites design primarily.
Interface
- Ensure that the site’s name is correct
- Make site name in the footer right after the copyright as a link to the home page. Insert following code instead of %sitename% in /language/en-GB/ en-GB.mod_footer.ini: <a href="https://www.joomlabliss.com//" title="%sitename%">%sitename%</a>
- Add customer’s logo. Change template to store logo in /images/stories/ folder to let client easily change logo. If logo is not available, ensure that their business name appears at the top banner in text, making sure that it looks good and fits the overall style of the template.
- Remove Joomla’s favicon. Add customer’s favicon, if it is available. If not, place a temporary favicon of your choice.
- Contact page. Check capitalization in all fields on the contact form; add the updated contact info, ensuring consistency and nice display; test the form to make sure it is working.
- Install error404 component (or errors2site and add settings recommended by errors2site to the .htaccess file) and configure error message. Check its display. (Was Modify the 404 error page - to reflect the colors of the template (the background of the title bar and the border of the box)).
- Check the color scheme to reflect the particular needs of the client.
- Ensure borders around the menu bar look nice and consistently the same for the 2nd and 3rd level.
- Ensure that all edges and corners on all boxes and bars, etc. appear nicely
- Ensure that the background image looks nice, especially if a gradient image is used, that no content is accidentally being "smudged over" by the background.
- Ensure smooth transition for the gradient images.
- Ensure that link hover/active is consistent throughout all elements of the site (check search, various modules, error page, contact, static pages, etc etc)
- Test to see that all buttons look good (contact, newsletter signup, search results, login form, and similar elements
- Check bullets and other formatting and make sure they are all available for use inside the content article inside the current editor (create a content page and use various styles to make sure all options display properly)
- Ensure all images display properly and that appropriate imagery is used (do not use copyrighted images!). Make sure there are no articles which have /components/content/article/... in their address, i.e. not connected to any, even fake, menu. If necessary, add those menus to site map.
- Test all forms and functional components, make sure to test them all one by one and correct visual imperfections to reflect the style of the template, e.g.:
- Square buttons vs. oval buttons
- Thick borders vs. thin borders
- Background color and shades
- Link color and hover/active color
- Header and sub-header styles
- Bullet styles
- Font styles Completed
- Translation pages and search results (page titles, images, etc.)
- Go over every page one by one and conduct a visual inspection, looking for inconsistencies in tags, titles, email formats, empty spaces, too much/too little spaces between sections, etc. etc.
- Check all modules and ensure that the display is correct, no uneven spacing, no border overlapping, nice alignment, etc.
Content
- Verify that all content has been ported to the new website.
- When pasting content, make sure to use H1, H2 and H3 in a logical hierarchical order. Make sure H1 is larger than H2, and H2 is larger than H3 and that all headers are of the color fitting the template’s style.
- Perform spell check on each page
- If the project includes basic SEO, insert META data for each page
- If there is a French (or another second language) version of the site, test that all pages are being translated properly.
- Test all modules in French as well.
Navigation
- Ensure that the site's structure corresponds to the requirement fully; check each menu item one by one
- Breadcrumbs – ensure that they work correctly and that they look good and fit the overall look and feel of the template.
- Install a site map component, like xMap, and ensure that all articles are reflected correctly: blog, faqs, newsletters, etc. Check for duplications or omissions. In some cases, K2 component can conflict with xMap and requires manual adjustment.
- Click on each module that requires signup or registration or leads to another page and ensure that everything is in good order and the flow is logical and user friendly
Functionality
- Check to see that all features are represented as required
- Test all forms by filling them in properly, incompletely, leaving them blank, clicking back and forward on the browser - make sure that it all works up to modern web standard. Test all functional components this way.
- Test to see that emails are being received and that registrations are being stored as required.
- Test the French versions as well.
- Speed optimization: compress images, optimize CSS, optimize Java scripts, use jotcache. Check to see that you performed all speed optimization steps.
Website Admin
- Ensure new user creation is working properly (create a user, login and logout as this user)
- Test the editor. JCE editor often requires manual adjustment, especially with numbered lists. Create an article, save and close it. Reopen and try to edit, add a link, insert an image, add META data. Ensure that the site map reflects the changes. Ensure the display is proper.
- Test the backup functionality (Akeeba). Backup the site and activate it on another server. Untested backup equals no backup.
- Install OSE security component and test all login sets
- Generate site loading speed report using GTMetrix, record the speed. Perform speed optimization and generate another report. Record the new speed,
- Make sure the URLs are all search engine friendly (use a SEF component).
This webiste QA checklist is by no means exhaustive. Feel free to check out Joomla resources for additional tips.
- website design qa checklist
- website design Ottawa
- Joomla website design
- Joomla Ottawa