Week 9 Retrospectives

Group Status Report

Status

Morale

Inidividual Status Reports

Alberto

• What went well:
  

  This week we focused on end-to-end testing, integrating JSDocs, adding code coverage and overall UI polishing to prep for the demo. Because everyone cares about the impression we give to the professor and fellow classmates, we have all been working hard to get the MVP to the best state possible before the practice demo with the Professor. The hard work and determination have been a constant for the whole team throughout the quarter.

• What I learned this week:
  

  I submitted my first PR for some UI polishes. So far I hadn't coded as I mainly focused on documentation and planning, class presentations and overall status reports. I also felt like the dev teams did not need additional resources. However, because I enjoy design, I wanted to contribute to the project by making a few changes that I felt like would make the overall app appear better. Overall throughout the process, but it was reaffirmed to me this week, I learned that you don't necessarily have to be coding to be contributing to the project. Even though there was always this idea in the back of my head that told me I was not being useful because I wasn't coding.

• What can I do to improve:
  

  I want to be less afraid of taking initiative.

• Inidividual morale:
  

  I am feeling good as our MVP is in a great state. There is definitely some UI polishing we can still do but it's a great milestone that we have reached. These next two weeks will be a lot of documentation review which I am conscious I will be spending a good amount of time on.

Alex

• What went well:
  

  We accomplished so much this week! We integrated JS Docs and Cypress in to our development workflow and GitHub Actions. We also got a big upgrade to our landing page, greatly improved our test coverage, and cleaned up our code a bit.

• What I learned this week:
  

  I mostly learned a lot about how to write Cypress tests this week. In addition, I learned that our Cypress workflow on GitHub Actions saves downloadable screenshots of any failing tests so you can see what the screen looked like when a check failed!

• What can I do to improve:
  

  Honestly, get a new computer. It slows down my productivity so much, and I probably spent 10+ hours fixing my local environment this week, which shouldn't be something you spend time on this late into a project. My time could be better spent on other tasks.

• Inidividual morale:
  

  My morale this week is quite better than previous weeks. I really feel like I'm contributing more significantly than before, which was something that had been bothering me a lot. Our team is pumping out great quality work, and I think we're on a reasonable pace to have a complete product to submit next week without scrambling at the last minute. My only stress currently is balancing time to study for the course alongside our remaining tasks and finding time to sleep. So proud of everyone's work this week!

Chang

• What went well:
  

  This week we finished Cypress End-to-end testing and deployed JSDoc and test coverage report to GitHub Pages.

• What I learned this week:
  

  How to write Cypress test and how to use GitHub Actions to deploy GitHub Pages.

• What can I do to improve:
  

  Add Emoji and avatar to our app.

• Inidividual morale:
  

  Keep working on our chat app.

Dian

• What went well:
  

  We added Cypress end-to-end testing and jsdoc generation this week to make our project more error-free and standard. We also tweaked some UI and github workflows to make our interface more friendly and deployment more smoothly.

• What I learned this week:
  

  I learned that how jsdoc is generated through github action and end-to-end testing suite/tool called Cypress. All the testing related stuff can be automated using Github actions.

• What can I do to improve:
  

  I should learn more about Cypress on how to write standard code and play with the interface to see how tests go along with the test.

• Inidividual morale:
  

  Our app is ready to go, in terms of functionality and test coverage. I have confidence on our demo and presentation later.

Edward

• What went well:
  

  This week I was able to increase some of our test coverage and implement a new landing page for our web application. Overall, I think I was able to contribute to the polish of our project.

• What I learned this week:
  

  Learned some more CSS and image animations working on the landing page!

• What can I do to improve:
  

  Overall, I've been finding some minor bugs with the code that I have committed so far. Although we have a great CI/CD pipeline in place to help push out faster changes, I should also hold myself to a higher standard. Additionally, I'd like to reduce the number of iterations I need to do on my code reviews.

• Inidividual morale:
  

  Feeling pretty good that everything is coming together!

Jason

• What went well:
  

  We have further polished our project and everything is on track!

• What I learned this week:
  

  I learned more about DevOps, and Cypress things.

• What can I do to improve:
  

  I should write better reviews to avoid confusion.

• Inidividual morale:
  

  Good!