Identifying equivalence classes











Sponsored Links:

1)If the entry specifies a range of valid values, define a valid EC (within the range) & six valid EC (six off each finish of the range).
2)If the entry specifies the number (N) of valid values, define a valid EC EC & six sick (none, & over N).
3)If the entry specifies a set of valid values, define a valid EC (within the set) as well as a valid EC (not the set).
4)If there is reason to believe that the program handles each valid entry differently then define an EC valid for valid input.
5)If the entry specifies a "must be" the situation, define a valid EC & an EC valid.
6)If there is reason to believe that the elements of an EC not handled in an identical manner by the program, subdivided in to small EC .

Boundary-value analysis:1)Rather than selecting any element of an EC as representative, the elements are selected so that the edge of the EC, is being tested. These are always a nice place to look for defects.
2)In lieu of focusing exclusively on the conditions of entry, exit conditions are also explored by the definition of exit from the EC. What could be the start? What are the types of production? What I must generate as an input to force a useful set of classes that represent the products to be produced?

Error guessing:Its ad hoc approach based on intuition & experience to identify evidence that is thought about likely to expose errors.

No comments: