FUNDAMENTALS OF TESTING
Test6condition6-6ans--
An6item6or6event6of6a6component6or6system6that6could6be6verified6by6one6or6more6test6ca
ses
Test6case6-6ans--
A6set6of6input6values,6execution6preconditions,6expected6results,6and6execution6postcon
ditions,6such6as6to6exercise6a6part6of6the6code
Test6procedure6specification6-6ans--A6sequence6of6actions6for6the6execution6of6a6test
Reasons6to6know6test6coverage6-6ans--
1)6Provide6a6quantitative6measure6of6the6quality6of6testing6that6has6been6done
2)6Provides6a6way6of6estimating6how6much6more6testing6is6needed
Three6categories6of6test6case6design6techniques6-6ans--1)6Black6box6techniques
2)6White6box6techniques
3)6Experience6based6techniques
Specification6based6techniques6-6ans--Black6box6testing6-
6test6cases6derived6directly6from6a6specification6or6a6model6of6a6system6or6proposed6syst
em6(documentation)
56types6of6specification6based6techniques6-6ans--1)6Equivalence6partitioning
2)6Boundary6value6analysis
3)6Decision6table6testing
4)6State6transition6testing
5)6Use6case6testing
Equivalence6partitioning6-6ans--
Reduces6the6number6of6tests6needed6by6considering6partitions6are6the6only6test6cases6n
eeded
Boundary6value6analysis6-6ans--
Looks6for6tests6that6focus6on6the6possible6boundaries6of6inputs,6noting6that6most6errors6o
ccur6there