October 13, 2017
This is the 2nd part of the series about analyzing what we’re coding, and therefore which unit tests and integration tests to write. Last time, we talked about the problem we want to test (either unit tests, integration tests or… Continue Reading…
October 13, 2017
It’s been a while, but we’re not done yet. A new version of “Everyday Unit Testing” arrives! Let’s see what we have in this one: First of all, I’ve made “From Legacy To Testable Code” its own chapter. I’m not… Continue Reading…
October 13, 2017
This series of posts describes the process I use to decide which unit tests to write, and how to write them – regardless if the code already exists or not. This approach works for both TDD and test-after unit tests,… 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…
October 11, 2017
You think I was finished? I haven’t even started. The first group of associated costs to testing were around the fact that unit tests are, in fact, code and as such are susceptible to all kinds of flaws that come… Continue Reading…
October 9, 2017
We talked about what we perceive as the cost of unit tests: slowing us down. That does not mean that unit tests are free. There are actual costs associated with unit tests, although they may not be what you think. I… Continue Reading…