There are many different types of testing, and unfortunately, there isn’t a clean line between the different definitions. With that said, here are the characteristics that generally describe different types of testing.

We have other guides on the common mistakes committed when writing unit tests, and it’s important to understand and recognize when we’re making these mistakes. But even more important is learning how to avoid them in the first place. In this chapter, we’ll discuss exactly this!

If you’ve made it this far into our unit testing guide, then you probably agree that writing unit tests is a good thing. But often, developers still don’t write as many unit tests as they should. Why is that?

Now that you’ve created your first unit test, learned how to calculate code coverage with JaCoCo, and started to make a more comprehensive test suite, it’s time to learn a slightly more advanced unit testing skill: mocking.

Welcome back to the Definitive Guide to Unit Testing! In this chapter, we will address how to create a complete test suite.

If you’re read Chapter 1 of the Definitive Guide to Unit Testing, then you already know the basics of unit testing and may have even created your first unit test. You’re probably wondering how these tests can combine to create a comprehensive test suite (and how many of these tests you’ll need to write). In this chapter, we’ll talk about code coverage and how to measure it.

Unit testing is really important for code quality (and for making your life easier when hunting for bugs), but if you’ve never done it before, where do you begin? To help out, we’re sharing the Definitive Guide to Unit Testing. 

If you’re looking for resources to help you learn about DevOps, our informal book club has come up with the top 5 DevOps books, covering topics that will help teams and individuals get started or streamline existing processes.