Helping software testers remain relevant and employable – find out more below
One of the observations I’m seeing a lot in the Testing community is the desire and passion to experiment with ideas. This is not new, there have always been people exploring and experimenting with ideas, from test case production to test reporting. But it feels to me like it’s becoming more mainstream to experiment;
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
I’ve blogged a little recently on Cloud Testing and the future it may hold for the industry. From this post I got involved in a number of chats and discussions, mainly with Testers and Managers looking to move to the cloud. One of the many assumptions I took from these discussions was that Cloud
This morning I was in my local Tesco supermarket and noticed a classic case of inconsistency between the message and the action. I am a seriously big fan of the self service checkouts in Supermarkets. Not only have they reduced queues but they’ve made it entirely possible to dehumanise the entire experience of food shopping;
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
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.
I got asked a question the other day about metrics. “If you don’t use metrics to assess test completion, how do you know when you are half way complete?” I won’t go in to all of the details surrounding the discussion that ensued, but I thought I would share with you the
I’ve mentioned a few times via Twitter (mainly from India) about a neat little tool Julian Harty talked about at the Step_Auto conference; FightingLayoutBugs. It’s a Java code project that checks for layout bugs. It’s all Open Source code and available from “http://code.google.com/p/fighting-layout-bugs/“. So here is what FightingLayoutBugs does out of the tin: DetectInvalidImageUrls