Java Testing Weekly 24 / 2017

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

  • Cleaner parameterized tests with JUnit 5 provides a quick introduction to writing parameterized tests with JUnit 5. It describes how you can write your first parameterized test and explains how you can use different argument sources such as methods and CSV files.
  • Testing exceptions with JUnit 5 describes how you can write assertions for the exceptions thrown by the system under test.

The Really Valuable Stuff

  • Fill the Gap is a thought-provoking blog post that tells the story of a bug that was fixed when the author decided to stop waiting for developers to fix it and took matters into her own hands.
  • How often you should run your automation identifies four different strategies that you can use when you decide how often you want to run your automated tests and describes when you should use each strategy.
  • Should Automation Find Bugs? is an excellent blog post which argues that it's not a good thing if your automated tests find bugs after you have committed your changes to the master branch. This post also identifies four problems that prevent the author's team to catch these problems before the code is committed to the master branch.

It's Time to Update Your Dependencies

No updates this week.

0 comments… add one

Leave a Reply