Testing Prompts

Functionality Testing Prompts

Functionality Issues

Ensuring that the functioning of all custom functions is working as defined within the Client's Deliverables & Dependencies.
Ensure that the functioning of all menu items, links, buttons, etc. work as expected/directed.
Ensure that the execution of specific functions do not cause any other issues within the page/Site/App. e.g. Clicking on "About" within the menu, should take the user to the "About" page, and NOT produce any other results. e.g. The "on-click" event should NOT cause any alignment issues within the current page or "About" page. e.g. In-page links should either jump to the relevant portion within the page - or open up a new tab.

CMS Admin Experience Issues

Highlight any issues related to the CMS admin experience (and its impact on the front-end): a. Adding/editing/deleting posts. b. Editing plugin settings (e.g. slideshow speeds), etc. c. Font style, weight, size, line height according to the respective project guidelines. d.Content overflow, alignment & spacing issues.

Incorrect OR Broken Links

Validating that the page displays correctly and effectively communicates to users that the requested resource is not found. This includes ensuring the 404 error message is clear and user-friendly, providing relevant navigation options or links to help users return to the main site or find alternative content.
Ensure there are NO incorrect or broken links within each page.
Ensure ALL external Site/App links open in a new browser tab.
Ensure ALL internal Site/App links open in the same browser tab. Use any of the given links:
- validator.w3.org/checklink
- brokenlinkcheck.com

Site/App Speed

Is the load speed acceptable from a user's perspective across all devices? (Benchmarks: Facebook. See: (Care of Google) How Speed Impacts the User Experience.)
What is the Site/App's speed?
- Google Page Speed: Target 80% or above
Lighthouse/Web Vitals audit also returns additional checks such as Accessibility, which shall be captured.
More on core web vitals here.

Missing (or slow to load) Content

There should be no question marks, error-indicative images, or "blank spaces", where content is expected to appear.
Site/App-Hosted/Driven Text/Images/Videos: Ensure that all text/images/videos that should appear, do appear! On DESKTOP and MOBILE!
3rd Party Content:Ensure that all content being fed from a 3rd-party (API, RSS Feed, etc.) renders as expected.

Email and Phone Number Issues

On Desktop browsers:

Emails should open up default/user's email client.
Telephone numbers should open up Skype (if installed). Otherwise remain inactive (depending on the Client's desired experience/what's documented in the SOW).

On Mobile browsers:

Emails should open up default/user's email client.
Telephone numbers should initiate the phone call process on the user's phone.

*Note: The PM/Dev/QA should be documenting all form requirements (field expectations, alert messages, etc.) clearly up-front (within the SOW/ticket/task) to ensure that the form is developed appropriately, as well as tested according to the expected behaviour for each field/the entire form user journey.

Mandatory Fields:

Ensure that it's clear to the user WHAT fields are mandatory. (For example: The field is starred or highlighted in some way. If starred, there should be a reference message as to what this star means. E.g. "This field is mandatory.")
Ensure that the appropriate "alert" message appears on-screen if the user does not "fill-in" a mandatory field (ideally DURING the user experience/next to the field as opposed to "on Submit").

All Fields:

Ensure that it's been indicated to the user, what kind of entry they're expected to make within each field. (For example: The field might be a calendar, whereby a date before a certain date or after a certain date can not be selected.)
Ensure that the appropriate "alert" message appears if the user does not provide an appropriate entry for each field (ideally DURING the user experience as opposed to "on Submit").

Alert/Error Messages:

Ensure that the alert messages match-up with what's been documented in terms of "form requirements"*. If there are any CAPTCHA fields, ensure that they are working as expected.
Form Errors: Alert/Error Messages: Ensure that there are no appearance related issues. Font style, color, alignment, spacing, position, wrapping, overlapping issues, pop-up appearance issues, etc.

Confirmation Emails:
Ensure that the confirmation email(s) related to any forms on the Site/App match-up with what's in the "form requirements"*. (Usually, confirmation emails are sent to 1. the user, 2. the Site/App Admin.)

Plugin and API Behavior Issues

Ensure that all plugins and APIs are behaving/functioning as expected and the user journey is working as it should. a. Plugins - Image Carousels, Image Sliders, Form Plugins, etc. b. APIs - e.g. Google Map, Twitter Feed, YouTube Videos, etc
Ensure that there are no appearance related issues. Font style, color, alignment, spacing, position, wrapping, overlapping issues, pop-up appearance issues, etc.

Content Sharing/Posting Issues

Ensure that the social icons are operating as they should and in a speedy fashion.
Ensure that the message/image that is shared matches up with what's been specified by the Client/in the SOW. E.g. If the user is sharing an image from the Site/App via Facebook, then that specific image/image description should be posted to the user's wall (NOT a generic image/image description, UNLESS directed by the Client). -Content Sharing/Posting Issues: Ensure that there are no appearance related issues with any social icons. Font style, color, alignment, spacing, position, wrapping, overlapping issues, pop-up appearance issues, etc.

