March 13, 2016
When we talked about understanding what we’re actually testing in error handling, we talked about the ability to understand the behavior of our code-under-test . Just to recall, here are the three types of error implementation, and what we can… Continue Reading…
October 3, 2023
One of the things that unit tests are best for is checking error conditions. While we want wider coverage of full happy flows, error conditions are sometimes hard to simulate in a big system, and unit tests excel at minimal setup to… Continue Reading…
October 12, 2017
“Why do we need unit tests?” Seems like a silly question. We want to check if something is working, right? Let’s dig deeper, though. At the time of writing, if we’re using test-first or TDD, we’re designing interfaces, apply usage… Continue Reading…
October 12, 2017
In “Should I use multiple asserts” we described the problem when using them in a single unit test. In the example I gave, while checking the result of a single operation, it still made sense to get information on both… Continue Reading…
October 12, 2017
I get this unit testing question often. It makes efficient sense to stuff all kinds of assertions after a single setup and invocation. While there’s no one answer, for me, it usually comes down to: Try to separate rather than join… Continue Reading…
October 11, 2017
As we’ve seen already, we don’t have to write every unit test possible, since not every unit test is going to help us in the future, and may even cause us some problems. Here’s an actual example I encountered. I’ll… Continue Reading…
October 11, 2017
“Is this a good unit test?” Usually the question refers to a test that somebody has already written. But are these unit tests effective? Should we have written it in the first place? That’s right, we don’t need to test… Continue Reading…