Errors by any Other Name

You say "defect", the customer hears "defective" and the developers anticipate blame. You say "failure", the customer hears "catastrophe" and the tech support staff anticipate overtime. You say "own goal" and the customer wonders what you're talking about and you anticipate an imminent conversation with your boss.

As an industry we use many different names for bugs, including anomaly, call, crash, defect, DR, enhancement, error, events, exception, failure, fault, flaw, incident, issue, mistake, own goal, problem, side effect, suggestion, ticket, TR (collected from 1, 2, 3, 4). But surely it's as Shakespeare never said:

What's in a name? That which we call errors
By any other name would smell as sweat;

Really? What exactly are we talking about here? I like the broad Rapid Software Testing take on what a bug is:

A bug is anything about the product that threatens its value.

The BBST Bug Advocacy course has something similar:

Anything that causes an unnecessary or unreasonable reduction of the quality of a software product

finessing the idea by introducing the notion that there can be reasonable or necessary (to people who matter) compromises in a product, and that these might not be regarded as bugs.

Multiple names exist for many reasons including: because language is productive (e.g. metonymy, synonymy), because the distinctions are required or useful in some situations, because they're taken from the tool used to manage them, because of misunderstandings, because of tradition, because of culture, because of migration of words from one person or project, or company or industry to another.

And some of the names here are probably not widely used as synonyms for bugs as a whole. Some are sub-classes of bugs, for example suggestion, crash and side-effect. Some are potential attributes of many sub-classes, such as regression or blocker. Some refer to the artefacts produced in the recording or acknowledgement of an issue and which, strictly, are distinct from its existence: ticket, call, report, incident and the like.

Does it matter that we have so many names, anyway? Put simply: yes, sometimes. People are highly attuned to nuances of meaning and also, more pertinently, to forming opinions based on their interpretation of a simple word. If you don't believe me, sit in a meeting where a product or a company name is being decided. The choice of term for (let's say) an issue can be interpreted as, amongst other things:

Attributing blame for the issue, e.g. to a person, software component, process or company. Anne-Marie Charrett doesn't use "the word defect because of the impact the word has on a developers ears. No-one likes to hear their code is defective, much better is a bug or an issue." When I was a technical support manager, I made it policy never to refer to problems reported by customers as bugs (to the customer) instead we used the word issue, largely to avoid implicitly attributing blame to our product before investigation.
Providing a value judgement on the issue, e.g. the existence of a defect as agreeing that the product is defective. When I attended Rapid Software Testing, James Bach was against using the word defect because of potential legal implications.
Designating a severity or priority of the issue to e.g. you, a stakeholder, your company, your customer. For example, compare your reaction to being told there's an incoming suggestion vs a failure. Similarly, the term used might identify a point in the time that the issue will be scheduled for resolution, e.g. an enhancement vs a blocker.
Marking the issue as core or a symptom, e.g. a UI issue could be bad logic in the underlying model or bad rendering of the model. Jerry Weinberg makes a distinction between fault (an underlying issue) and failure (a manifestation of the fault) in Quality Software Management and other books. The BBST Bug Advocacy course makes error and fault synonyms and permits defect to cover both error and failure.
Identifying a point in the production process that the issue was generated. The August 2013 issue of TEST magazine differentiates flaw (a design problem) from bug (coding error) while on the Software Testing Club forum, Chad Patrick noted a definition of error as "a problem created, found, and resolved during the same phase. So a bug introduced in code and caught during a peer review or unit test, an incorrect requirement uncovered and resolved during a static analysis during analysis, etc." Fiona Charles suggests that defect has a pair term rarely used in software: "[the construction industry] also uses the term deficiency, to mean (approximately) things we should have built but didn't - in contrast with defect, meaning things we built that don't match spec."

There's some discussion on the STC about whether we need industry standardisation on these kinds of terms. I don't think we do, although it's clear that there's a set of words that have loaded meanings in some circumstances and in any dialogue that requires non-shallow understanding, those terms are going to have to be defined.

As usual, context is the guiding factor. The people you're talking to, the relationship you have with them, the kind of problem you're discussing about the kind of thing that you're building or supporting, how you're discussing it need to be understood by both sides, or you'll start to see issues, mistakes, errors, problems ...

Image: http://flic.kr/p/8vYnck

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...

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 ...

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...

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually...

Reasonable Doubt

