After the second sprint

 

During this sprint, our team focused on setting up automated testing tools within our development environment, working with Vitest and Playwright. Unlike the previous sprint where we mainly researched tools, this time we attempted to implement them into our actual project workflow using Docker. A large portion of the work involved configuring the environment, installing dependencies, and troubleshooting issues that prevented the tools from running correctly. Although there are limited successful GitLab commits due to setup failures, the effort was focused on building the foundation for testing integration. However, we were able to get a working version that can be used as a base for every test.

First half-working git commit : https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/commit/9382538b27224d0d6ffc4815798cfe0207040781

One thing that worked well during this sprint was persistence in troubleshooting. Even though the setup failed multiple times, I was able to better understand how testing tools interact with development environments, especially when using Docker. I was able to test different ways to install dependencies in containers having problems with paths and execution. With these experience, it built stronger understanding of the system and how to update or fix current code while working with other team correctly.

The biggest difficulty during this sprint was dealing with environment and configuration issues. Setting up Vitest and Playwright inside Docker proved to be more complex than expected, and many attempts resulted in errors or incomplete installations. The steps were one work the other did not work vice versa. Because of this, a lot of time was spent retrying similar steps without fully isolating the root cause of the problems. Additionally, dependency conflicts and differences between local and container environments made debugging more difficult.

As the team, sharing clear documentation of what has been tried and what errors occurred would help prevent repeated work and improve collaboration. However, it could have been hard as some errors were faulty of the local machine as what worked for me did not work for the teammates and so on. If we were able to document this well and share it better with teammates, we might have found the solution faster

Individually, I could improve by approaching debugging in a more structured way. Instead of repeating full installation attempts, I should focus on isolating specific issues and testing smaller components step by step. Also, I need to double check if my local setting is same as others because it seems like what is working for me does not work for others or it could be the other way around.

The apprenticeship pattern I selected is “Use the Source.” This pattern emphasizes learning directly from official documentation, source code, and primary resources rather than relying only on tutorials or secondary explanations. I selected this pattern because it strongly relates to my experience during this sprint. While trying to set up Vitest and Playwright, I often relied on mixed sources such as blog posts or videos, which sometimes conflicted with each other or were outdated. Overall, this sprint was challenging but still valuable. Even though I was not able to successfully complete the testing setup, I gained a deeper understanding of the complexities involved in configuring modern testing tools.

Comments

Post a Comment

Popular posts from this blog

Waterfall 2.0

  When looking around the internet, I found that there was waterfall 2.0 version of the waterfall software development methodology that we learned at start of class. After I saw the article, I found out that even the most established practices can transform to meet the demands of new era. Therefore, I chose this article as it provides basic summarization of waterfall 2.0 and the difference between traditional waterfall model. As we talked about why waterfall method was being replaced by agile and scrum, I thought there will be some people who will try to improve and use the old working method so using this article showed me how waterfall transformed to adopt need of current workflow. Therefore, I decided to look into it as a background for finding out about the improved version as it revives the dying method into a new form.              This article uses baking as an example to illustrate the principles of waterfall 2...
Read more

Is Agile going to fail?

  This article by Jeff Gothelf asks the question “Is Agile finally over?” after 20+ years of implementation to tech field. He argues that even though Agile’s widespread adaptation hasn’t got the result that Agile was intended for. Many companies claimed to be “Agile” as they copy each other, but the implementation of it was shallow or almost non-existent to make changes according to it. Therefore, he says that agile does not seems working as companies try to make employee follow set of rules instead of working in following the basic principles of Agile. He concluded that organizations need to focus on true organizational agility rather than rigid framework adoption. This article caught my attention while searching through the internet as it criticizes Agile’s current status in the business world as ideal of agile does not really fit in reality in organization experience. The vague promises and core ideas are often overlooked to the ‘wants’ of either customer or the organization...
Read more

Docker and it basics

     Since I use different computers from home, class, and work, after learning from class about docker and setting up the same environment for all the devices, I thought it was time to look into docker more. The article is about what is docker, why it became popular and comparing it with other tools. That is why I choose this article because “Docker overview” by Marsdev gives comprehensive introduction about docker, comparing to virtual machine, use cases and advantage over other tools over the internet. It clearly explains these things easily and detailed make it ideal choice to learn how docker works and its benefits.      The article covers essential components of Docker including Docker Engine, Images, Dockerfiles, Docker Hub, Volumes, Compose, and Desktop and how they work. For example, Docker Engine serves as the backbone of the platform, enabling the creation and management of containers, while Docker Compose allows developers to manage multiple...
Read more