Skip to content

Weekly Meeting 11

alpervv edited this page May 2, 2026 · 1 revision

Weekly Meeting Notes – Week 11

Date: 02-05-2026 Place: Google Meet Participants:

  • Akif Emre Biçen
  • Furkan Kaan Biçer
  • Beyza Nur Deniz
  • İbrahim İlter
  • Muhammed Efe Özavcı
  • Muhammed Mustafa Öztürkmen
  • Enes Hamza Üstün
  • Alper Vural

Note Taker: Alper Vural


1. Agenda

  • Review Milestone 2 status and overdue issues
  • Plan pre-final issue closure deadline and testing strategy
  • Discuss E2E testing approach and tooling
  • Address customer meeting outcomes
  • Discuss timeline feature, path/route story feature, search improvements, and user profiles

2. Key Points Discussed

Issue & Milestone Status

  • There are currently 13 open issues
  • Milestone 2 still has open issues and open PRs, and its deadline has already passed
  • All remaining issues must be closed asap, by a set target date; testing (including E2E) must also be completed by then

E2E Testing

  • E2E tests will be written using Selenium or another suitable framework, covering defined user scenarios
  • The team discussed how E2E testing will be structured, ownership, and timelines
  • A dedicated wiki page will be created for E2E tests
  • A shared template will be defined; all tests must conform to it
  • Mobile E2E tests will be handled with Appium, following the same template structure

Customer Meeting Outcomes

  • The APK is not included in the current release
  • The stub app will be removed
  • The .env file is missing, causing the application to fail on startup; it will be added
  • Route/path feature was discussed: Enes noted the instructor does not seem to want multiple disconnected locations but rather a route. İbrahim suggested different colored pinpoints for different entities. Enes raised the question of how users will draw the path. Final decision: Users will place multiple pins that together define a path/trail (i.e., multiple locations as waypoints), which was agreed upon

Timeline Feature

  • Discussed how the timeline feature should be implemented
  • Proposed approach: stories that are close in date and location are grouped under a single pin; tapping the pin opens the timeline view
  • Feature discussion and implementation were delegated to the frontend team

Search Improvements

  • Search currently fails when the case does not match exactly; case-insensitive matching will be added
  • In addition to location-based search, content-based search will also be supported
  • Search improvements will be addressed after the route/path feature is complete

User Profiles & Dashboards

  • User profiles and dashboards will be implemented; the relevant issues are already open

3. Decisions

  • All open issues must be resolved before the final, by a defined target date
  • E2E tests (web via Selenium, mobile via Appium) will follow a shared template and be documented on a dedicated wiki page
  • The APK will be added to the release; the stub app will be removed; the .env file will be committed
  • Multiple pinpoint locations as waypoints will be used to define a user-drawn route/path
  • Timeline feature design and implementation are owned by the frontend team
  • Case-insensitive and content-based search will be added after the path feature is completed

4. Action Items

Task Owner
Close all open Milestone 2 issues and PRs Everyone
Create E2E test wiki page and define shared template Muhammed Mustafa Öztürkmen
Design and implement timeline feature Frontend Team
Implement user profiles / dashboards Enes Hamza Üstün

Team Members

Milestones


Lab Reports


Weekly Meetings

Other Meetings


Templates

Scenarios

Use Case Diagrams

Class Diagram

Sequence Diagrams

Requirements


Implementation

Clone this wiki locally