Bloggo back to the blog
Blog Spy Vol 21: A Weekly Round-up From The Software Testing Blogosphere-->
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.
Women Who Test: A Gathering of Geek Girls – Smita Mishra
Smita Mishra does a guest post on Lorinda Brandon’s blog about the gathering of a selection of women in tech who were chosen to represent the “Testing” part of the technology world, to tell their stories and figure out how to get more young women into the technology world. Read more here.
Experience Report: Pairing with a Programmer – Erik Brickarp
“It was one of those typical “do or die” scenarios: A feature was implemented that was critical for the project but it was delivered late due to slightly optimistic estimates. To make matters worse it touched on rather fundamental parts of the product making it somewhat complicated to roll back. The job was to quickly test, fix bugs and, in corporation with our product owner, decide if the feature was ready to be released. The feature in this case was rather technical with a simple interface that, depending on configuration, triggered tons of background activity including communication between different servers.” Read more here.
Mispelled Words? – Michael Bolton
“A while ago I was working with a tester at a client site, and I observed a problem: one word in a status message dialog box was misspelled. Due to a frozen severity classification system and (worse) to the kind of thinking that accompanies it, the tester initially classified this as a low-severity bug. I believed, as I still do, there were good reasons to classify it as higher, even though it might be easy to fall into thinking of spelling errors as trivial.” Read more here.
Tacit and Explicit Knowledge and Exploratory Testing – John Stevenson
“Having finally read the excellent book Tacit and Explicit Knowledge by Harry Collins which I personally found to make a significant impact on my thinking of how we learn and record information (knowledge). The book is not an easy book to read and it took me a few times of re-reading some sections to work out what the author may have meant.” Read John’s thoughts on the book here.
Technical skills are a must for modern testers – Martijn de Vrieze
“When looking at the current developments within IT the focus of testing is getting to be more and more on the business-logic and functionality rather than user-flows. More and more systems are delivered as API-based systems or service oriented architectures where the UI, or front-end, is only to a lesser extend important. UI’s can be put live into the world a lot easier, with béta testing, testing in production etc. Whereas the business-logic of an application, as well as the API’s are increasingly becoming more and more important, since that is where the actual value of most applications is.” Read more here.
The Value of Testing & Test Teams – Rajesh Mathur
“When I first saw this theme, I thought it is going to be a cake walk writing about the value of testing. My fellow testers, teams and I provide immeasurable value to the projects we work on as well as to the larger organization. Just when I thought this was easy to prove, another thought came to my mind – I recalled of all the arguments, discussions, ambiguities and complexities we face every day. This thought also brought about the questions and comments we face about so called best practices, matrices, and the value we were providing.” Read more here.
A Long Time “Face Value” – Michael Larsen
“As testers, we like to believe that we don’t take things at their “face value”. We pride ourselves in the fact that we investigate things, we are skeptics, we research and we check things out, and we are sure that the things that we do have passed this so called test. Yet, very often, we carry around things that we’ve always thought were true, or have thought something was true for so long we never thought to investigate. This is a story of one of those instances, and the “face value” issue has, effectively, spanned my entire professional life.” Read more here.
A good assessment is about improving – Jeroen Mengerink
“Improvements require an assessment, either formal or informal. A good assessment tells you what you are doing right and which areas are open for improvement. If you do not plan to act on the improvement areas, then why do you do an assessment? So the target for an assessment is twofold. First you need to know where you are, next you need to know where you want to go. The road from where you are to where you want to be can only be defined by improvement actions. So how do you do a good assessment of any situation?” Read more here.
The Many Perspectives of Automated Testing – Dan Ashby
“A few months ago, I read a great blog post by Iain McCowatt (@imccowatt) about “Models of Automation”.The blog detailed a problem that Iain had witnessed between two of the teams that he was working with regarding automated testing – There was a lack of communication between the two teams and this was down to the different models the teams were using to write their automation scripts…
The framework team’s automated scripts were aimed at automating “whole tests”, whereas the test team’s automation was aimed at “tasks”.
I can relate to both models that the teams were using as when I first started learning and attempting to build automated scripts, I had the mentality of the test team in Iain’s examples, while I was learning from people who were coming from the other angle…” Read more here.
Tools for Including Customers in your Software Life-cycle – John Ruberto
“Customer-Driven Quality is a framework for building software that is loved by your customers. It starts with the premise that customers define quality and every phase of the software development life-cycle should include engagement from actual customers. This post in one a series and describes some of the tools and infrastructure that most likely already exists in software development organizations, which are necessary to implement a Customer-Driven Quality program.” Read more here.