Posts

Equivalence Partitioning Testing

  The article “Comprehensive Guide to Equivalence Partitioning Testing” from TestGrid explains an important software testing technique used to design efficient test cases. Equivalence partitioning is a black-box testing method where input data is divided into groups, or “partitions,” that are expected to behave the same way in the system. Instead of testing every possible input value, testers can choose one representative value from each partition to verify the system’s behavior. This approach reduces the number of test cases while still maintaining good test coverage. The article explains how the equivalence partitioning is useful when the range of possible inputs is large and testing every value would be wasting time. By grouping similar inputs together, testers assume that if one value in the group works correctly, the rest of the values in that group should behave the same way. For example, if a form only accepts ages between 18 and 59, the test cases can be divided into thr...
Post a Comment
Read more

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...
Post a Comment
Read more

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...
Post a Comment
Read more