📝 Assignment: Spot the Bugs – To-Do App Review

🎯 Learning Objectives

• 🔍 Understand how to observe and define basic functional requirements.
• 🐞 Identify visible bugs in a simple web application.
• 📝 Write clear and structured bug reports using GitHub Issues.

---

📋 What You'll Need

• 💻 A browser (e.g., Chrome, Firefox, or Edge).
• 📂 The provided todo-tracker.html file.
• 🌐 Access to the course GitHub repository.

---

📝 Submission Instructions

📂 Submit 2 GitHub Issues using the bug report format below.
🗂️ Locate a Bug_Report_Summary.md file on this repo and include:

• ✅ A list of 3 expected app behaviours.
• 🔗 Links to your 2 GitHub Issues.

🚨 Note: You must raise the bug reports directly on GitHub using the Issues tab of the class repository. These issues will be referenced by ID and linked in your Bug_Report_Summary.md file.

---

🚀 Run in VS Code (Live Server)

Prerequisites

• Install VS Code
• Add the Live Server extension

Quick Setup

1. Clone and open the repository:

2. Open todo-tracker.html in VS Code's Explorer (Ctrl+Shift+E), right-click, and select Open with Live Server.

---

📚 Assignment Questions

Question 1 📋

Write down 3 expected behaviours that a To-Do app should have in the Bug_Report_Summary.md file.
📌Example:

• Tasks should not be added if the input is empty.

---

Question 2 🐛

Test the app by interacting with todo-tracker.html.
Find and report 2 bugs 001 and 002 using GitHub Issues. Use this format:

**Title**: [e.g., "Task disappears after refresh"]

**Steps to Reproduce**:
1. Type "Buy milk"
2. Click "Add"
3. Refresh the page

**Expected**: Task should still be visible  
**Actual**: Task disappears  
**Severity**: Medium

---

💭 Reflection

Should be captured in your Bug_Report_Summary.md file.

How to edit a markdownfile

NOTE: You should not fork the repository