Posts

Aftermath of Sprint 3

During Sprint 3, our team continued working on automated testing, but this sprint was different from the previous one because we moved further from setup research into more in depth writing and improving tests. In Sprint 2, much of the work focused on trying to get Vitest and Playwright working inside Docker and understanding why the testing environment was failing. In Sprint 3, I focused more on rebuilding my local setup, reinstalling necessary software, checking that the development environment was usable, and writing tests that could become part of the project workflow. This included fixing issues with VS Code, Docker, dependencies, and the project files so that the test tools could run more consistently. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/tree/frontend_testing_release2026?ref_type=heads (since I had problems in my computer asked to upload from other teammates One thing that worked well during this sprint was t...
Post a Comment
Read more

Technical Review in Software Testing

  The resource I selected is TestSigma’s article, “What is Technical Review in Software Testing?” The article explains that a technical review is a structured evaluation of software artifacts such as code, design documents, test plans, requirements, architecture, and test cases. Its main purpose is to find defects early in the software development life cycle before they become more expensive and harder to fix later. The article describes technical review as a static testing technique because it can identify problems without actually running the software. It also explains different types of reviews, including code reviews, design reviews, requirements reviews, test plan reviews, test case reviews, architecture reviews, and document reviews. The article also outlines a basic review process: planning, preparation, review meeting, approval, and documentation.              I selected this resource because I have been work...
Post a Comment
Read more

More of Test Doubles

  The blog post I selected is “Understanding Test Doubles - Fakes, Stubs, Mocks, and Spies” by Sarah Dutkiewicz. I chose this resource because it gives our view of how we do test doubles with better examples for class as it explains several kinds of test doubles and shows how each one supports more focused and maintainable tests through concrete code examples. The article explains that “test doubles” is an umbrella term for objects that replace real dependencies during testing, and that not all doubles should be used in the same way. The post explains that fakes are simple working implementations made for testing, stubs return pre-programmed responses, mocks are used to verify that certain interactions happened, and spies record calls so the test can inspect them later. It continues to uses small C# examples with interfaces like IUserRepository and IExternalService to show when each type is appropriate and why choosing the right one matters. It also emphasizes that using the wro...
Post a Comment
Read more