Bloggo back to the blog
Blog Spy: A Weekly Round-up From The Software Testing Blogosphere-->
Tools should are a prerequisite for efficient and effective QA – Ewald Roodenrijs
“Last month I had a meeting with senior management in my company and I made the statement that “quality is user experience”, in other words “without the right amount of quality the user experience will always be low”. And I think most people in QA and Testing will agree with me on that. Even organizations agree on that. Then, but why do we still see so much failures in software around us? Why do we still create software without the needed quality.” Read more here.
Iterative Estimation – Tobias Mayer
“Estimation has been the bane of the developer’s life ever since we moved beyond the hacker era of software creation, and into “corporate software”. When people hacked, they just wrote code, completed stuff and released it. People took pride in their work, challenged one another, made things up as they went along and produced wonders, the like of which no one had ever seen before.” Read more here.
Automation Kick Off: Beginning Automation with the right foot(I) – Ignacio Esmite
“Ok, we decided to introduce automation to our project, so, how do we start? In other words, which is the strategy that we should follow to introduce functional testing automation in our project or organization? The objective of this blog post is to start a series of posts that do not describe how to introduce automation because depends on the context, but instead, the purpose is to describe how to not start with automation.” Read more here.
Book Reflection: Tacit & Explicit Knowledge – Rikard Edgren
Harry Collins’ Tacit and Explicit Knowledge is a book about scripted and exploratory testing. Explicit knowledge is what can be told and is able to transfer knowledge. Tacit knowledge is what can’t be told (yet), knowledge transferred in other ways than reading/listening. There is nothing strange or mystical about this, “experience goes along with having tacit knowledge”. Read more here.
Management Myth 16: “I Know How Long the Work Should Take” Johanna Rothman
“Long ago, when I was a young developer at an anonymous company, one of my managers was disappointed with my progress. “I know how long the work should take. If I was doing the work, it would be done by now,” he huffed at me.” Read more about Johanna’s experience here.
Outside-In development with Double Loop TDD – Emily Bache
In my last post, I started talking about London School TDD, and the two features of it that I think distinguish it from Classic TDD. The first was Outside-In development with Double Loop TDD, which I’d like to talk more about in this post. Read the post here.
Emily will also be presenting a track session on ‘Specification By Example Using GUI Tests – How Could That Work?’ and an Active Workshop on ‘Readable, Executable Requirements: Hands-On’ at the 2013 EuroSTAR Conference.
If you want to really know, ask a tester! – Peter Morgan
Who should really know what is going on with the project, and how the software works (perhaps as opposed to how the software should work)? Not unsurprisingly, Peter Morgan advocates that it should be the testers that have this knowledge, both because of what they do, and because of their role as “the eyes and ears of the project”. Read this post here.
Q&A From the webinar: Creativity to show the way in Software Testing – Nathalie van Delft
Nathalie van Delft compiles a list of answers to the questions asked in a webinar for the EuroSTAR Software Testing Community entitled “Creativity to show the way in Software Testing”. Read Nathalie’s answers here.