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

  • Catching up with Allure. Part 2: report generating describes how you can create an Allure data file and create a test report from the contents of that file.
  • Creating executable specifications with Spectrum explains how you can get started with Spectrum and describes how you can write specifications by using both describe/it and given/when/then syntax.
  • Gatling Load Testing Part 2 – Extending Gatling is a very comprehensive blog post that helps you to identify the building blocks of a Gatling extension and describes how you can create your own Gatling extension.
  • Grails 3.3 Integration Testing with Spock Mocks explains how you can create a mock bean and use this bean when you write integration tests for your Grails application by using Spock Framework.
  • Migrating from JUnit 4 to JUnit 5 is a straightforward post that identifies the differences between JUnit 4 and JUnit 5. This information will help you to migrate your existing tests from JUnit 4 to JUnit 5.
  • Mocks or the real thing? Tips for better unit testing is a good blog post that explains why you shouldn't "abuse" the cool features of mocking frameworks (such as mocking static methods or constructor calls). Instead, you should concentrate on making your code more testable so that you don't have to resort to these ugly hacks.

The Really Valuable Stuff

  • Leadership in Unit Testing Implementation, Part II is an interesting blog post that explains how metrics can cause unwanted side effects if they are not used properly. Also, this post explains that managers can help you to solve this problem by encouraging developers to share their experiences (both good and bad) with their colleagues.
  • Test Automation Canvas introduces an interesting tool that help you to analyze and review your test automation efforts. I recommend that you take a look at this blog post because I think that this tool will also help you to explain what you do and why you do it.

It's Time to Update Your Dependencies

2 comments… add one
  • Java Spring Master Aug 17, 2017 @ 17:52

    How about adding a few words to describe the java test week?

    • Petri Aug 17, 2017 @ 19:07


      Could you clarify what you mean?

Leave a Reply