Common Software Errors – Checklist - Rahul's Testing Titbits

I have been referring to this fantastic resource for a couple of years. It’s the Common Software Errors Appendix on Testing Computer Software by Dr. Cem Kaner. Appendix : Common Software Errors (bbst.courses).

I have often referred this to my friends but this 89-page document often appears to be a long read for most people. Now, I have decided to convert this into a checklist for me or anyone who wants to leverage the power of these common software errors to assist their testing.

Disclaimer: All credits for these points go to Dr. Cem Kaner. I have just converted them to checklist pointers for quick use.

Pro Tip: The webpage will save the status of the checklist until you reset the page cache or a timeout happens (180 days). So, you can use this as a workbook too.

Functionality Errors

Missing functionality

Wrong functionality

Doesn't do what the user expects

Excessive functionality

Too Slow or Too Restrictive

Misleading Info Errors

Simple factual errors

Spelling errors

Confusing feature names

Similarly named features

Information overload

Common Display Bugs

Wrong or partial string displayed

Messages displayed for too long or not long enough

Inconsistency Bugs

Inconsistent capitalization

Inconsistent menu position

Inconsistent abbreviation. Ex: Jan, July

Menu Bugs

No back or forward

Too many paths to the same place

You can't get there from here situation

Disaster Prevention Bugs

No backup facility

No undo support

No, "Are you sure?"

No incremental save

User Tailorability Bugs

Can't turn off the noise or sound

Can't tailor to popular hardwares

Can't change device initialization or startup

Can't turn off automatic saves

Can't find out what you did last time. Ex: History.

Error Prevention Bugs

Coping with invalid data. Ex: Ignoring text in a Phone # Field

Implementation of Checksum for file read / write

Protection against using incompatible versions

Protection against malicious user or inputs. SQL Attack, Injections, etc.

Boundary Bugs

Invisible Boundaries

Hardware Boundaries

Boundaries in Time

Numeric Boundaries

Initial & Later States

Failure to set a data item to 0

Failure to clear a string or flag

Failure to reinitialize

Incorrect initialization

Failure to initialize loop-control variable

Looping Bugs

Infinite loop

Wrong starting value for the loop control variable

Accidental change of the loop control variable

Wrong criterion for ending the loop

Commands that do or don't belong inside the loop

Improper loop nesting

Switch Case Bugs

Missing default

Missing case in switch statement

Overlapping cases

Invalid or impossible cases

Missing Bugs

Failure to notice a problem

Misreading the screen

Failure to report a problem

Failure to execute a planned test

Failure to use the most "promising" test cases

Ignoring programmers' suggestions

Failure to notice a problem

Misreading the screen

Failure to report a problem

Failure to execute a planned test

Failure to use the most "promising" test cases

Ignoring programmers' suggestions

Poor Reporting Bugs

Illegible reports

Failure to make it clear how to reproduce the problem

Failure to say that you can't reproduce a problem

Failure to check your report

Failure to report timing dependencies

Failure to simplify conditions

Concentration on trivial issues

Abusive or aggressive language

Finding Wrong Bugs

Errors in testing programs

Corrupted data file

Misinterpreted specifications or documentation

Information Miss Errors

No onscreen instructions

Missing Cursor or Entry Prompt

Failure to check for the same document being opened more than once

Undocumented features

Failure to show activity during long delays. Ex: Progress Bar

States that appear impossible to exit

Help Text & Error Messages

Inappropriate complex technical jargons in error message

Too verbose message

Inappropriate emotional tone

No Hex Dump Codes or Mysterious Codes

Display Layout Bugs

Wrong Grouping of Menu Items

Misuse of color a.k.a. Over Color

Heavy reliance on color & no / minimal text

Poor aesthetics in the screen layout

Time Waster Bugs

Garden paths & no fruits

Choices that can't be taken. Ex: Save without an update? or Press Help: Sorry! Help not available.

Are you really, really sure?

Obscurely or idiosyncratically named features

No incremental saves

State Transition Bugs

Can do nothing and leave (Support for Rollback)

Can quit mid-program

Can stop mid-loading

Shouldn't timeout quickly

Misc. Nuances

Obsession with security

Can't hide menus or No support for full screen

Doesn't support standard OS features (Ex: CTRL+C,V)

Doesn't allow long names

Performance Bugs

Slow program

Poor responsiveness

No warning that operation will take long time

No progress reports

Too short time-outs

Error Detection Bugs

Highlights overflow

Highlights impossible values

Highlights error flag

Highlights hardware fault or error conditions

Calculation Bugs

Truncation and round-off error

Incorrect approximation

Overflow and Underflow

Wrong formula

Wrong order of operator

Program Stops

Dead crash

Waits for impossible condition, or combination of conditions

Wrong user or process priority

Program goes uncontrolled

If Else Related Bugs

Wrong inequalities (e.g., > instead of >=)

Testing floating point values for equality

Confusion between AND & OR

Incorrectly negating a logical expression: !(true) vs (true)

Hardware Bugs

Wrong Device

Wrong Device Address

Device Unavailable

Device Returned To Wrong Pool

Wrong Privilege Level For a Device

Noisy Channel-Overloaded Bus

Channel Goes Down - Driver Gone

Time-out Problem

File Already In Use

Unexpected End OF File

Misunderstood Status or Return Code

Device Protocol Error

Ignores Channel Throughput Limits

Assumes Device Is or Isn't Or Should Be Or Shouldn't Be Initialized

Version, ID Related Bugs

Old Bugs Mysteriously Reappear Due To Integration Issue

Failure To Update Issue In Multiple Locations Or Program Files

No Title On Heading

Wrong Version Number On The Title Screen

No Copyright Message Or A Bad One

Release Build Doesn't Work Or Contain Wrong Code Or Data

Poor Tracking or Follow Up Bugs

Failure to provide summary reports

Failure to re-report serious bugs

Failure to verify fixes

Failure to check for unresolved problems just before release

Happy Testing & Happy Bug Hunting!