# Thread: functinal testing (boundray values)

1. ## functinal testing (boundray values)

Hi all ,

this is first time i post question here , I'm just graduate student ,i
prepare my project in software testing , and i must test a program using
functional testing , boundary values , so i need
just informations how i can design test cases ??

thanks in advance for you all

2. ## Re: functinal testing (boundray values)

Boundary values:
Figure any input value, think of the smallest possible value, design a test case for entering this value, 1 below this value and 1 above this value.
Then do the same for the biggest possible value, and maybe one more testcase for a value in the middle (between those 2 boundary values).

This makes 7 testcases...

Regards,
Juergen

3. ## Re: functinal testing (boundray values)

And that's just the beginning. Boundary testing also includes testing for the maximum number of characters and one more, and the minimum number of characters and one less, then the alpha numerics and control characters need to be tested for acceptance by the application. What happens if you put a space between some characters? The list of things to test can get pretty big. That's why you need to organize your test objectives and select a minimum number of tests to adequately validate your application. The test cases are just the steps to input data and evaluate outputs.

4. ## Re: functinal testing (boundray values)

Hi ,

thanks for you all

audry

5. ## Re: functinal testing (boundray values)

I would see boundary testing in unit testing instead of functional testing.

6. ## Re: functinal testing (boundray values)

Originally posted by ddv:
I would see boundary testing in unit testing instead of functional testing.
<font size="2" face="Verdana, Arial, Helvetica">You will also see yourself out of a job very quickly

7. ## Re: functinal testing (boundray values)

Originally posted by Rich W.:
And that's just the beginning.
<font size="2" face="Verdana, Arial, Helvetica">And there's more...

If you are dealing in integers you should always include 0,1, 127, 128, 255, 156, 32767 (2^15-1), 32768, 65535 (2^16-1), 65536, 2^31-1, 2^31, 2^32-1, 2^32, 2^63-1, 2^63, 2^64-1, 2^64. These checks or to ensure that the programmer is using the correct size and type of integer.

For floating point, your boundary testing should include not only limit-1,limit,limit+1, but also n, n/2, limit-n,limit,limit+n, limit-n/2,limit,limit+n/2, where n is the smallest allowable increment on a field. For example, if your spec said that a field was accurate to 3 places of decimal, n would be 0.001. These checks are for accuracy and rounding.

For applications with non-linear functions (scientific, engineering, statistical, financial modelling etc..) it is worth consulting with the developers to see if there are other values that can also be treated as limits.

Basically what you are looking for in boundary testing is the smallest subset of the set of all possible input values for a functional unit that provides the same degree of testing to that provided by testing all possible values. This subset obviously varies hugely between applications, and IMO, one of the key skills of a good tester is being able to correctly identify these values.

8. ## Re: functinal testing (boundray values)

@Turbografx: I don't understand your answer. Are boundaries value not supposed to be already tested during unit testing?

What the point of doing this during functional testing, which is supposed to test the right behavior of the user interface?

9. ## Re: functinal testing (boundray values)

Originally posted by ddv:
What the point of doing this during functional testing, which is supposed to test the right behavior of the user interface?
<font size="2" face="Verdana, Arial, Helvetica">My understanding of functional testing is the activity of testing a system for compliance with the functional specification. While this is typically driven via the user interface, it involves much more than user interface testing. This includes testing all stated and implied boundary conditions present in the functional spec.

My understanding of unit testing is the activity of testing a small part of the system, in isolation, against its design specification. This includes testing all stated and implied boundary conditions present in the design spec for that unit.

The implication of your original post is that if boundary checking has been carried out at unit level, it is not required at functional level. I don't believe this to be true.

10. ## Re: functinal testing (boundray values)

Originally posted by ddv:
@Turbografx: I don't understand your answer. Are boundaries value not supposed to be already tested during unit testing?

What the point of doing this during functional testing, which is supposed to test the right behavior of the user interface?
<font size="2" face="Verdana, Arial, Helvetica">Functional Testing is to test that the application/product works as defined in the requirements it is highly likely that everything tested in Unit Testing by the developers will be retested during Functional Testing - boundary testing is an integral part of this.

Page 1 of 2 12 Last

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.