part one: the big picture
1.terms for software failures
Defect variance fault failure problem inconsistency error feature incident bug anomaly
difference:
fault,failure and defect tend to imply a condition that's really severe,maybe even dangerous.
Anomaly,incident and variance don't sound quite so negative and are often used to infer unintended operation rather than
all-out failure.
Problem,error and bug are probably the most generic terms used.
2.A formal definition of software bug
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.
3. Bugs are caused for numerous reasons,but,in this sample project analysis,the main cause can be
traced to the specification.Reasons contain specification,design,code,other.
4. The cost to fix bugs can increase dramatically over time.
5. what exactly does a software tester do?
The goal of a software tester is to find bugs, find them as early as possible , and make sure they get fixed.
6. what makes a good software tester?
Most software tester should have:
(1)They are explorers.
(2)They are troubleshooters.
(3)They are relentless.
(4)They are creative.
(5)They are (mellowed) perfectionists.
(6)They exercise good judgment.
(7)They are tactful and diplomatic.
(8)They are persuasive.