Support Your Test Team

If you can keep your head when all about you customers and colleagues are losing theirs and blaming it on you then, with apologies to Kipling, you'll stand a decent chance of being comfortable in tech support.

I often think about the crossover between support and test and I've recruited people with support experience to work as testers more than once. I've also noted before that I have my test team watch all support traffic and it's common in many companies for testers to be brought in for advice and to test fixes for issues that start as support tickets. But being the owner of a hard-to-reproduce high-value support issue, without a buffer between you and the customer who is experiencing the pain, being the one responsible for working out what the issue is and identifying a workaround adds piquancy and urgency and pressure to the diagnostic task.

This kind of thing is often more constrained than the average test mission. In this scenario you know that there's an issue. You even know some of the symptoms, but you usually have a distorted lens through which to view it, a delay on your interactions with it ... If you can wait and not be tired by waiting ... restrictions on the questions you can reasonably ask and an understandably limited supply of patience on the part of the customer who frankly just wants the thing to work and who has their own deadlines, usually pressing, which are the reason they've had to open your application again for the first time in months. You also have to split your time between looking for a solution and looking for a workaround. Prioritisation and timeliness are key.

In one case I can recall, a customer was having difficulties with a file we'd supplied which, when applied to their installation, caused a fatal error. There was a known issue with files of this kind being corrupted in transfer or deployment and, using Occam's Razor, we initially explored that as the most likely cause - without success.

With the customer's approval, and the aim of getting a quick win for them, we tried some sledgehammer workarounds such as reinstallation and a change of host machine. I also suggested a somewhat horrid fix that the customer understood would work - with some compromises - but decided not to take up immediately.

The customer thought that it was probably a build issue - they had just upgraded - but I was less certain because I had set up a local shadow which was running with the same file the customer had (confirmed by md5sum) with no ill effects. Creating a local copy of the customer environment is often a sensible - if potentially expensive - tactic although ensuring that you've matched them in all significant respects is a challenge in its own right, given that you don't yet know what is significant.

Regardless of the speculation, the mission now was to get either a workaround or a fix, or both, in short order. I started with the idea that the issue was environmental and explored ways to provoke the problem. In the absence of full information about the customer setup I made assumptions about it and tried to provoke the kinds of effects that locale differences can show, such as problems with file encodings.

By working back from the symptoms I found some issues that exhibited the same behaviour and then spoke to a developer with expertise on the customer platform for pointers about how to provoke those issues directly. He was able to finesse my bug reports but we weren't able to get to the customer issue itself. If you can trust yourself when all men doubt you, But make allowance for their doubting too ...

