Blog

go back to the blog

Blog Spy Vol 46 A Weekly Roundup From The Software Testing Blogosphere

  • 12/02/2014
  • 8671 Views
  • no comments
  • Posted by EuroSTAR
-->

Welcome to the fourth Blog Spy round up of 2014. Here are some of the latest blog posts from the Software Testing Industry that have caught our eye during the past week:

My Journey to Learn How to Code – Part 1 – Teri Charles

“I’ve set a big goal for myself this year. This is the year I’m going to learn how to code. You see, I’m always looking for ways to be a better Software Tester. That can be through reading books on testing, trainings, participating in Weekend Testing groups, running the local Boulder QA Meetup, reading other Tester’s blogs, writing about testing in my own blog, belonging to different testing organizations, going to testing conferences, mentoring, and practicing testing. But I want to take the learning of my craft to an entirely different level. I want to go deeper. And for me, that’s learning how to code. The more I know about the code I’m testing, the better Tester I will be.”

Read more here.

Careers on coffee table – Maaret Pyhäjärvi

“Coffee discussions seem be good food for thought. My company / colleagues have a principle of not talking about work, so we talk about all sorts of things – sometimes related to work. Today the topic turned out to be career – or sense of missing one completely.”

Read more here.

Fake Agile – Test Consultant – Pradeep Soundararajan

“I call myself a Fake Agile – Test Consultant. All consulting I have done in the space of Agile never exposed to me what some people over the internet seem to be talking about.”

Read more here.

To Project or not to Project – Markus Gärtner

“Over the years, I became more and more suspicious about the concept of a project. I have worked in several companies, at times working with products, at times working with projects. I have seen more waterfall projects.”

Read more here.

Testing: valuable or bullshit? – James Christie

“I’ve recently been thinking about automation, not specifically about test automation, rather about the wider issue of machines replacing humans and how that might affect testers. It started when I discussed this chart with a friend, who is a church pastor. He had spotted that there was only a probability of 0.08% that computerisation would result in job losses for the clergy in the next two decades.”

Read more here.

Cost of Delay Due to Multitasking, Part 2 – Johanna Rothman

“In Cost of Delay: Not Shipping on Time, Part 1, I introduced you to the notion of cost of delay. I said you could reduce the cost of delay by managing your projects: have shorter projects, using release criteria, or selecting a lifecycle that manages the risk.”

Read more here.

We Have to Automate – Michael Bolton

“A recent discussion on LinkedIn, entitled “Why Is Automated Software Testing A Better Choice?”, prompted some discussion. (As usual, the question “better than what?” was begged.) Then came this comment from my friend Jon Hagar: “There are … environments where the team must automate, e.g. a fast embedded control system where computation cycle is 10ms.””

Read more here.

So you think you can test …. – Huib Schoots

“Recently I saw this tweet: “a lot of testers don’t consider alternatives because they don’t know them”. It was a reaction in a discussion about a Dutch article with the title “The days of the ‘Dutch school of testing’ are over”. Jan Jaap claims that Dutch testers suffer from “Law of the handicap of a head start”. Really? I don’t think it is the handicap of a head start. Did we (Dutch testers) ever had a head start? I think it is something that is called “The Dunning-Kruger effect”.”

Read more here.

User stories should be about behaviour changes – Gojko Adzic

This is an excerpt from Gojko’s upcoming book 50 Quick Ideas to Improve your User Stories.

“Bill Wake’s INVEST set of user story characteristics has two conflicting forces. Independent and Valuable are often difficult to reconcile with Small. Value of software is a vague and esoteric concept in the domain of business users, but task size is under the control of a delivery team, so many teams end up choosing size over value. The result are “technical stories”, things that don’t really produce any outcome and a disconnect between what the team is pushing out and what the business sponsors really care about.”

Read more here.

Blog post by

go back to the blog

eurostar

Leave your blog link in the comments below.

EuroSTAR In Pictures

View image gallery