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.
- Testing on the Toilet: What Makes a Good End-to-End Test? identifies four characteristics of a good end-to-end test and introduces three caveats that you must take into account when you write end-to-end tests.
The Really Valuable Stuff
- 8 Reasons Johnny Does Not Write Bug Free Code explains why writing bug free code is so hard. As you probably figured out, the author introduces eight reasons that prevents programmers from doing this. My favorite is batch programming. What’s your favorite?
- Accessibility testing crash course is an excellent blog post that describes why you should do accessibility testing, helps you to understand the basic principles of accessibility testing, and provides a list of the author’s favorite accessibility testing tools. If you have time to read only one blog post, it should be this one.
- Fighting the urge for Jira is an interesting post that describes an alternative (and probably a somewhat harder) way for dealing with bugs and issues found from the tested code.
- How to Train Up a New Software Tester provides a quite comprehensive list of tips that helps to train up a new tester. By the way, I think that you can use most of these tips even if you are training up a new developer.
- Pair Testing gives a simplified description of pair testing and describes what can happen if you decide to give it a shot. This post gave a me a “crazy” idea. What if a tester would pair test with a developer? I have no idea if this useful or interesting from the tester’s point of view, but I would be ready to find out an answer to that question.
- Shifting the furniture (a cautionary tale) tells an intriguing story that helps you to understand that good intentions do not guarantee good results.
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.
P.S. If you want to make sure that you don’t ever miss Java Testing Weekly, you should subscribe my newsletter.