A while ago I remember Phil Kirkham mentioning that he’d found a bug that “fell” outside of the Test Cases he’d been given and someone was arguing that it wasn’t a bug. I found it incredibly interesting that someone would dismiss a serious bug because it was not found as part of a test case.
I often get asked by people new to Software Testing what the best approach to learning more about Testing is. Is it certification, books, blogs or other courses? These are the usual categories that get listed. I very rarely hear people ask whether “practice” is a good approach to learning. I think this stems
Whilst on the train a few months back I spent some time observing how people were using technology. Some were using the tech as I assume it was intended, some were “street hacking” the products, whilst others had adopted unique ways of utilising technology (and other devices) to fit the context they found themselves in.
At EuroSTAR last week it was sad to see a “them versus us” culture still thriving in the software development community. I thought things were changing, especially with the on-set of Agile heading mainstream but it seems not. I got embroiled in a conversation which stole an hour of my life. An hour in
I believe that one of the biggest mistakes a Hiring Manager (Test Manager etc) can do for a team is to hire in people with the same set of views and opinions. I’m not talking about “Yes” people who don’t have the confidence or inclination to disagree. I’m talking about people who are pretty much
One of the interesting changes I see in the Testing industry is that many new companies, with newly formed Development teams (i.e. Programmers, Testers, Product etc), are automatically looking to the cloud for Testing solutions and tools. It’s a natural process as many of these companies often power their entire infrastructure through Cloud tech. It’s
During a conversation with a group of testers at an event I soon found myself outnumbered in my views around “enhancements” to the product. I was the only one who saw a Tester’s role as more than just verification. I was a little amazed at how this group of Tester’s (or shall we call them
Bear with me as a clear a few posts out of draft. This is my last one for a few weeks. Promise. This one came about as response to James Bach’s excellent Open Lecture presentation. I took away a number of lessons from that lecture. (including the title – Professional Skeptics, Dispeller of Illusions
One of my favourite blogs (http://www.experientia.com/blog/) carried an essay/article on humans and machines by Marina Gorbis. It’s a breezy article but makes some awesome points and each point Marina made rang true for what we are seeing in the Testing world. Marina makes a point that machines are replacing the mechanistic jobs traditionally done by
The other day someone sent me an email asking me how to stand out from the masses in the Testing world. I responded by suggesting they engage in the community, join groups that interest them, read about any other subject that interests them but isn’t directly considered a Testing information source and to start learning
I’ve always tried to appreciate ‘context’ when I talk about Testing and also when I Test because ‘context’ is a very real thing. I’m an avid campaigner against Best Practices in Testing and I take every opportunity possible to question blatant “context unaware” statements about testing, especially so when they are communicated as “law”.
There comes a time when we all use numbers to represent some fact or information. These numbers *can* be highly effective at communicating your information. Image courtesy of : http://www.flickr.com/photos/fragmented/ These numbers could become the defacto representation of some outcome, fact or finding. These numbers could become the metric you make a decision by.
In almost all places of work, there exists a level of wasted time and effort when communicating a message multiple times. In almost all places of work, there exists a level of wasted time and effort when communicating a message multiple times. These “duplicate conversations” are wasteful and ultimately take people away from the
I’m reading an excellent book at the moment called “Game Storming” by Dave Gray, Sunni Brown and James Macanufo. It’s one of those books that’s given me a “lesson” or insight in every chapter. In essence Game Storming is about generating new ideas and novel solutions. It’s a way of getting from Starting
It seems the more that something becomes popular the more that people start to hate it, often without even trying it. Look at what’s happening with Agile in the testing community. A lot of negativity from people who’ve never tried it. The lashing out is usually based on false ideas of what it actually means