This is the 4th part of the series about analyzing our code and deciding what to test. Last time, we talked about design constraints. Now we’re moving towards the code itself. Almost there. Step 6: Prepare existing code This is an obvious step Read more…
This is the 3rd part of the series about analyzing what we’re coding, and therefore what to test. Last time, we talked about test categorization and design considerations regarding testability. We haven’t touched or written any code yet. Nor will we Read more…
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 Read more…
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 Read more…
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, Read more…
“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 Read more…
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 Read more…
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 Read more…
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 Read more…
“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 Read more…