In Your job is to deliver code you have proven to work Simon Willison writes: As software engineers we ... need to deliver code that works — and we need to include proof that it works as well. He is coming at this from the perspective of LLM-assisted coding, but most of what he says applies in general. I think this is a reasonable consise summary of his requirements for developers: Manual happy paths: get the system into an initial state, exercise the code, check that it has the desired effect on the state. Manual edge cases: no advice given, just a note that skill here is a sign of a senior engineer. Automated tests: should demonstrate the change like Manual happy paths but also fail if the change is reverted. He notes that, even though LLM tooling can write automated tests, it's humans who are accountable for the code and it's on us to "include evidence that it works as it should." Coincidentally, just the week before I read his post I told one of my...

On Herding Cats

Last night I was at the Cambridge Tester meetup for a workshop on leadership. It was a two-parter with Drew Pontikis facilitating conversation about workplace scenarios followed by an AMA with a group of experienced managers. I can't come to work this week, my cat died. Drew opened by asking us what our first thoughts would be as managers on seeing that sentence. Naturally, sadness and sympathy, followed by a week ? for a cat ? and I only got a day for my gran! Then practicalities such as maybe there's company policy that covers that , and then the acknowledgement that it's contextual: perhaps this was a long-time emotional support animal . Having established that management decisions are a mixture of emotion, logic, and contingency Drew noted that most of us don't get training in management or leadership then split us into small groups and confronted us with three situations to talk through: Setting personal development goals for others. Dropping a clange...

Great Shot, Kid

This week I've been playing with altwalker , a model-based testing tool. To get the hang of it, I attempted to build a very simple model of a workflow that is supported by the service my team owns. Hacking away at the example code, and looking frequently at the docs, I was able to get up and running in a few hours, creating: a basic model: nodes for system states, edges for operations simple assertions: mainly consistency checks on the states client: HTTP client to implement the operations against the service's API I configured this so that altwalker will perform a random walk of the model, starting state data is randomised, and the client will choose randomly whenever offered an option. Why so much randomness? Because it means that, over successive runs, more of the infinite space of possible workflow executions will be covered. Once I had that basically working I wrote a shell script that would run this loop a number of times: call altwalker ...

Bottom-up or Top-down?

The theme at LLEWT this year was Rules and constraints to ensure better quality. My experience report concerned a team I'd been on for several years which developed (bottom-up) a set of working practices that we called team agreements. The agreements survived "natural" variation such as people leaving and joining and even some structural reorganisation which preserved most of the team members but changed the team's responsibilities or merged in a few people from a disbanded team. The agreements did not, however, persist through a significant round of (top-down) redundancies where the team was merged with two others. I'm interested in thinking about the ways in which constraints on how people work affect the work and whether there are patterns that could help us to apply the right kinds of constraints at times they are likely to be useful. I'm going to use this post to dump my thoughts. My starting po...

LLEWT 2024

This weekend I was at LLEWT 2024, a peer conference on Anglesey , north Wales, discussing communication. Given the day jobs of the participants, it was no surprise that the experience reports and the conversations that followed them mostly focussed on software development contexts. Notes from my presentation are in Express, Listen, and Field . I made sketchnotes (below) for each presentation and a mindmap (above) to try to summarise the whole. Without much reflection yet, I guess I would pull these common high-level threads from the day: There are multiple reasons that communication fails ... like, duh! ... but having multiple strategies for framing a message can help ... and having multiple tactics for delivering a message can help too. Understanding what you want from an interaction is key ... so setting the context to make that more likely is wise ... which might mean meta-conversation, being transparent, or changing your approach...

Exploring It!

This week the test team at Linguamatics held our first internal conference. There was no topic, but three broad categories could be seen in the talks and workshops that were given: experience reports, tooling, and alternative perspectives on our work. (The latter included the life cycle of a bug, and psychology in testing.) My contribution was an experience report looking at how I explore both inside and outside of testing. I've tidied up some of my notes from the prep for it below. There are testing skills that I use elsewhere in my life. Or perhaps there are skills from my life that I bring to testing. Maybe I'm so far down life's road that it's hard to tell quite what started where? Maybe I'm naturally this way and becoming a tester with an interest in improvement amped things up? Maybe I've so tangled up my work, life, and hobby that deciding where one starts and another ends is problematic? The answers to those questions is, I think, almost certai...

Hiccupps

Search This Blog