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

  • Protractor Tutorial: example project setup is a good tutorial that explains how you can install the required tools, configure your project, and write your first test with Protractor.
  • Spring Boot and Gradle: Separating Tests describes 4 different options that you can use when you want to separate your unit and integration tests. The goal of this post is to explain how you can run only unit or integration tests when you are using Gradle.
  • Testing Apache Camel Applications with Spring Boot explains how you can write unit tests for Apache Camel routes by using the Spring Test Framework.

The Really Valuable Stuff

  • 8 Reasons why Software Testing is Harder than Development. This is an interesting and thought provoking post. If you take the time to read this blog post, I suspect that you will have more respect for testing (and testers).
  • Manage your biases as a tester – Part 3/4 identifies and describes six cognitive biases that are caused by "Need to act fast".
  • Thoughts: Accessibility testing for the web is a blog post that explains why accessibility is important and gives you some pointers that help you to start doing accessibility testing.
  • Risk-based release testing is an excellent blog post that describes how a single workshop helped a team to change their working habits. Before the workshop, they were doing traditional (and boring) testing. They simply followed a test plan and did not ask any questions. If you want to know what they started do after the workshop, you have to read this blog post.
  • Why Ask Why tells a story that explains why you should always ask the question why if you spot something that doesn't make any sense. This crucial because I think that "the actual testing" is only a small part of your job. You should also make sure that you solve the right problem, help your colleagues to grow, and try to make your workflow more efficient (work smarter, not harder).

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