Update test docs

tests/defect-log.md

@@ -0,0 +1,274 @@
+# 🐞 Defect Log
+
+This log tracks all known defects identified during testing.
+
+---
+
+## DEF-001
+
+**Title:**  
+Pickup Request Not Saved or Reflected on Dashboard
+
+**Detected By:**  
+Manual QA
+
+**Date Reported:**  
+_2025-07-09_
+
+**Related Test Case(s):**  
+[TC-SM-001]
+
+**Environment:**  
+- Local React App (`npm start`)
+- Browser: Chrome
+
+**Description:**  
+When a user schedules a new pickup:
+- The request is **not saved** in `localStorage` or any backend.
+- The **Dashboard** "Scheduled Pickups"  or count does not update to reflect the new request.
+
+**Steps to Reproduce:**  
+1. Go to **Dashboard** — record current pickups count.  
+2. Schedule a new pickup via the **Pickup Scheduler** form.  
+3. Inspect `localStorage` → no new pickup data.  
+4. Return to Dashboard → count unchanged.
+
+**Expected Behavior:**  
+- Pickup details should persist in `localStorage` under `scheduledPickups`.
+- Dashboard count should update automatically.
+
+**Actual Behavior:**  
+- No data saved.
+- Dashboard does not change.
+
+**Severity:**  
+High — Core functionality is broken.
+
+**Status:**  
+Open
+
+**Assigned To:**  
+_Samuel Kimwele Mbai_
+
+**Attachments:**  
+- Screenshots of storage check & dashboard state.![image](https://github.com/user-attachments/assets/c5412371-2b5b-4fd5-b061-f992bd854ff9)
+---
+
+
+## DEF-002
+
+**Title:**  
+Missing Top-Level `<h1>` Heading on Blog Page
+
+**Detected By:**  
+Manual Accessibility Testing (axe DevTools)
+
+**Date Reported:**  
+_2025-07-07_
+
+**Related Test Case(s):**  
+[TC-MK-001]
+
+**Environment:**  
+- Local React App (`npm start`)  
+- Browser: Chrome  
+- Tool: axe DevTools v4.10.3
+
+**Description:**  
+The `/blog` page does not contain a single, descriptive top-level `<h1>` heading. This violates accessibility standards that require a clear page title for assistive technologies.
+
+Note: Other pages in the application (e.g., Login, Awareness, Admin Panel) do include valid `<h1>` tags — this issue is isolated to the Blog page.
+
+**Steps to Reproduce:**  
+1. Start the app locally with `npm start`.  
+2. Navigate to `http://localhost:3000/blog`.  
+3. Open Chrome DevTools → go to **axe DevTools** tab.  
+4. Click **"Analyze"**.  
+5. Observe the issue: “Page should contain one `<h1>` heading”.
+
+**Expected Behavior:**  
+- The Blog page should include a unique `<h1>` element near the top of its main content section.
+
+**Actual Behavior:**  
+- No `<h1>` found; page structure begins with `<h3>` or styled `<div>`s instead.
+
+**Severity:**  
+Medium — Affects accessibility and WCAG compliance.
+
+**Status:**  
+Open
+
+**Assigned To:**  
+_Martin Kimani_
+
+**Attachments:**  
+- Screenshot of axe DevTools result panel
+- ![image](https://github.com/user-attachments/assets/a19f5671-5d71-475a-9836-b0d589f3b027)
+- [WCAG Guideline 1.3.1 – Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html)
+
+## DEF-003
+
+**Title:**  
+Form Accepts Overly Long Inputs and Invalid Email Without Proper Validation
+
+**Detected By:**  
+Manual Edge Case Testing
+
+**Date Reported:**  
+_2025-07-07_
+
+**Related Test Case(s):**  
+[TC-MK-002]
+
+**Environment:**  
+- Local React App (`npm start`)  
+- Browser: Chrome  
+- Page: Pickup Scheduling Form (`/schedule`)
+
+**Description:**  
+The form fails to validate excessively long input in the **"Name"** field and does not enforce proper format validation in the **"Email"** field. The only check in place appears to be for the presence of the `@` symbol.
+
+**Steps to Reproduce:**  
+1. Go to the Pickup Scheduling form.  
+2. In the **Name** field, paste over 500 characters (e.g., lorem ipsum).  
+3. In the **Email** field, enter an invalid email like `example@gmail...` (missing domain).  
+4. Click **Submit**.  
+5. Observe behavior.
+
+**Expected Behavior:**  
+- App should **restrict Name input** (e.g., max 100 characters) or show a clear validation error.  
+- Email should be validated using a regex or HTML5 pattern (e.g., `user@example.com`) and **show an error message** for invalid formats.
+
+**Actual Behavior:**  
+- The form **accepts 500+ characters** in the Name field with no error or truncation.  
+- The Email field **accepts invalid formats** like `example@gmail.` without any feedback or warning.  
+- The form still submits successfully (depending on implementation).
+
+**Severity:**  
+Medium – affects data integrity and user input reliability.
+
+**Status:**  
+Open
+
+**Assigned To:**  
+_Martin Kimani_
+
+**Attachments:**  
+- Screenshot of input fields before and after submission
+   ![image](https://github.com/user-attachments/assets/45797129-0750-49f5-9aa2-c2403e7930de)
+
+
+
+## DEF-004
+
+**Title:**
+Feedback Form Accepts Any Request ID Without Validation
+
+**Detected By:**
+Manual QA – Functional Testing
+
+**Date Reported:**
+*2025-07-09*
+
+**Related Test Case(s):**
+\[TC-BN-006]
+
+**Environment:**
+
+* Local React App (`npm start`)
+* Browser: Chrome
+* Page: Feedback (`/feedback`)
+
+**Description:**
+The Feedback form allows users to submit feedback using any text string as a Request ID — even if it does not match an existing or valid pickup request. This leads to data inconsistency and undermines traceability.
+
+There is no mechanism in place to:
+
+* Verify the Request ID exists
+* Autofill or restrict to valid IDs only
+* Display an error if an invalid ID is used
+
+**Steps to Reproduce:**
+
+1. Navigate to the Feedback page (`/feedback`)
+2. In the **Request ID** field, enter a made-up value (e.g., `REQ9999`)
+3. Type a comment in the **Feedback** field
+4. Click **Submit**
+5. Observe the result
+
+**Expected Behavior:**
+
+* The app should **validate** the entered Request ID against existing requests
+* An error message should appear if the ID is invalid or unrecognized
+* Optionally, the Request ID should be **autofilled or selected** from a dropdown list of real requests
+
+**Actual Behavior:**
+
+* The form **accepts any input** in the Request ID field
+* Feedback is **submitted even for non-existent IDs**
+* No validation or warning is triggered
+
+**Severity:**
+Medium — affects data accuracy and backend processing of feedback
+
+**Status:**
+Open
+
+**Assigned To:**
+*Bridget Ngugi*
+
+**Attachments:**
+![image](https://github.com/user-attachments/assets/5a6b7ff0-e0a2-44d9-b859-65e76e1551db)
+
+
+## DEF-005
+
+**Title:**  
+Missing “Cancel” Button in Admin Panel for Pending Pickups
+
+**Detected By:**  
+Manual Functional Testing
+
+**Date Reported:**  
+_2025-07-07_
+
+**Related Test Case(s):**  
+[TC-BR-002]
+
+**Environment:**  
+- Local HTML App (opened via Live Server)  
+- File: `index.html`  
+- Browser: Chrome
+
+**Description:**  
+According to test case TC-BR-002, admins should be able to cancel user pickup requests from the "Pending Pickups" section. However, the current Admin Panel UI does **not include a “Cancel” button**, making it impossible to complete this action.
+
+**Steps to Reproduce:**  
+1. Open `index.html` in Live Server  
+2. Log in as Admin (or simulate admin access)  
+3. Navigate to the **Admin Panel** → **Pending Pickups**  
+4. Observe that no “Cancel” option is present for any listed user request
+
+**Expected Behavior:**  
+- Each request in "Pending Pickups" should include a visible **"Cancel" button**  
+- On clicking "Cancel", the request should be removed from the list and show a **confirmation alert/message**
+
+**Actual Behavior:**  
+- No "Cancel" buttons are present  
+- No UI mechanism to remove or manage pickup requests as an admin
+
+**Severity:**  
+High — Admin functionality is incomplete and does not support request management
+
+**Status:**  
+Open
+
+**Assigned To:**  
+_Bridget Ngugi_
+
+**Attachments:**  
+- Screenshot of Admin Panel showing missing Cancel buttons  
+  ![image](https://github.com/user-attachments/assets/a39bde06-ccd4-4908-a881-e06a171bbdec)
+
+
+

tests/environment.md

@@ -0,0 +1,72 @@
+# 🌍 Test Environment Setup – CleanCity QA Project
+
+**Project:** CleanCity – Waste Pickup Scheduler  
+**Team Name:** CleanTrackers  
+**Prepared by:** Samuel Mbai, Martin Kimani, Bridget Ngugi  
+**Date:** July 4, 2025
+
+---
+
+## 🧰 Required Tools & Platforms
+
+| Category              | Tool / Platform                  |
+|-----------------------|----------------------------------|
+| Version Control       | GitHub                           |
+| Browser Testing       | Chrome, Firefox, Edge, Safari    |
+| Device Emulation      | Chrome DevTools Responsive Mode  |
+| Accessibility Testing | axe DevTools, WAVE, NVDA         |
+| Performance Tools     | Google Lighthouse                |
+| Project Management    | GitHub Projects (Kanban Board)   |
+| Documentation         | Markdown (`.md`), GitHub Issues  |
+
+---
+
+## 🌐 Browser Compatibility Matrix
+
+| Browser        | OS            | Version Tested |
+|----------------|---------------|----------------|
+| Chrome         | Windows/macOS | 114+           |
+| Firefox        | Windows/macOS | 102+           |
+| Safari         | macOS/iOS     | 15+            |
+| Microsoft Edge | Windows       | 114+           |
+
+---
+
+## 📱 Device Coverage
+
+| Device Type | Testing Method                   |
+|-------------|----------------------------------|
+| Desktop     | Manual + DevTools                |
+| Tablet      | Chrome DevTools → iPad emulation |
+| Mobile      | Chrome DevTools → iPhone/Android emulation |
+
+---
+
+## 📶 Network Conditions Tested
+
+| Network Type | Tool/Method                      |
+|--------------|----------------------------------|
+| WiFi         | Real-time testing (stable)       |
+| 4G / 3G      | Chrome DevTools → Throttling     |
+
+---
+
+## ♿ Accessibility Testing Tools
+
+| Tool            | Purpose                                      |
+|-----------------|----------------------------------------------|
+| axe DevTools    | Automated WCAG compliance scans              |
+| WAVE Extension  | Color contrast, landmarks, ARIA checks       |
+| NVDA            | Screen reader simulation (keyboard support)  |
+| Manual Keyboard | Tab/Shift navigation through all elements    |
+---
+## 📋 Project Management Platform
+
+- **Tool:** GitHub Projects (Classic Kanban Board)
+- **Workflow:** To Do → In Progress → In Review → Done
+- **Issue Types:** Bug, Task, Story
+- **Used for:** Task tracking, defect logging, test planning
+---
+## 📝 Notes
+- All test environments were selected based on project guidelines, device/browser usage statistics, and CleanCity's responsive design expectations.
+- Automation tools (e.g., Jest + React Testing Library) may be integrated in Week 2 or 3 for bonus marks.

tests/team-roles.md

@@ -0,0 +1,23 @@
+### 🧑‍💼 Samuel Mbai – Team Lead & QA Coordinator
+- Leads weekly meetings and task delegation  
+- Oversees creation of test strategy and test plan  
+- Sets up GitHub Kanban board and workflow columns  
+- Tracks progress and ensures timely submissions  
+- Reviews documentation, manages GitHub activity
+
+---
+
+### 🧑‍💻 Martin Kimani – Manual Tester & Accessibility Specialist
+- Writes and executes test cases for forms, scheduling, and dashboard features  
+- Performs accessibility checks using tools like axe DevTools and WAVE  
+- Manually verifies edge cases and mobile responsiveness  
+- Prepares and maintains test documentation (`test-plan.md`, `test-data.md`, `test-cases.md`)
+
+---
+
+### 👩‍💻 Bridget Ngugi – Functional Tester & Bug Analyst
+- Designs and executes manual test cases across all user roles  
+- Logs bugs clearly in GitHub Issues with steps, screenshots, and severity labels  
+- Performs exploratory and regression testing across browsers  
+- Helps maintain defect log and prioritizes reported issues  
+- Assists in drafting the final test report and 5-minute presentation outline