Testing

The following checklists will give you an idea of things to consider when testing your website

Testing

Tests that could be identified include:

• Links

  • internal Links

  • Links to external sites (e.g., Google maps, Facebook)

  • Test on different device

• Media/Interactive elements

  • checking text (fonts, spelling, grammar, layout (flow – when resized))

  • checking media elements (text, images, audio, video)

  • checking interactive elements (JavaScript (e.g., slideshows), Forms)

  • Check all files are available (especially any images or audio files that are included with the HTML pages), and in the correct folders.

• Responsiveness

To test how your site would look on a mobile phone, the easiest is to reduce the width of your browser to see that the elements display and resize correctly. In Chrome you can also use the developer tools (Three vertical dots (top/right) > More Tools > Developer Tools, then in the Developer Tools toolbar is an icon ( ) That allows you to toggle devices.

• • in other browsers (At a minimum the most popular browsers ( Chrome and if possible Safari), then the others (Edge, Firefox, Opera, etc.). Refer to Usage share of web browsers ( Wikipedia contributors, 2022) for a current list.

  • on different devices (e.g. Mobile, Tablet, Desktop/Laptop.

• Accessibility

  • Alt text - are they sufficiently described so for someone with vision impairments they can know what is being displayed and a search engine can effectively understand your media?

  • Video captions

• User testing/Readability

  • usability (getting others to try it),

  • Checking readability (to find a list of tools you can refer to Readability testing tools (Digital.govt.nz, 2022) )

• Legal

  • Checking with stakeholders (e.g., client, potential target audience, local iwi) that the happy with the design and content.

  • Checking legal issues (e.g., Copyright, Privacy statement, images protect privacy). If your site collected information you would also check the security of the data.

• Code

  • Check for any absolute links e.g., have a drive letter ( src="file:C:// ..." ) or website prefix (e.g., Neocities)

  • using a validator (e.g., https://validator.w3.org/) . Note that the site must be hosted online for this to work, e.g. Neocities.

• Maintenance

  • Maintenance plan exits. Includes website URL updating, checking for broken links, updating content, etc.

  • Backup plan

Test Template

To assist testing your site, you should create a Test checklist to check for basic functionality (Links, responsiveness, media, etc) plus checking that any unusual or tricky techniques work. This checklist can be used after modifications are done on the website to make sure the original features are still working as expected. Any additional features would be added to the checklist.

References

Digital.govt.nz (2022) Readability testing tools. https://www.digital.govt.nz/standards-and-guidance/design-and-ux/content-design-guidance/content-design-tools-and-resources/readability-testing-tools/

Wikipedia contributors. (2022, February 22). Usage share of web browsers. In Wikipedia, The Free Encyclopedia. Retrieved 03:54, February 23, 2022, from https://en.wikipedia.org/w/index.php?title=Usage_share_of_web_browsers&oldid=1073405865