go back to the blog

Blog Spy Vol 34: A Weekly Round-up From The Software Testing Blogosphere

  • 02/10/2013
  • no comments
  • Posted by EuroSTAR

A round up of some of the latest blog posts from the Software Testing Industry in the past week. If you would like to have your blog featured in our regular round-up, please email details and a link to the post to [email protected] or tweet us @esconfs.


Upcoming Testing Conferences – Our way to EuroSTAR – Michael Herrmann

After winning a free place at this year’s EuroSTAR Conference from Ministry of Testing, Michael Herrmann on how he won the ticket to EuroSTAR. Read all about it here.


Interview Questions – Michael Bolton

“Imagine that you are working for me, and that I want your help in qualifying and hiring new staff. I start by giving you my idea of how to interview a candidate for a job.” Read more here.


Going Exploratory – Erik Brickarp

Erik shares the lessons he has learned after joining a new team at work. Read more here.


Test Automation – Finding your starting point – Martijn de Vrieze

“The other day I had a job coaching of a colleague who, for his assignment, needs to start setting up test automation within an agile environment. He is very interested in test automation and the possibilities it gives you, however his knowledge on the subject, as well as on coding, is very limited.

In preparation for this first coaching session with him I was pondering where to start with him and I ended up starting with the, to me, obvious points.” Read more here.


Alternative Uses for Fiddler – Alan Richardson

“A few days ago I realised that one of my use cases for Fiddler, did not stem from a need for debug proxying.” Read more here.


Blaming the Tester – Adam Knight

“It has been my unfortunate experience more than once to have to defend my testing approach to customers. On each occasion has been deemed necessary in the light of an issue that the customer has encountered in the production use of a piece of software that I have been responsible for testing. I’m open to admitting when an issue that should have been detected was not. What has been particularly frustrating for me in these situations is when the presence of the issue in question, or at least the risk of it, had already been detected and raised by the testing team…” Read more here.


It’s not only about testing! – Joel Montvelisky

“It’s impossible to run all these tests in the time we’ve got left!”

“How many times have you said this phrase?

I know I’ve said it tens if not hundreds of times…

Looking back, I must have sounded like Star Trek’s Dr. McCoy with his:

“I’m a doctor, not a…”

Funny thing is that also looking back I think that about 80% of the times I said this phrase we were eventually able to release the project on time (or very close to it), either because we managed to run most of the tests we needed to run, or because (believe it or not!) we found a way to release the project without running all the tests we had planned…” Read more here.


How I interview: An exploratory approach – Benjamin Yaroch

“Recently Michael Bolton posted some Interview Questions as a thought experiment. This post prompted a bit of a discussion on twitter about how people interview. Like most I’ve interviewed and been interviewed countless times so I’ve experienced a wide array of methods, techniques, and approaches. Beyond that I minored in Human Resources so I’ve studied interviewing in-depth. As one might expect some interviewing methods are better than others and often what is best is based on the specific needs of the role and company. With that said I thought I would share my approach which has served me well over the last 8 years, your mileage may vary.

I use a framework that I adapted (stole) from testing, I call it Session-Based Exploratory Interviewing (SBEI). It’s based on Session-Based Exploratory Testing (SBET) created by Jon and James Bach.” Read more here.


What Really Matters in Developer Testing – Peter Provost

“Recently someone asked me to provide guidance to someone wanting “convince development teams to adopt TDD”. I wrote a rather long reply that was the seed leading to this article. My answer was simple: you cannot convince people to do Test-Driven Development (TDD). In fact, you should not even try because it focuses on the wrong thing.

TDD is a technique, not an objective.” Read more here.


Not “right”, but as good as I can do – James Christie

“In my last blog post I explained my concerns about the way that testers have traditionally adopted an excessively positivist attitude, i.e. they conducted testing as if it were a controlled scientific experiment that would allow them to announce definite, confident answers.

I restricted that article to my rejection of the positivist approach. However, I need to follow it up with my explanation of why I can’t accept the opposite position, that of the anti-positivist or interpretivist. The interpretivist would argue that there is no single, fixed reality. Everything we know is socially constructed. Researchers into social activities have to work with the subjects of the research, learning together and building a joint account of what reality might be. Everything is relative. There is no single truth, just truths.” Read more here.

Blog post by

go back to the blog


Leave your blog link in the comments below.

EuroSTAR In Pictures

View image gallery