I released the intermediate package of my Test With Spring course. Take a look at the course >>

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

  • My problem with the screenplay pattern is an interesting post which assumes that you have some experience from writing end-to-end tests. In any case, the author explains how the screenplay pattern should coexist with your page objects and describes how you should organize your test code if you decide to use this approach.
  • TDD with Spock, Groovy and Java provides a very quick introduction to TDD and describes how you can write unit tests for Java code with Spock Framework.
  • Testing Spring Data + Spring Boot applications with Arquillian (Part 2) improves the integration test written in the first part of this tutorial. To be more specific, this post explains how you can insert test data into the used Redis instance by using the Arquillian Persistence Extension (APE).
  • The tragedy of 100% code coverage provides two examples that demonstrate what can happen if you have a code coverage target (it doesn’t have to be 100%) or if you write pointless tests just because your boss ordered you to do it.

The Really Valuable Stuff

  • Five Factor Testing is a very interesting post that identifies five reasons (factors) why developers typically write tests and explains how you can use these factors as a framework that helps you to have useful discussions about your testing strategy.
  • Remember what your tests are trying to verify describes why you should (almost) always write end-to-end tests that mimic the behavior of a real user. In other words, this post explains why it’s a bad idea to “force” your test to do something that your users cannot do.

It’s Time to Update Your Dependencies

About the Author

Petri Kainulainen is passionate about software development and continuous improvement. He is specialized in software development with the Spring Framework and is the author of Spring Data book.

About Petri Kainulainen →

0 comments… add one

Leave a Comment