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.
- End-To-End Integration Testing For Kubernetes and OpenShift describes how you can write integration tests for your Kubernetes and OpenShift clusters by using only Arquillian Cube.
- JUnit 5 Tutorial: Writing Parameterized Tests describes how you can write parameterized tests with JUnit 5.
- Inheriting WebDriver Throughout Your Page Classes describes an alternative way of obtaining a reference to the used
- Running End-to-End Tests With Maven – Spock Edition is a free sample lesson of my Test With Spring course. It describes how you can create a Maven project that can run end-to-end tests which use Spock Framework.
The Really Valuable Stuff
- Excuses is a thought-provoking rant that compares TDD to double entry book keeping. The funniest part of this post is the long list of “arguments” against double entry book keeping which you won’t hear in real life.
- Mapping Biases to Testing – The Framing Effect is an interesting post that defines the term framing effect and describes why it can have a negative effect to your testing activities.
- No, I Didn’t Automate That Test explains why it might be a good idea to NOT write automated tests for your code.
- Test-Driven Developers: Building a testing culture is a thought-provoking blog post that starts by pointing out that most of us have worked on software projects that either have no tests or have tests that suck. After the author has described the problem, he divides automated tests into three categories and introduces four rules that help you to build (and enforce) a testing culture.