Posts

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://v...

My current state accroding to Software Craftsman

  Before this reading, I mostly thought about becoming a “good developer” in terms of technical skills, knowing more languages, frameworks, and tools, and use them according to what was needed to reach the goal. However, the book shifts focus on identity and long-term growth. It argues that being a Software Craftsman is not just about competence; it is about commitment to mastery. The three stages—apprentice, journeyman, and master—made the abstract idea of growth feel structured and personal. I strongly identify with the apprentice stage. The idea that everyone begins with “Hello World,” but what differentiates people is how they approach growth afterward, really resonated with me. The journeyman stage was interesting because it expands responsibility outward. It is not enough to just improve personally; you begin contributing to others and strengthening the community. But something interesting is that reality of modern software development is that you may be with a single tea...

Junit Testing and its basic

  The article “JUnit Testing: The Basics and a Quick Tutorial” explains the fundamentals of Junit and how it works in testing environment. The author begins by describing unit testing as the process of verifying small pieces of code independently, ensuring each component behaves correctly before integrating it into a full application. JUnit supports this by allowing developers to write automated tests using annotations and assertions that compare expected and actual results. The article highlights that testing early improves code quality, helps detect bugs quickly, and supports continuous integration workflows. It also introduces major features such as annotations, assertions, parameterized tests, and exception testing. Finally, the tutorial demonstrates how to install JUnit, write a simple test class, and run tests from an IDE or command line. I selected this resource because I am currently learning software testing and writing unit tests myself. This article is short but sum...