Skip to main content

How did you find that bug? Are we sitting comfortably, then I'll begin.


How did you find that bug? - They asked with a sort of puzzled "he dun't thunk like uz" look on their faces. An expression that suggested they were unsure whether to commend the discovery or gather their pitchforks and organise a well overdue witch burning.

Likewise, I now knew why they needed me. The team members were genuinely hard working people trying to build something new and exciting. But they lacked one thing, someone exploring & asking questions - trying to find out new things about their application. Exploring is literally a step into the unknown, and that can be uncomfortable for those not experienced in how to do it well.

Related image
Exploring is literally a step into the unknown.
So how did I find that bug? It's easy to tell a story of how I tried that particular input value because... Paragraph 3 of v4.6 of the requirements document stated that the user shall indeed on occasion X given input Y in Chrome v62 do... Or spout some other overly verbose explanation of why that broken 'scenario' came to be valid. 

But I wouldn't be answering their question, and I wouldn't be telling the truth. The truth of how I (and other testers) do this is harder to remember. But having a better idea of how you got there is going to help you get there again.

Let's take a trivial example. A few years ago, working on a new editorial system for a financial news organisation: I discovered that entering a double quote character into the content search feature caused it to crash. Even worse it returned no results (But it didn't fail to provide the users with a nasty technical error message). This had not been noticed before, yet many tests had been written and run. They had more acceptance tests than they could run in a night.

I had not examined requirements documentation for that feature. I had not perused the Acceptance Criteria for the Search feature. I had not reviewed the unreliable test automation. What I did was speak to the team and then type some quoted text into the search form. I had thought that the search should behave like Google, whereby if you include text in quotes - it will search for an exact match to that string of characters. I was interested to see what happened.

I did not know whether the search should support this sort of exact phrase matching. But I was exploring. I knew 'searches' [in my experience] worked like this - so I decided to check if this one did. This was the first step in a series of related tests that allowed me and my colleagues to uncover many more issues with the search feature.

When a team is focused on short-term delivery goals they can lose sight of the features not listed right in front of them. You need someone to question, someone to explore someone to point out that crashing when an editor uses a quote is sub-optimal. That's what I do at Investigating Software.

Comments

Popular posts from this blog

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship” “Are you willing to bet on that?” No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten. Instead, I recommend you to ask yourself that question next time you believe you are finished.  Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach. Testing is gambling with your time to find information about the app. Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app

The gamification of Software Testing

A while back, I sat in on a planning meeting. Many planning meetings slide awkwardly into a sort of ad-hoc technical analysis discussion, and this was no exception. With a little prompting, the team started to draw up what they wanted to build on a whiteboard. The picture spoke its thousand words, and I could feel that the team now understood what needed to be done. The right questions were being asked, and initial development guesstimates were approaching common sense levels. The discussion came around to testing, skipping over how they might test the feature, the team focused immediately on how long testing would take. When probed as to how the testing would be performed? How we might find out what the team did wrong? Confused faces stared back at me. During our ensuing chat, I realised that they had been using BDD scenarios [only] as a metric of what testing needs to be done and when they are ready to ship. (Now I knew why I was hired to help) There is nothing wrong with c

DevOps and Software Testing.

Most of my recent work has been with DevOps teams. While in one sense DevOps is another evolution in software development. It also introduces some new skill requirements and responsibilities into the daily routine of a tester. These diagrams tend to confuse people, hence the video... I've created a short video to highlight some of these changes and the opportunities they bring. It's not an exhaustive view of DevOps but it gives a highlight of what you could be working with. While DevOps isn't a panacea to our software development problems, I have found that empowering teams with the ability to build and use the tools they need, can rapidly improve team morale and productivity.