Boundary
value analysis is a software
testing technique in which tests
are designed to include representatives of boundary values. The idea comes from
the Boundary (topology).
Given that we have a set of test vectors to test the system, a topology can be
defined on that set. Those inputs which belong to the same equivalence class as defined by the equivalence partitioning theory would constitute the basis (topology).Given that the basis
sets are neighbors as defined in neighborhood
(mathematics) , there would exist
boundary between them. The test vectors on either side of the boundary are
called boundary values. In practice this would require that the test vectors
can be ordered, and that the individual parameters follows some kind of order (
either partial order or total
order ).
The boundary between two
partitions is the place where the behavior of the application changes and is
not a real number itself. The boundary value is the minimum (or maximum) value
that is at the boundary. The number 0 is the maximum number in the first
partition, the number 1 is the minimum value in the second partition, both are
boundary values. Test cases should be created to generate inputs or outputs
that will fall on and to either side of each boundary, which results in two
cases per boundary. The test cases on each side of a boundary should be in the
smallest increment possible for the component under test, for an integer this
is 1, but the input was a decimal with 2 places then it would be .01. In the
example above there are boundary values at 0,1 and 12,13 and each should be
tested.
Boundary value analysis does not require invalid partitions.
Take an example where a heater is turned on if the temperature is 10 degrees or
colder. There are two partitions (temperature<=10, temperature>10) and
two boundary values to be tested (temperature=10, temperature=11).
Where a boundary value falls within the invalid partition
the test case is designed to ensure the software component handles the value in
a controlled manner. Boundary value analysis can be used throughout the testing
cycle and is equally applicable at all testing phases.
Software Quality Assurance
Software Quality Assurance
Software Testing FAQs
QA Software
Regards,
Er Ratnesh Porwal
Software Engineer
www.AeroSoftCorp.com
www.AeroSoft.in
www.AeroSoft.co.in
www.AeroSoftseo.com
On Line Assistence :
Gtalk : ratnesh.aerosoft@gmail.com
Y! Messenger : ratnesh.AeroSoft@yahoo.com
Rediff Bol ratnesh.AeroSoft@rediffmail. com
Er Ratnesh Porwal
Software Engineer
www.AeroSoftCorp.com
www.AeroSoft.in
www.AeroSoft.co.in
www.AeroSoftseo.com
On Line Assistence :
Gtalk : ratnesh.aerosoft@gmail.com
Y! Messenger : ratnesh.AeroSoft@yahoo.com
Rediff Bol ratnesh.AeroSoft@rediffmail.
No comments:
Post a Comment