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

  • JMockit 101 is the first part of baeldung’s JMockit tutorial, and it provides a practical introduction to JMockit. You will learn to specify expectations and create mock objects with JMockit. The most interesting thing about JMockit is that it has a totally different API than mockito. I am not sure if I like it, but I think that it is a good thing that we have multiple different mocking frameworks.
  • JUnit 5 M1 announces the release of JUnit 5 M1. The first milestone release concentrated on providing stable APIs for IDEs and other build tools. Also, it included a new feature called dynamic tests. If you want to know more about dynamic tests, you should read this blog post.
  • Robot Framework Tutorial 2016 – Integration with Jenkins describes how you can integrate Robot Framework with Jenkins CI server. This post provides step-by-step instructions and it has a lot screenshots. In other words, you should be able to get the job done as long as you follow the instructions.
  • Testing with Hamcrest is basically a cheat sheet that describes how you can use different Hamcrest matchers. This post is useful to both beginners and more advanced users because it can be used as a “reference manual”.

The Really Valuable Stuff

  • Test environments and organizational aspects is a really interesting post because tells two stories. The first story is describes the pros and cons of using mocks and stubs for isolating the system under test from its dependencies. The second one describes how organizational aspects might limit your choices or increase them. The second story made me realize how lucky I am when I work for a company that isn’t afraid to spend money. There is basically “zero” bureaucracy and I feel that our IT department is working for me. All this feels so natural to me that I am always surprised to see that all companies do not act this way.
  • The tester and technical debt is a great post because it provides one excellent insight: technical debt is typically born by accident. The thing is that most of us don’t decide that today is the day when we create technical debt. Instead we make small decisions every day, and one day we realize that our codebase is not as good as it should be. When we realize this, we don’t take responsibility of our actions. We simply call it technical debt and “move on”. I think it’s ironic (and extremely satisfying) that this post provides the best description of technical debt which I have ever read. And, it was written by a tester.
  • Should developers own acceptance tests? argues that acceptance tests should be owned by the team. I think that this is a good idea because of two reasons: First, developers typically don’t have time to own everything and if developers would own acceptance tests, they would not probably write them. Second, testers are good at designing test cases and they typically don’t want to automate everything. If developers would would own acceptance tests, they would probably automate them and this is not always a good thing.
  • We Are Not Gatekeepers is an excellent post that describes why testers are not responsible of quality assurance and they don’t decide when something can be deployed to production. I am not sure why some people don’t get this, but I suspect that these people don’t want to take responsibility of their actions and decisions. Do you agree?

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.

  • If you have any feedback about this newsletter, share your thoughts on the comment section.
  • If you have written a blog post about automated testing or software testing, ping me on Twitter.
  • [You can share this blog post on Twitter](https://www.twitter.com/share/?text=Java Testing Weekly 28 / 2016 by @petrikainulaine - &url=http://www.petrikainulainen.net/weekly/java-testing-weekly-28-2016/).

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