Edit post Follow this blog Administration + Create my blog

Types of errors with examples

May 3 2019 , Written by Harry Published on #TESTER

Types of errors with examples


User Interface Errors:

      Missing/Wrong Functions Doesn’t do what the user expects, Missing information, Misleading, Confusing information, Wrong content in Help text, Inappropriate error messages.

      Performance issues - Poor responsiveness, Can't redirect output, Inappropriate use of keyboard

Error Handling:

     Inadequate - protection against corrupted data, tests of user input, version control;

     Ignores – overflow, data comparison, Error recovery – aborting errors, recovery from hardware problems.

Boundary related errors:

    Boundaries in loop, space, time, memory, mishandling of cases outside the boundary.

Calculation errors:

    Bad Logic, Bad Arithmetic, Outdated constants, Calculation errors, incorrect conversion from one data representation to another, Wrong formula, incorrect approximation.

Initial and Later states:

    Failure to - set data item to zero, to initialize a loop control variable, or re-initialize a pointer, to clear a string or flag, Incorrect initialization.

Control flow errors:

    Wrong returning state assumed, Exception handling based exits, Stack underflow/overflow, Failure to block or unblock interrupts, Comparison sometimes yields the wrong result, Missing/wrong default, and Data Type errors.

Errors in Handling or Interpreting Data:

    Un-terminated null strings, overwriting a file after an error exit or user abort.

Race Conditions:

    Assumption that one event or task finished before another begins, Resource races, Tasks starts before its prerequisites are met, Messages cross or don't arrive in the order sent.

Load Conditions:

     Required resources are not available, No available large memory area, Low priority tasks not put off, doesn’t erase old files from mass storage and doesn’t return unused memory.


    Wrong Device, Device unavailable, Underutilizing device intelligence, Misunderstood status or return code, Wrong operation or instruction codes.

Source, Version and ID Control:

     No Title or version ID, Failure to update multiple copies of data or program files.

Testing Errors:

    Failure to notice/report a problem, Failure to use the most promising test case, Corrupted data files, Misinterpreted specifications or documentation, Failure to make it clear how to reproduce the problem, Failure to check for unresolved problems just before release, Failure to verify fixes, Failure to provide a summary report.

Share this post
To be informed of the latest articles, subscribe:
Comment on this post