At the same time, I looked for historical data in bug reports (remember don't just search the open ones) and previous support tickets. I spoke to other members of the support team about a locale issue with another customer at around the same time - but they were clearly unrelated and would have different solutions.

The initial customer report contained several overlapping issues from their own attempts to diagnose the problem and we maintained a dialogue about those, progressively filtering out the ones that we could resolve or at least explain and that appeared not to have a bearing on the main problem.

At this point I asked whether we could have direct access to their installation and the customer was able to provide it, which unusual is but enormously helpful when available. I was able to switch from the meta problem of trying to set up an environment to enable the issue and dive straight into investigating the cause of a problem I could now provoke at will.

I first tried some high-level stuff such as installing different JVMs and running some of our software components by hand to narrow down the area in which the problem might exist. Then I returned to the environment, repeating some of my earlier experiments to see if they gave the same responses on the customer machine. I also did a direct eyeball comparison of all configuration options that I thought might be related to the issue between the customer machine and our local shadow - and some that weren't.

Changing tack again, I inspected our source code, deoxidised my rusty Java and wrote a validator for the file based on the library our software uses. When that failed to show issues I altered my validator to be more like our software but again that showed no issues. This wasn't a disaster, just more data.

While your time is important to your company, the customer's time is important to them, their company and by extension your company. You have to be focussed on getting value for every experiment you carry out ... If you can fill the unforgiving minute with sixty seconds' worth of distance run.

To try to understand the problem space more I reverted to manual work and tried a bunch of different files - not created for this customer, that I knew would not work in this environment but which I had used previously in other installations internally - and I found that under some circumstances I could get further in the interpretation of the file before encountering an error. Exploiting this vector I crafted some more variants of the file and tried them in turn. One resolved the issue.

So now we had a workaround for the customer and a target for the dev team. With knowledge of the change to the file that caused a critical effect on the installation, one of the developers built me an instrumented version of the software with focussed debug around the change. It confirmed enough details to permit further code inspection, informed by the research I'd done, to identify a subtle software issue that required particular environmental settings, particular content in the file and certain temporal dependencies.

Exploratory testing techniques are invaluable in these sorts of cases. The kinds of heuristics and approaches that Rapid Software Testing espouses - factoring; logical vs lateral thinking; plunge in and quit; random fire; critical thinking; questioning your premises; focus/defocus; asking what if? - can keep giving you options to try. You have to be prepared to iterate, to revisit, to expand and contract your search, to investigate all available resources (people, documentation, code inspection) and assimilate them.

Stakeholder interaction is critical too. Live support can be stressful; you have to think on your feet, be professional at all times, provide rationale for the steps you are asking the customer to perform. During an extended support interaction, giving the customer some options is usually appreciated and keeping the customer informed and demonstrating effort and progress, even if only in narrowing down the possibilities, can provide reassurance. You also need to take your experience and learn from it, to feed your gut for next time round. With hindsight, I could have found this issue faster, more directly. I'll bear that in mind in future.

If you can dream - and not make dreams your master; If you can think - and not make thoughts your aim ... If you're a tester looking for a challenge, and to hone your skills, you could, with further apologies to Kipling, do worse than swinging by tech support for a spell, my son.
Image: http://flic.kr/p/7FVs91

Comments

Meet Me Halfway?

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested ...

Beginning Sketchnoting

In September 2017 I attended Ian Johnson 's visual note-taking workshop at DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

How do I Test AI?

Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components . I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete. Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

Don't Know? Find Out!

In What We Know We Don't Know , Hillel Wayne crisply summarises a handful of research findings about software development, describes how the research is carried out and reviewed and how he explores it, and contrasts those evidence-based results with the pronouncements of charismatic thought leaders. He also notes how and why this kind of research is hard in the software world. I won't pull much from the talk because I want to encourage you to watch it. Go on, it's reasonably short, it's comprehensible for me at 1.25x, and you can skip the section on Domain-Driven Design (the talk was at DDD Europe) if that's not your bag. Let me just give the same example that he opens with: research shows that most code reviews focus more on the first file presented to reviewers rather than the most important file in the eye of the developer. What we should learn: flag the starting and other critical files to receive more productive reviews. You never even thought about that possi...

My Adidas

If you've met me anywhere outside of a wedding or funeral, a snowy day, or a muddy field in the last 20 years you'll have seen me in Adidas Superstar trainers. But why? This post is for April Cools' Club . --00-- I'm the butt of many jokes in our house, but not having a good memory features prominently amongst them. See also being bald ("do you need a hat, Dad?"), wearing jeans that have elastane in them (they're very comfy but "oh look, he's got the jeggings on again!"), and finding joy in contorted puns ("no-one's laughing except you, you know that, right?") Which is why it's interesting that I have a very strong, if admittedly not complete, memory of the first time I heard Run DMC. Raising Hell , their third album, was released in the UK in May 1986 and I bought it pretty much immediately after hearing it on the evening show on Radio 1, probably presented by Janice Long, ...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report. Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia. ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...

Not a Happy Place

A few months ago I stopped having therapy because I felt I had stabilised myself enough to navigate life without it. For the time being, anyway. I'm sure the counselling helped me but I couldn't tell you how and I've chosen not to look deeply into it. For someone who is usually pretty analytical this is perhaps an interesting decision but I knew that I didn't want to be second-guessing my counsellor, Sue, or mentally cross-referencing stuff that I'd researched while we were talking. And talk was what we mostly did, with Sue suggesting hardly any specific tools for me to try. One that she did recommend was finding a happy place to visualise, somewhere that I could be out of the moment for a moment to calm disruptive thoughts. (Something like this .) Surprisingly, I found that I couldn't conjure anywhere up inside my head. That's when I realised that I've always had difficulty seeing with my mind's eye but never called it out. If I try to imagine ev...

Software Sisyphus

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "How can I possibly test 'all the stuff' every iteration?" Whoa! There's a lot to unpack there, so let me break it down a little: who is suggesting that "al...

Hiccupps

Search This Blog