Joshua's Blog

The semester is quickly coming to an end, and so for my third blog post, I read " Black Box vs White Box Testing - What's the Difference? ", written by Faith Quinn. As the title suggests, it touches on one of the course topics (in this case one that we have been over already, unlike my previous blogs): Specification-Based vs Code-Based Testing, otherwise known as Black Box vs White Box Testing. To quickly summarize what exactly that is; black box testing is when you focus on the expected behavior of the software without looking at the code itself, while white box testing is when you use knowledge of the internal code structure to design tests. Quinn’s post explains the difference between the two approaches, and also shows that both can be useful depending on what kind of problem you are trying to find. This made the post a good fit for the class because it connects directly to one of the main testing ideas we discussed during the semester. I chose this particular resource...

We are nearing the end of the semester, and with that have completed our second sprint. It has formally spanned from the 5th of March to the 7th of April, a week shorter than was initially planned due to what I believe were time constraints. Our sprint consisted of four goals, and of those goals we were able to complete two. The sprint was largely divided into two "parts". The first part is what we actually completed; the "prep-work". This involved the necessary preparations our team needed to start test development, which consisted of creating a new branch dedicated to frontend-testing (our team), and building a new container that had the necessary testing tools needed for our tests. These necessary tools were Playwright and Vitest.  The second part, and the part we did not finish, was themed around the actual test development. This involved all of us independently writing draft-tests , to help us formalize a methodology we could follow, as a group, when writing ...