URL and/or Page Naming Issues

Ensure that the page name/title matches the menu selection.
Ensure that the URL matches the menu selection/page name - makes sense to the user. (These expectations should be documented in the SOW.)

Behavior State Issues

Ensure that the behaviour states for the following items work/behave as expected/what's been directed on each page (across all devices/browsers):
- Menu Items
- Sub-menu Items
- Buttons
- Links
- Images (If applicable. Note: Often images will have hover-over and/or active state)
Behaviour states for the above items are typically as follows:
- Hover-over State
- Selected/Active State
- Static/Disabled (Inactive link.)
Look for inconsistencies in behaviors and highlight these inconsistencies also.

Webmaster Tools

To ensure that the Webmaster Tools are actively tracking and providing valuable insights into the website's performance and visibility in search engine results. Find more info here

Google Analytics/Google Tag implementation

To ensure the implementation is functioning correctly, providing accurate data for analysis and decision-making purposes.

To ensure that the social sharing functionality integrates seamlessly into the application, providing users with a reliable and engaging sharing experience.
References:
- https://developers.facebook.com/tools/debug/
- https://www.linkedin.com/post-inspector/

Web Accessibility

Check if specifically requested and/or time permits.
Verifying "Web Accessibility" checks, the process involves assessing that the web application or site conforms to accessibility standards such as WCAG (Web Content Accessibility Guidelines).
This includes testing for features like alternative text for images, keyboard navigation support, semantic HTML markup, color contrast ratios, and ensuring compatibility with assistive technologies like screen readers.
References:
- http://www.w3.org/WAI/eval/preliminary.html

UI (User Interface) Testing Prompts

Design Symmetry and Consistency Issues:

Ensure that each page matches up with what's in the PSD file, in terms of: "DESIGN SYMMETRY AND CONSISTENCY". Specifically with regards to:
Margins
Spacing
Alignments (in relation to text/images/links/buttons)
Colors
Area blocks
Sizes used (for all elements on the page)

Note: Absolute pixel perfection may or may not be necessary, dependent on the Client's preference. Some Clients are more focused on the page's "design symmetry and consistency" than absolute pixel perfection (depending on the Platform also). This should be clarified with the Client before the commencement of any QA activities.

Font Appearance Issues:

Font style, weight, size, line-height.
Ensure that the fonts on each page - across each device/browser - match-up with what's in the PSD file/what's been directed.
Make sure the text is easily visible/readable.
Small font sizes may look OK in the .PSD file, but may not be easily visible/readable when presented on the site/app.

Note: Some fonts may not be able to render in exactly the same way across all devices/browsers. In this scenario, ensure you understand WHICH device/browser is of priority to the Client (as per the "Testing Requirements and Priorities" as documented in the SOW). Consult your PM for priorities.

Spelling Errors:

Highlight any spelling errors, even if the mistakes are also in the Copy deck.

Copy Deck Match-Up Errors:

Ensure that the text on each page matches up with what's in the Copy deck/what's been directed. (Unless the Copy deck contains a spelling error. See above.)

Note for Axioned Team: The team SHOULD have a separate Copy deck document - in a .doc or Google doc format. And we SHOULD directly copy/paste from that document ONLY. To check that what you've copied is accurate: Ctrl C (COPY), Ctrl F (FIND/within your document or page), Ctrl V (PASTE/within "Find").

Image Quality Issues:

Ensure that the images do not look grainy or blurred.
Ensure that the images should not be squashed.
Ensure that images are optimized on receipt from the Client.

Stock Image Check:

Ensure that any image is not watermarked i.e. no image is a stock image (in the package) → especially check for background images.

Other Checks/Prompt

Development Inspections/Schedule should be established at the outset of each project, ticket, or task to ensure thoroughness and alignment with project goals. This includes:
- Security Inspection: Conducting comprehensive security assessments to identify and mitigate potential vulnerabilities and ensure data protection.
- SEO Inspection: Analyzing the code and content to optimize for search engines, enhancing visibility and user accessibility.
- DevOps Inspection: Ensuring seamless integration and automation across development and operations processes to enhance efficiency and deployment reliability.
- Throughout these inspections, ongoing coordination with the inspection team is essential to address findings promptly and maintain project momentum.
Dummy CMS/database entries: To verify the removal of dummy CMS/database entries on the live environment involves confirming that all test data, placeholder content, or temporary entries used during development or testing phases have been properly deleted or hidden from public view. This ensures that the live website or application only displays accurate and relevant information to users, maintaining data integrity and user experience standards.
robots.txt file: To verify the robots.txt file for staging involves ensuring it accurately restricts or allows search engine crawlers as intended for the staging environment. Similarly, for the live environment, the robots.txt file should accurately control crawler access according to production requirements, ensuring it aligns with SEO and content management strategies.
Plugins: To verify that correct plugins are being used (dependent on CMS), ensure compatibility with the CMS version, validate proper functionality according to requirements, and confirm seamless integration without impacting site performance or user experience.