Test Notes

I don't make software; I make it better

| Login

68 Posts | 0 Stories | 22 Comments | 641 Trackbacks

News

Please Note
The information in this weblog is provided “AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion.

SoftwareTesting
Browse Archives at
groups.google.com

Page Loads:

Technorati Profile

Post Categories

Image Galleries

My Album

Friend's Blog's

Groups

Sites

Microsoft User Group Hyderabad

Testing Blog's

The term “bug” is not very precise

Error: mistake made by the developer; located in people’s heads.

Fault: an error in a program. An error may lead to one or more faults.

Failure: execution of faulty code may lead to one or more failures. Failures are found by comparing the actual output with the expected output.

Many people still call it a “bug”!

posted on Friday, August 20, 2004 8:24 PM

Feedback

# re: The term “bug” is not very precise 8/24/2004 9:30 PM devasish

Nice way to present. Your website is compact, but has a lot of good information explained in a very clear way.

# re: The term “bug” is not very precise 9/15/2004 2:40 AM Bugger

Bugs are named thus to bug the developer!!

# re: The term “bug” is not very precise 9/21/2004 9:09 PM Debanjan Ray

"Bug" is a undefined and unexpected behaviour of the software. The term "undefined" is the behavior which is not described as requirement in Functional or Requirement specification of a document.
The term "unexpected" is the implicit, intended and wanted requirement of the SW which is not exactly documented

# re: The term “bug” is not very precise 10/13/2004 5:13 PM Veeraiah Chowdary.M

Yes,exactly correct

bugs are error/problem,It many be programming bugs/Document bugs occured in software testing lifecycle.

Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments:
Please add 8 and 3 and type the answer here: Remember Me?