Java Testing Weekly 19 / 2016

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

  • JUnit 5 - Conditions provides a comprehensive introduction to the programmatic conditional test execution API of JUnit 5. This is an excellent blog post, and if you are interested in JUnit 5, you must read it.
  • Mockito's Mock Methods is a practical blog post that helps you to create mock object with Mockito. If you need to start using Mockito in your unit tests, this blog post will help you to get started. However, if you have already used Mockito, this blog post isn't very useful to you.

The Really Valuable Stuff

  • Automation: Redirecting the Magic Bullet is a thought provoking blog post that describes why automated testing feels "safer" that testing. It also explains how automated testing help developers to be better testers and describes why this is a good thing.
  • Code Naked is an entertaining blog post that describes the discussion of two developers. The first developer tries to explain to the second developer why he cannot marge the pull request made by the second developers because it has no automated tests. Unfortunately, the second developer doesn't seem to get it.
  • First steps into testing in a Continuous Delivery setting describes the basics of creating an optimal test strategy for projects which use continuous delivery. It provides good tips that help you to write automated tests on right level. Also, this post gives you a few ideas that help you to utilize testers outside the continuous delivery pipeline.
  • Performance Engineering and Load Testing: A Changing Dynamic in an excellent blog post that identifies techniques that are often used as a replacement for load testing and describes why load testing is a better choice (when it is done properly). I like this post because I have noticed that load testing is (sadly) often done improperly or left to he users of the application. Although letting our users to do load testing might make sense in certain situations, most of the time this decision is made because we have no other choice. In other words, we let our users to do this because we have no time or money to do it our self. That is why I think that is important that we don't forget the value of load testing and understand that not doing it is almost always a mistake.
  • Software testing is not … part 3 explains why software testing cannot be done by irreplaceable robots. This myth makes me irritated because most of the time the people who believe in it only want to save costs. Also, I have noticed that they don't really care whether their developers write automated tests or not. In fact, often they think that automated testing is just an unnecessary expense (like testing) because we can let our customers test our software. It's insane.
  • The Ultimate Tester: Curiosity describes why curiosity is a very useful trait for a tester and explains how curiosity will help a tester to identify good test cases. This post made me realize that testers and developers are not that different. A good developer is also curious and always looking for better ways to solve the same problem.


It's Time for Feedback

Because I want to make this newsletter worth your time, I am asking you to help me make it better.

P.S. If you want to make sure that you don't ever miss Java Testing Weekly, you should subscribe my newsletter.

0 comments… add one

Leave a Reply