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.
- How I would approach creating automated user interface-driven tests is an educating blog post that describes what kind of tools the author would use if he would create a test suite for an application that is written with C#. Also, the second (and a very interesting) part of the blog post explains how the author would use these tools. And yes, I know that this newsletter is called Java Testing Weekly, but I think that you can learn something by reading this blog post.
- Introduction to Selenium WebDriver is a free sample lesson of my Test With Spring course. It provides a (very) quick introduction to Selenium WebDriver, identifies the key components of your end-to-end tests, and describes how you can get the required dependencies with Maven and Gradle.
- Test Doubles – Fakes, Mocks and Stubs describes these three test doubles and provides some examples that help you to understand when you should use them.
The Really Valuable Stuff
- Ditching Traditional XML Parsing is an interesting post that explains why the author decided to ditch fancier methods for creating XML documents and use strings instead. The moral of this story is that sometimes when we create input data for our automated tests, we should pick the simplest way to do it.
- The Myth of Automating without Exploring is a short and an excellent blog post which argues that you cannot create a meaningful test suite if you writing test code without thinking what you do and why you do it.
- Why and how you should test your software is the second draft of a talk the author will give at PyCon 2017. This post tries to answer to these two question: 1) why should you test your software? and 2) how should you test your software?