The 10% discount ends 22nd of December. Get the master package of the Test With Spring course.

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

  • An introduction to property-based testing with JUnit-Quickcheck describes how you can write property based tests with JUnit and JUnit-Quickcheck. If you want to take your testing skills to the next level and go beyond static examples, you should definitely take a look at property based testing. In other words, read this blog post.
  • Concurrency testing with tempus-fugit describes how you can write tests for concurrent code by using JUnit and tempus-fugit library. It is not a complete tutorial, but it helps to write your first tests. If you need to write tests for concurrent code, but you don’t know how to do it, you should stop procrastinating and read this blog post.
  • JavaScript with Selenium WebDriver and Mocha describes how you can write end-to-end tests for your web application by using the official selenium bindings for Javascript and Mocha test framework. I like this post because it starts with the basics and introduces the more “advanced” stuff (setup methods, teardown methods, and page objects) after the author has already written a few tests. This way you can see how you can use these things for writing cleaner test code.
  • JUnit Testing Using Mockito and PowerMock describes how you can create mock objects with Mockito and PowerMock. I use Mockito every day, but I haven’t used PowerMock for a while. The reason for this is that if you are working in a greenfield project, you shouldn’t need to use PowerMock. However, If you are working with legacy code, which was not designed to be tested, PowerMock is a very useful tool. That is why every developer should know how (and when) to use it.

The Really Valuable Stuff

  • Load Testing Defined helps you to understand the importance of load testing and provides good advice on creating realistic load testing scenarios (HINT: look beyond the number of concurred users). If you want to get started with load testing, this post is a good place to start.
  • Mistakes is an excellent post that describes how fear can do serious damage to your career. Strictly speaking, this post doesn’t talk about testing, but I think that it is very relevant to developers as well. It seems that the author damaged her career because she didn’t want to get out of her comfort zone. If you have a negative attitude towards automated tests (or testing in general), are you sure that don’t suffer from the same problem?
  • My Favorite Resources For Testers And Test Automators provides a good sized list of testing resources. This list includes 10 blogs, 5 meetup groups (London area), 5 books, 3 conferences, and 3 educational resources. If you want to improve your testing skills, this list might be useful to you.
  • Predatory Testing defines the term predatory testing and helps you to hunt the bugs down by using each of your five senses. I enjoyed reading blog post, but I am not sure whether the author was serious or not. I guess you have to read this blog post and draw your own conclusions.

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.

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