Daily Scrum 3 (Sprint 2) - shanjida-alam/Smart-Living-Community GitHub Wiki

Meeting Notes - 09-11-2024

Date, Duration, and Location:

09-November-2024 6:00 PM 15 Minutes Discord Voice Channel

Editor

Mst.Solaimi Hamid

Attendees:

  • Mst.Solaimi Hamid (SH)
  • Shanjida Alam (SA)
  • Irtifa Haider (IH)
  • Hasneen Tamanna (HT)
  • Md.Tanvir Hossain Saon (TH)
  • Jubaer Ahmad Khan (JK)

Daily Scrum Time

  • Frequency: Every 2 days
  • Time: 6:00 PM

Scrum Roles

  • Scrum Master: Jubaer Ahmad Khan (JK)
  • Product Owners: Shanjida Alam (SA)
  • Development Team Members: SH, SA, IH, HT, TH, JK

Daily Task Progress

MEMBER(S) What we did yesterday? What problems faced? What will do today?
1. SH Completed the full User Interface (UI),
Attempted Test-Driven Development (TDD) and
try to generate function.
Encountered difficulties in generating test case function while working within a Test-Driven Development (TDD) framework and
Sickness, affecting productivity.
Work on resolving the issues faced with test case function generation using TDD,
Create new Branch "Manage directory" in git and
try to develop viewmodel part.
2. SA Generated test cases,
Completed the full User Interface (UI) and
Attempted Test-Driven Development (TDD).
Faced difficulties in generating test cases within the TDD approach. Work on resolving the issues faced with test case generation using TDD.
3. IH Created test cases for the Model and Repository layers for the Community Bulletin Board feature,
Successfully passed the test cases for the Model and Repository.
Experienced issues with database connections for two consecutive scrum sessions, leading to testing using mock objects,
Sickness since Scrum 1, affecting productivity.
Design UI files for CreateAnnouncement,
Create test cases for CreateAnnouncementViewModel.
4. HT Generated five test cases for the ViewModel class,
Created the CreateBillView class.
Challenges encountered in identifying every possible scenario for the test cases. Write functions corresponding to each identified test case and re-run the tests for verification.
5. TH Generated test cases,
Created the Security Log Model,
Designed the layout.
Faced challenges in writing functions derived from the identified test cases. Write functions for the test cases.
6. JK Completed UI design for the Parking fragments,
Created dummy test case methods for the ResidentParkingRegistration class and
Successfully passed the test case for data retrieval from Firebase Firestore.
Encountered a challenge with Firebase-related testing in Android. After spending time on JVM-based tests, I realized that instrumentation testing is necessary for Android’s online database tests,
Forgot to turn off the Toggl timer,
Progress slowed due to illness.
Complete the remaining test case methods for the ResidentParkingRegistration class,
Integrate unit code options into the login interface, Pass the unit-tested code to the main content activity, enabling resident identification and access to app features.

Notes

  • Maintain a Single Activity with Multiple Fragments: Ensure the project follows a single-activity structure, with navigation handled through multiple fragments. This approach promotes modularity, easier navigation management, and better alignment with modern Android architecture practices.

  • Keep Necessary Screenshots at Every Step: Remember to take screenshots after running the test cases first, which will return failed result, and again take screenshot after writing the functions, and re-running the test cases which should return passed/successful result.

⚠️ **GitHub.com Fallback** ⚠️