Weekly Meeting 8

Lab 8 – Weekly Meeting

Date: 29.04.2026 Time: 17:00 – 18:00

---

Participants

• Ali Akkaya ✅
• Bora Aydemir ✅
• Ömer Belemir Delier ✅
• Arif Evren ✅
• Ulaş Sertan Kemeç ✅
• Ekin Kılıç ✅
• Baran Önder ✅

---

Agenda

1. General project status review.
2. On-site accessibility inspection around the campus and observation of standard violations.
3. Discussion on the importance of writing tests and improving test coverage.

---

Discussion Items

General Project Status

The team reviewed the overall progress of the project, discussing completed tasks, ongoing work, and any blockers affecting the timeline. The current state of the frontend and backend implementations was assessed, and the team aligned on the remaining steps needed before the next milestone.

Campus Accessibility Inspection

Team members shared observations from an on-site inspection conducted around the school campus. The inspection focused on identifying real-world violations of the accessibility standards discussed in the previous week's meeting. Several instances of non-compliant infrastructure were noted, including broken ramps, narrow pathways, and obstructed routes. These observations were found to be directly relevant to the obstacle categories and reporting flows implemented in the system, and they reinforced the practical value of the project.

Importance of Testing

The team discussed the critical role of writing tests in ensuring the reliability and correctness of the system. The current test coverage was reviewed and identified as insufficient, particularly for the frontend components and core API flows. The team agreed that improving test coverage is a priority going forward, and discussed approaches for writing unit tests, integration tests, and component-level tests. The importance of catching regressions early and maintaining confidence in the codebase as the project evolves was emphasized.

---

Action Steps

• All Members: Document any accessibility violations observed during the campus inspection and map them to existing obstacle categories in the system.
• Ali Akkaya: Begin writing unit and component tests for the frontend screens with low coverage.
• Bora Aydemir: Add integration tests for the critical backend API endpoints.
• Ömer Belemir Delier: Update the meeting notes and track test coverage progress across the project.
• Arif Evren: Write tests for the routing and obstacle reporting flows.
• Ulaş Sertan Kemeç: Review and update GitHub issues to include test-related tasks.
• Ekin Kılıç: Identify frontend components most in need of test coverage and coordinate testing efforts.
• Baran Önder: Review the overall test strategy and ensure consistency across frontend and backend testing approaches.