Skip to content

Sprint 7

Adam Narozniak edited this page Apr 29, 2022 · 8 revisions

Gaëtan Schwartz (@gaetschwartz)

Adam Narozniak (@adam-narozniak)(Scrum Master)

In this sprint, I fixed an overlapping UI fragment for a game fragment. I was also working on the multi-round game (with live data updates) and a new fragment at the end of the game. I got stuck a few times mostly because of the asynchronous nature of the code there which I had to incorporate (especially I had a problem with excluding the button clicks after the first click till the async action is finished). I haven't merged it because in the testing I need a UID that I am not able to get for testing (I get null and the code breaks). Next week I find a workaround for that and implement the play again functionality.

Silvio Müller (@aladin6060)

I tried to implement some testing for the ML Pipeline and prepare the ML pipeline to be integrated into the game fragment. Sadly I could not accomplish these two tasks. The image labeller is complex, I am unsure how I can translate the requirements to code. I spent a lot of time this week on the project but did not make big progress.

Bhargav Venugopal (@bhvrgav)

This week, I was still pretty overwhelmed with learning and trying to integrate the backend with the UI. I spent a lot of time trying to learn and also sought help from my teammates. However, I still had difficulty implementing it. As such, I am disappointed that I have nothing to show with regards to the database for this sprint. I also had to work on adding the friend request capability for which I had to do up the UI and implement and search function. This also took me a significant amount of time. I will aim to put in more than the stipulated 8h next week so that I do not delay the database integration any further.

Leonardo Pennino (@leonardopennino)

This week I started thinking of a design to let user create their own games with their own rules. In the meantime since this feature is still a WIP I continued the profile fragment by adding the possibility to modify the profile picture which is then loaded to firebase. The profile pictures all implement caching correctly and do not slow down or crash the application in case of no/slow internet connection. Also testing it was a bit awkward since it required the user be logged in firebase so I mocked the cache class hoping it is a good solution for it.

Jinglun Pan (@panadax)

For this sprint, I have implemented data fetching for the Leaderboard module, and also with the reference of @Leonardo cache design logic, I also implement the leaderboard (PR #91) . Also with my experience with the stats module, I can design it as more modular and portable. During this sprint, I once stuck with the test writing but with help of @Gaetan who give me much useful advice to track and locate what make my test fail. I really appreciate having all of our nice team players.

Clone this wiki locally