Sprint 5 - HealthPlay-EPFL/Health-Play GitHub Wiki

Summary for Sprint 5

Etienne (Scrum Master)

Albin

This week I've experience Cirrus CI meaning whatever I do I can't push my code because the code compile localy but it doesn't compile on Cirus CI. The diffrent random errors given by Cirrus CI are useless because i can only check locally that there is no error whatsoever. Given that, I've decided to change the ml package for pose detection but same problem with Cirrus CI. Despite that I,ve done the tests for the kneetag camera with the new package.

Ozan

This week everything seemed to have gone smoothly for the first time since the beginning of the semester. I implemented everything I needed to, augmented some coverage and corrected some bugs. For next week, I'll try to implement the camera API to user for barcode scanning.

Baptiste

This week I didn't manage to find an efficient way to test the Frag_home fragment. I decided to keep buttons to switch between the calendar and the graphs. I didn't spend enough time working this week, as wasn't feeling great mentaly (covid too).

Antoine R.

This week I implemented the user plant collection on Firebase and I cleaned up my APIs codes so that Osan could reuse the camera system for the barcode scanning. Linking user pictures to the collection took the expected amount of time but the ListView display was complex to figure out and I did not have time to implement as many tests as I wanted.

Antoine M.

This week, I begin to resize the element of interface for different size of the screen, I finish the dataMap in modifying the Graph_Stat fragment, I solve the bug of the logo is not in center, and I implement a fragment version of the GameMenu for use the button navigation.

Etienne

The week was much simpler for me because i didn't have to create a new class/activity, i only had to make the code more modular and apply the theme fo each activity. The difficult part was the calendar because it didd't work like the rest of the widgets.

Overall team

In general, the tasks were less challenging than last week, which means we had less difficulty implementing them. Two of our group members were focused on adding more tests to some activities, the code coverage should now be more acceptable than last week, for these activities. We had two scrum meetings, one on Tuesday and the other on Thursday.