Hello! I know some of you have seen me around, but I’d like to take the chance to introduce myself. I am a newer member of AST, who not very long ago had context blinders removed, revealing what software testing can be. I’ll never go back to prescriptive process! Because I love an adventure, the AST Board […]
Once you start to have a larger number of tests it can be important to be able to break them down into different categories or groupings. From a functionality perspective this allows you to only run a subset of tests. They can also help to provide clarity or insight to your test code, by replacing … [Read more…]
A few weeks ago I put out an appeal for resources for testers who are pulled into live support situations:
Looking for blogs, books, videos or other advice for testers pulled into real-time customer support, e.g. helping diagnose issues #testing
— James Thomas (@qahiccupps) October 28, 2016
One suggestion I received was The Mom Test by Rob Fitzpatrick, a book intended to help entrepreneurs or sales folk to efficiently validate ideas by engagement with an appropriate target market segment. And perhaps that doesn’t sound directly relevant to testers?
But it’s front-loaded with advice for framing information-gathering questions in a way which attempts not to bias the the answers (“This book is specifically about how to properly talk to customers and learn from them”). And that might be, right?
The conceit of the name, I’m pleased to say, is not that mums are stupid and have to be talked down to. Rather, the insight is that “Your mom will lie to you the most (just ‘cuz she loves you)” but, in fact, if you frame your questions the wrong way, pretty much anyone will lie to you and the result of your conversation will be non-data, non-committal, and non-actionable. So, if you can find ways to ask your mum questions that she finds it easy to be truthful about, the same techniques should work with others.
The content is readable, and seems reasonable, and feels like real life informed it. The advice is – hurrah! – not in the form of some arbitrary number of magic steps to enlightenment, but examples, summarised as rules of thumb. Here’s a few of the latter that I found relevant to customer support engagements, with a bit of commentary:
- Opinions are worthless … go for data instead
- You’re shooting blind until you understand their goals … or their idea of what the problem is
- Watching someone do a task will show you where the problems and inefficiencies really are, not where the customer thinks they are … again, understand the real problem, gather real data
- People want to help you. Give them an excuse to do so … offer opportunities for the customer to talk; and then listen to them
- The more you’re talking, the worse you’re doing … again, listen
Wikipedia’s article on equivalence class partitioning (ECP) is a great example of the poor thinking and teaching and writing that often passes for wisdom in the testing field. It’s narrow and misleading, serving to imply that testing is some little … Continue reading →
The Problem Early last month I was trying to update some gems on my MBP and ran into an SSL error: ERROR: While executing gem … (Gem::RemoteFetcher::FetchError) SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://api.rubygems.org/specs.4.8.gz) In typical fashion I ignored the error and tried updating RubyGems (the package manager). That failed […]
TL;DR This post is about Outlook broken business feature, carbon copy recipients. In e-mail, the abbreviation CC indicates those who are to receive a copy of a message addressed primarily to another (CC is the abbreviation of carbon copy). The list of recipients in copy is visible to all other recipients of the message. In common … Continue reading Outlook broke important business feature →
I often hear how testing is part of life. I even use that, or related references, myself. Over the past few days I’ve been able to observe life and testing intersecting in a setting that is not part of my “everyday life”. This story starts at 12:30am, Saturday morning. My Wife wakes me up complaining … Continue reading Testing and Life Collide
TL;DR After series of posts about How to kill UI regression testing, maybe you got impression that I am against UI browser automation test scripts. In this post, I will put my thoughts about the value of UI automation tests. First some context. Here are requirements for excellent UI automation tests: Language that enables you … Continue reading Value of UI automation tests →