Java Testing Weekly 4 / 2018

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

  • Java EE vs Spring Testing describes why the author thinks that writing integration tests with Spring is easier than writing integration tests for "pure" Java EE web applications.
  • Testing of Microservices is a yet another blog post that describes how you can write automated tests for microservices. The interesting thing about this blog post is that it argues that you should focus more on integration tests than on traditional unit tests.

The Really Valuable Stuff

  • Don't be fooled by 100% code coverage is a good post that explains why it's not a good idea to aim for 100% code coverage.
  • IntegrationTest is an interesting article that explains the difference of narrow and broad integration tests, and argues that your test suite must contain both test types.
  • Three types of coding dojo for test automation introduces three different types of coding dojos that you can organize when you provide test automation "training" for your colleagues.
  • To TDD or not to TDD is an interesting post that explains the benefits of test-first and code-first approaches, and argues that you should use both approaches.

It's Time to Update Your Dependencies

0 comments… add one

Leave a Reply