Java Testing Weekly 33 / 2016

There are many software development blogs out there, but many of them don't publish testing articles on a regular basis.

Also, I have noticed that some software developers don't read blogs written by software testers.

That is a shame because I think that we can learn a lot from them.

That is why I decided to create a newsletter that shares the best testing articles which I found during the last week.

Let's get started.

Technical Stuff

  • Introduction to Unit Testing is a collection of free sample lessons of my Test With Spring course. These lessons help you to run your unit tests with Maven or Gradle and they explain how you can eliminate duplicate code by writing nested unit tests.
  • Unit Testing Anti-Pattern: Misleading Tests describes two unit tests that test the same method and explains why the first (and a more common) test is not as good as the second test. I won't explain the details here, but I have to admit that I have never thought about this, and now I am a bit shamed because the author has a point.

The Really Valuable Stuff

  • Mapping Biases to Testing: Confirmation Bias describes why it is dangerous to jump into a conclusion when you think that your assumptions are correct. This post helps you to identify the reasons that lead into hasty decisions. This is an important skill because recognizing those reasons will (hopefully) help you to avoid making hasty decisions.
  • Three top tips for using Given When Then gives you three tips that help you to write better documentation for the tested code by using the Given-When-Then syntax. I recommend that you take a look at this blog post because I think it is useful to you even if you don't use BDD. For example, I realized that I can use the these tips when I am naming my "normal" test methods.
  • Integration and Integrated Part 1 and Part 2 explain the different between an integration test and an integrated test. When I first heard these terms, I thought that they mean the same thing. However, this is not true.

It's Time for Feedback

Because I want to make this newsletter worth your time, I am asking you to help me make it better.

P.S. If you want to make sure that you don't ever miss Java Testing Weekly, you should subscribe my newsletter.

0 comments… add one

Leave a Reply