Software Testing

Why software Testing?
Software testing helps to deliver quality software products that satisfy user’s requirements, needs and expectations. If done poorly,
Ø defects are found during operation,
Ø it results in high maintenance cost and user dissatisfaction
Ø It may cause mission failure
Ø Impact on operational performance and reliability

Software Bug: A Formal Definition

Calling any and all software problems bugs may sound simple enough, but doing so hasn’t really addressed the issue. To keep from running in circular definitions, there needs to be a definitive description of what a bug is.

A software bug occurs when one or more of the following five rules is true:

1) The software doesn’t do something that the product specification says it should do.
2) The software does something that the product specification says it shouldn’t do.
3) The software does something that the product specification doesn’t mention.
4) The software doesn’t do something that the product specification doesn’t mention but should.
5) The software is difficult to understand, hard to use, slow, or –in the software tester’s eyes- will be viewed by the end user as just plain not right.

What exactly does Software Tester Do? (Or Role of Tester)

From the above Examples you have seen how nasty bugs can be and you know what is the definition of a bug is, and you can think how costly they can be. So main goal of tester is

“The goal of Software Tester is to find bugs”

As a software tester you shouldn’t be content at just finding bugs, you should think about how to find them sooner in the development process, thus making them cheaper to fix.

“The goal of a Software Tester is to find bugs, and find them as early as possible”.

But, finding bugs early isn’t enough.

“The goal of a Software Tester is to find bugs, and find them as early as possible and make sure they get fixed”