Java Testing Weekly 18 / 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

  • Introduction to Serenity BDD describes the core concepts of Serenity, explains how you can write simple tests with Serenity, and helps you integrate Serenity with JBehave, Rest Assured, and Jira.
  • Spring From the Trenches: Cleaning Up Our Test Code With HTTP Request Builders describes how you can remove duplicate code from your test suite when you write unit and/or integration tests with Spring MVC Test framework.
  • Spock testing framework versus JUnit identifies five big differences between the Spock Framework and JUnit 4. Even though the author states you can draw your own conclusions after you have read the blog post, I think that he is trying to get you to ditch JUnit and start using Spock Framework. There is nothing wrong with that though. Spock is a great framework. That being said, all JUnit 4 specific problems mentioned by this post are fixed in JUnit 5.
  • Testing Spring Data + Spring Boot applications with Arquillian (Part 1) describes how you can write integration tests for a code that uses Spring Data Redis. To be more specific, this post explains how you can start and stop a Redis server before your test methods are run by using Docker and Arquillian.
  • Using JsonPath and XmlPath in REST Assured provides 4 tips that help you use JsonPath and XmlPath when you are writing API tests with Rest Assured.

The Really Valuable Stuff

  • Epic Fails is an interesting post that explains why people don't necessarily start a tool or a framework that is handed over to them. If you cannot convince your colleagues to start writing tests or to use a new (and a better) tool, you should take a look at this blog post.
  • Why Your Automation Is Never “Done” identifies three reasons why your automation is never finished and explains how it can still provide tremendous value.
  • Experimenting with a Zero Bug policy is an interesting post that defines the term zero bug policy, explains the problems caused by open bugs, and describes how a zero bug policy works in practice. Also, this post describes both the pros and cons of the zero bug policy.

It's Time to Update Your Dependencies

0 comments… add one

Leave a Reply