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

  • Docker makes database integration testing so much easier describes how you can run your integration tests against a database that is running inside a Docker container. This is a really cool trick because managing multiple databases by using the traditional way can be quite painful.
  • Extending Selenium with Image recognition describes how you can integrate Sikuli with Selenium. If you need write tests for a web application that uses Flash or has a complex DOM tree, you should take a look at this blog post.
  • Java Automation with Serenity provides a quick introduction to Serenity that is an automated acceptance testing framework. This is a quite long post, but if you are interested in new frameworks, you should read this blog post. I am not sure if I will start using Serenity, but I got a few ideas which I will incorporate into my own test suites.
  • Ruling Database Testing with DBUnit Rules is a good blog post that describes how you can initialize your database into a known state before your integration tests are run by using the DBUnit Rules library. As you probably guessed, the DBUnit Rules library provides a set of JUnit 4 rules which you can use for this purpose.
  • Testing REST Endpoints Using REST Assured describes how you can write end-to-end tests for a REST API with Rest Assured. Even though this post provides a good introduction to Rest Assured, it is a shame that it doesn't describe how you can initialize your database into a known state before you run your end-to-end tests. Maybe you should consider using DBUnit Rules?
  • The Librarian: Introduction to Test-Driven Development provides a quick introduction to TDD. The author states that this post is targeted to: "junior developers who want to expand their testing horizon". In other words, if you have no experience from TDD, you should take a look at this blog post.
  • Selenium and what it is not busts four myths about Selenium. I have to admit that I had no idea that someone would think that Selenium is an API testing tool or a performance testing tool. I guess that is why we shouldn't write blog posts only about advanced topics. I think that writing occasional post that is targeted for beginners is a nice way to pay back to all of those people who helped us when we had no clue about software development.

The Test With Spring course helps you to write automated tests for Spring and Spring Boot web applications.


The Really Valuable Stuff

  • Good Reasons NOT to Log Bugs identifies seven reasons why logging bugs is a bad idea. This is an excellent blog post. I think that there are a few situations when it is a good idea to use an issue tracking tool, but most of the time Jira (or some other issue tracking tool) is a place where bugs go to die in old age.
  • Opportunities and Threats Part Two: Threats identifies different threats that can have a negative effect to testing as a profession. This is a really interesting blog post because I recognized that some of these threats are very real for software developers as well.
  • Pragmatic Integration Testing describes how you can you can write better integration tests. It is hard to write integration tests for code that uses external systems or APIs, and this post provides a few good tips that help you to tackle some of the problems caused by "external dependencies".

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