SW Testing concepts Search this site

Home Home > Test Design Techniques >

Bug
Black box test techiniques
FAQ
Reviews
Specification Based /Black Box test techniques
Software Development Life
Cycle
1.Equivalence Partitioning:
Test case Inputs to the software or system are divided into groups that are expected
to exhibit similar behavior, so they are likely to be processed in the same
Test Design Techniques
way.
Black box test this can be done for both valid(values accepted) and invalid(values
techiniques rejected) data.
White box test this is done for outputs, internal values, time related values(before and
techniques after an event) and for interface parameters()
Test Management
Test Plan
Test types Equivalence partitioning (also called Equivalence Class
What is Software Testing Partitioning or ECP [1] ) is a software testing technique that divides the
input data of a software unit into partitions of data from which test cases can
Sitemap
be derived. In principle, test cases are designed to cover each partition at least
once. This technique tries to define test cases that uncover classes of errors,
thereby reducing the total number of test cases that must be developed.

In rare cases equivalence partitioning is also applied to outputs of a software

component, typically it is applied to the inputs of a tested component. The
equivalence partitions are usually derived from the requirements specification
for input attributes that influence the processing of the test object. An input
has certain ranges which are valid and other ranges which are invalid. Invalid
data here does not mean that the data is incorrect, it means that this data lies
outside of specific partition. This may be best explained by the example of a
function which takes a parameter "month". The valid range for the month is 1
to 12, representing January to December. This valid range is called a partition.
In this example there are two further partitions of invalid ranges. The first
invalid partition would be <= 0 and the second invalid partition would be >=
13.

2. Boundary Value Analysis

Test cases designed to check for the boundary values.

3.Decision Table Testing : is a good way to deal with combination of inputs

which lead to different outputs

4.State Transition Testing : Depending on certain condition or previous

history, a system may exhibit a different behavior. It is
much used in embedded systems.

5.Use Case Testing : Tests derived from use cases are called use case
testing.
 Comments

You do not have permission to add comments.

Sign in | Recent Site Activity | Report Abuse | Print Page | Powered By Google Sites