After our First Sprint session ends

        During this sprint, our team focused primarily on researching and evaluating automated testing tools that could be used in our project. Since our team was the first to create a test, using tools for future use, much of our work involved reviewing documentation, checking for updates and if it is opensource, experimenting with different testing frameworks, and discussing which tools would best support our development workflow. Although there are currently no major commits or issues in GitLab yet, the sprint involved important groundwork for establishing our testing strategy. Even though there are no GitLab commits yet, the following resources were the main candidates for the tools we will use and evaluate the most visiting numerous documentations, videos, review and blogposts.:

  • https://playwright.dev/docs/intro  – Reviewed documentation to understand how Playwright performs end-to-end testing and browser automation.
  • https://vitest.dev/guide/  – Studied Vitest documentation to understand how it integrates with modern JavaScript frameworks for unit testing.
  • https://docs.cypress.io/app/get-started/why-cypress – Evaluated Cypress as another potential testing tool and compared its features with Playwright.

Even though this is not the only test tools and resources we checked, those were main that helped us understand the testing ecosystem and evaluate which tools would best fit our project.

        One thing that worked well during this sprint was the team’s ability to quickly explore different testing frameworks and discuss their advantages and limitations. By reviewing documentation and experimenting locally, I was able to gain a better understanding of how automated testing works in modern web development. In particular, I learned about the differences between unit testing frameworks and end-to-end testing tools. With careful examinations, I was able to use and write basic test using both tools. With the knowledge gained, we were able to communicate our findings and share pros and cons of each tools fast so we don’t have to use more time on single tool.

The biggest difficulty was the large number of testing tools available. Each framework has its own documentation, setup process, and recommended workflows. Sorting through these options required significant time and discussion to determine which tools would best fit our project as there were numbers of options. This made it sometimes difficult to keep track of progress as we had to test so many different tools at the same time, which caused some conflicts locally.

As a team, we could improve our communication during meetings and discussions. At times, some ideas or concerns may not be clearly voiced, which can make it harder for everyone to stay aligned on decisions. Making sure that team members speak up clearly and share their thoughts more openly would help ensure that important points are not missed.

I would have liked to spend more time experimenting with small example projects using different tools as there were long lists of how to use each tools efficiently or at specific cases with new updates and features coming up. This hands-on practice would help deepen my understanding of testing frameworks and make it easier to implement them later in the project.

The apprenticeship pattern I selected is “Be the Worst.” This pattern encourages developers to place themselves in environments where they are surrounded by people who are more experienced or knowledgeable than they are. By doing so, they are constantly challenged to learn new skills and improve their abilities. I selected this pattern because it reflects my experience during this sprint. While exploring different testing frameworks, I realized that there is a large amount of knowledge involved in automated testing that I am still learning. Reading documentation and seeing how professional developers structure testing environments made me aware of how much there is still to understand. If I had read this pattern earlier, I might have approached the sprint with a stronger focus on learning from others’ expertise. I would not have just be on entry level tutorial videos, blogs, posts and simple tasks for the research and went through more in-depth use cases that might be helpful for the project. Overall, this sprint provided a strong introduction to automated testing tools and laid the groundwork for implementing a testing strategy in our project.

 

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