How to Reduce Duplicate Bug Reporting by 75%

Reducing the pester of duplications in bug reporting.

Both software Developers and Testers need to be able to clearly identify any ‘Bug’, via the ‘Title’ used for the ‘Bug Report’.

Efficiency and Flexible Random Naming

By design, development tools like; SQL, PHP, FileMaker give development teams the freedom to randomly name; tables, fields, scripts, and display layouts. Likewise, testing teams have the same freedom creating titles for ‘Bug Reports’.

But, freedom comes at a price. In this case, the freedom to randomly name elements can result in less efficiency. However, we can increase efficiency and organization through well structured, ‘Unique Naming’. Let’s examine common tasks.

Software Testers:

  1. FIND: a ‘Bug’;
  2. SEARCH: previously reported bugs, to verify that their ‘Bug’ is ‘NEW’;
  3. REPORT: a ‘New Bug’, using a ‘Title’ that is unique.

Software Developers:

  1. REVIEW: Reported ‘Bugs’;
  2. SEARCH: Reported bugs to ‘Find’ specific ‘Bug Reports’

Our goal is to retrieve ‘High-Quality Search Results’, directly resulting in greater efficiency.

Poor Quality ‘Bug Titles’ and Duplicates

‘High-Quality Search Results’ are an essential part of ‘Bug Reporting’. ‘Poorly Conceived’ or ‘Duplicate’ bug reports result in less efficiency, translate to lost hours for Developers and Testers, and ultimately produce a lower ROI for the project investors.

Four distinct elements govern ‘Bug Title’ creation:

  1. Naming Formula
  2. Reporting Language
  3. Combination ‘Bug’ Titles
  4. Vocabulary

The first two elements are often well considered and are efficiently managed for most projects. Items No. 3 and 4 are where things can be significantly improved for many projects. So let’s go by the numbers, just to get things into proper focus:

No. 1: Naming Formula:

Resolved simply with a stated policy. For example, many testing companies require their Testers to report using a ‘Formula’ like:

501 – iOS 9 – Menu Top – Function – Home button does not work.

502 – iOS 9 – Function – Menu Bottom – Contact button does not work.

503 – Function – Menu Bottom – Contact button does not work. – iOS 9

These examples quickly tell us important things about the bug. They are also search efficient, for example, a search for; Menu’ and ‘Button’ would list all of the above when a Tester is reporting a ‘Bug’; or a Developer is searching for all the broken ‘Menu Button’ bugs.

No. 2: Reporting Language:

Again, resolved with a stated policy. That said, for many projects the reporting language of choice is ‘English’.

No. 3: Combination ‘Bug’ Titles

Often, a ‘Bug’ may require a combination title, as when the issue involves more than a simple button or tool, for example:

504 – Function – Hotel Booking Page – Calendar / Date Picker fails to hide after entry. – iOS 9

In this case, the problem is with the ‘Calendar’ but more specifically with the ‘Date Picker’ function of the ‘Calendar’.

This problem could be reported as:

  1. a) Calendar fails to hide after entry; or
  2. b) Date Picker fails to hide after entry.

Both would seem to be right, but only the combination title (i.e. Bug Title #504 above) should be used to ensure it is found for either search; ‘Calendar’ or ‘Date Picker’.

The solution, a ‘Managed Naming Formula’.

No. 4: Vocabulary

It is common to have Testers from multiple countries, with many writing in English as a second language (i.e. ESL), resulting in an extreme diversity of vocabulary used. This diversity results in completely different approaches to naming ‘Bug Titles’, quickly increasing the potential for poor quality ‘Titles’.

Again, the solution is a ‘Managed Naming Formula’.

 

The “Oh Happy Day” Solution “A Lexicon”

While we can continue to assume the norm, that Testers have a diversity of vocabulary and style of expression, we can create a special ‘Managed Vocabulary’ that is used for a target software project.

This is what is known as a “Lexicon”, and it is our ‘Happy Day Solution’.

At the onset of a new development project, a ‘Lexicon’ becomes the ‘Official’ vocabulary used by the project for naming. Now, the ‘Lexicon’ provides the guide for well structured, ‘Unique Titles’ for naming tables, fields, scripts, layouts and bug reports. Applying this strategy will compound efficiency in a positive way.

Creating a Lexicon

Now that we have a solution that will increase efficiency in software development, to create a ‘Lexicon’ for your project, I recommend using a ‘Project Wiki’ format for your ‘Lexicon’. This way, missing items can be added by any authorized party to the project at any time.

Conclusion

As with most solutions in the software development world, planning and management are the keys to a highly efficient development process. My proposed solution simply puts the project manager in control.

Best wishes with your software project or testing!

 

LogiGear Corporation
LogiGear Corporation provides global solutions for software testing, and offers public and corporate software testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

LogiGear Magazine March Testing Essentials Issue 2017
Check out the top 12 Automation tools with pros and cons–like Cross-Operating Systems, Cross-Automation Platforms, Programming Language Support, and more – for desktop Automation Testing. Although the demand for desktop app testing is not growing as fast as mobile and web app testing, it’s still a crucial day-to-day duty for many testers, especially those who ...
VISTACON 2010 – Keynote: The future of testing THE FUTURE OF TESTING BJ Rollison – Test Architect at Microsoft VISTACON 2010 – Keynote   BJ Rollison, Software Test Architect for Microsoft. Mr. Rollison started working for Microsoft in 1994, becoming one of the leading experts of test architecture and execution at Microsoft. He also teaches ...
When it is out of the question to delay delivery, the solution is a prioritization strategy in order to do the best possible job within the time constraints. The scenario is as follows: You are the test manager. You made a plan and a budget for testing. Your plans were, as far as you know, ...
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Quality cost is the sum of all costs a company invests into the release of a quality product. When developing a software product, there are 4 types of quality costs: prevention costs, appraisal costs, internal failure ...
The Testing Domain Workbook is the most extensive and exhaustive work you will ever find on a specific testing technique (or related techniques if you include equivalence class analysis and boundary testing as the book does). What I like best is the combination of academic background and roots combined with practical experience and industrial practice. All the concepts are ...
Introduction This 2 article series describes activities that are central to successfully integrating application performance testing into an Agile process. The activities described here specifically target performance specialists who are new to the practice of fully integrating performance testing into an Agile or other iteratively-based process, though many of the concepts and considerations can be ...
People who follow me on twitter or via my blog might be aware that I have a wide range of interests in areas outside my normal testing job. I like to research and learn different things, especially psychology and see if it may benefit and improve my skills and approaches during my normal testing job. ...
March Issue 2019: Leading the Charge with Better Test Methods
The V-Model for Software Development specifies 4 kinds of testing: Unit Testing Integration Testing System Testing Acceptance Testing You can find more information here (Wikipedia): http://en.wikipedia.org/wiki/V-Model_%28software_development%29#Validation_Phases What I’m finding is that of those only the Unit Testing is clear to me. The other kinds maybe good phases in a project, but for test design it ...
Introduction Software Testing 3.0 is a strategic end-to-end framework for change based upon a strategy to drive testing activities, tool selection, and people development that finally delivers on the promise of Software Testing. For more details on the evolution of Software Testing and Software Testing 3.0 see: The Early Evolution of Software Testing Software Testing ...
I’ve been intending to write a book review of How We Test Software At Microsoft, by Alan Page, Ken Johnston, and Bj Rollison, but for whatever reason I just never found the time, until now. In general, I like this book a lot. It’s a nice blend of the tactical and the strategic, of the ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe