-
Notifications
You must be signed in to change notification settings - Fork 0
Sprint 9
This week, I have worked on debugging some of the known bugs, documenting some of the ambiguous code and working on increasing the code quality. The biggest issue of the week for me was the frequent CI fails due to some fickle API calls. Another challenge I've faced was to allocate a task for myself with a proper amount of time, due to the fact that most of the remaining tasks or bugs are about Firebase, which I've heard already takes a while to learn.
This week I finished the image upload for the profile, due to CI issues it took longer than expected so I was not able to finish my second task which was to implement typing game on a multiplayer setting. I wouldn't say I encountered many issues coding, rounding the image was something new but overall the CI hampered my progress this week. Hoping next week will be better with that and I will catch up with the task I did not finish this week
The implementation of a QR code reader went mostly fine. The most challenging part was to get the best coverage knowing that it is nearly impossible to mock the camera. Then I had some problem with the CI, some test that I didn't write was not working anymore. It made me lose a lot of time. Finally I've done some bugfix to correct crashing while playing typing game when not authenticated.
I managed to do all my tasks this week. The major ones include saving the score after the game in the database and correct functionality of adding friends. I have also performed small bug and UI fixes to make the app look/work better. I did not encounter any severe problems/blockage. Team was very helpful in reviews and sharing opinions on one problems!
My tasks went well this week, much better than last sprint! I managed to connect the game manager to the local buzzer screen: it can now play songs and display their title in the answer card, and switches to a new song everytime an answer is given. I had no particular blockers when programming, and I also managed to make the emulator work reliably by recreating a device. However, the CI sometimes fails on code of activities that are not mine, which is very confusing.
My tasks this sprint went more or less smoothly, the only issue I had is in one of my PR: the checks on CI failed because a view cannot be found. However, when I run them locally, all the tests pass. I spent some time trying to understand what was going on, luckily, my teammate helped me solve the problem. I also encountered another weird thing which is if I use string.xml the lines were considered non-tested, but if I use hard-coded strings, it was not the case.
This week, our overall progress was rather smooth, except for some CI issues. Most of us got a good amount of work done, and we helped each other clear questions. We noticed various bugs and made a bug list which is being updated actively, and is being treated actively as well. Overall, our teamwork was great.