Rhonda's Spicy Recipes

Key Issues: Developers had to create multiple versions of websites or limit designs to work across browsers. Technologies like DHTML and CSS were implemented inconsistently, increasing development costs and complexity.

Website testing methodologies are structured approaches and used to ensure a website works correctly, looks consistent, and delivers a smooth experience across different environments. It is important to check everything from how the website functions to how it displays across browsers and devices.

Browser Compatibility Testing

Browser compatibility testing ensures that a website displays and behaves correctly across various browsers (e.g., Chrome, Firefox, Safari, and Edge) and different browser versions. Since each browser can interpret code slightly differently, developers must verify:

• Layout consistency (no broken pages or misplaced elements)
• Font and style uniformity
• Interactive features (like dropdowns or sliders) working correctly
• Responsive behaviour across devices (desktop, tablet, mobile)

Testing often includes manual checks and automation tools like BrowserStack or CrossBrowserTesting.

Website Functionality Testing

Functionality testing focuses on whether the website's features perform as expected. It checks both front-end (user interface) and back-end (server/database) operations.

• All links (internal, external, anchors) work properly.
• Forms accept, validate, and submit data correctly.
• Login/logout processes and user sessions function securely.
• Search features, filters, shopping carts, and payment systems operate without errors.
• Error messages display appropriately when something goes wrong.

This testing helps catch issues that directly impact user tasks and business goals.

The Northern Territory Government (NTG) has endorsed the World Wide Web Consortium's (W3C) Web Content Accessibility Guidelines (WCAG) 2.0, which is a widely recognised set of accessibility standards for digital content, including websites.

The endorsement focuses on ensuring that NTG websites and web content meet WCAG 2.0 Level AA compliance. This includes guidelines to make web content more accessible for people with disabilities, including visual, auditory, motor, and cognitive impairments.

All of the assets used for a particular webpage are stored on a secure local shared drive in a project-named folder in addition to the website's root folder. It makes the assets easily accessible to every team member, maintain clarity, and efficiency when working with files.

Project Folder Structure:

Rhonda's Spicy Recipes/
├── Assets/
│   ├── Branding/
│   ├── Font/
│   ├── Style/
│   ├── Image library/
│   ├── Iconography/
│   ├── Abstract graphic/
│   ├── Videos/
│   └── Templates/
├── Content/pages/
│   ├── Home/
│   ├── Recipes/
│   ├── Submit a Recipe/
│   └── Q&A/
└── Testing/
    ├── Feedback/
    └── Changes made/

Website Root Folder:

Within the root folder of the website, there is a slight difference with the local share drive, where an "Uploads" subfolder is added under the "Assets" folder for the information/assets uploaded by the user from the "Submit a Recipe" page.