# Thread: RE: Boundary Value conditions for MM/DD/YYYY

1. ## RE: Boundary Value conditions for MM/DD/YYYY

Hi All,

Could anyone list me all the boundary value conditions for date format ie: MM/DD/YYYY.
Note: All the condtions Pls.
eg: for Month: 0,1,2,11,12,13,7

Regards,
J

2. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

what do you mean by the boundary value condition here ??. What do u want to check ???

3. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

I mean using boundary value condtion techinique give me all the possible conditions. I need to check all the date condition, so that it satisfies all the posible conditions.

eg: As above example, irrespective of the other fields month will always be 1-12. so BVA for this is 0,1,2,11,12,13 and 7. So similary i need it for date and year as above format.

4. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

date: 30,31,32 (for months having 31 days)
29,30,31 (for months having 30 days)
For Feb: 27,28,29 (for normal year) &amp; 28,29,30 for leap year

month: 0,1,2, 11,12,13 (as u mentioned)

For year u can take 1999,2000,2001.

5. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

Hi sanket / All,

Thanks for the reply. I agree with you in terms of month and date.

For year yyyy, apart from 0000,0001,0002,9998,9999 are there any other options.

Note: As per boundary value technique is there any option need to cover for yyyy. pls answer.

7. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

[ QUOTE ]
For year yyyy, apart from 0000,0001,0002,9998,9999 are there any other options.

Note: As per boundary value technique is there any option need to cover for yyyy. pls answer.

[/ QUOTE ]

Taking 0000, 9999 &amp; all such stuff for boundary values doesn't make sense as no one is going to enter years like 9998, 9999 in 2009 (even taking into account future) or years like 0000, 0001, 0002 at present (i.e. in 2009). You need to see the valid year range from requirements. If it is not mentioned in requirement better ask your client.

I guess that max range has to be something between 1900 - 3000 or 3050

So just take the below boundary values:

1899, 1900, 1901
1999, 2000, 2001 (just to make sure as century changes)
2999, 3000, 3001 (depending on your range).

Hope this helps.

8. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

[ QUOTE ]
no one is going to enter years like 9998, 9999 in 2009 (even taking into account future) or years like 0000, 0001, 0002 at present (i.e. in 2009).

[/ QUOTE ]

I'm going to.

And I'm going to enter years like the following if the UI allows me to:
-1
1
02
003
999999
zerble
//
\\
199A
20 01
etc, etc.

Why? Because that's the way I roll.

9. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

Hi Joe

[ QUOTE ]
no one is going to enter years like 9998, 9999 in 2009 (even taking into account future) or years like 0000, 0001, 0002 at present (i.e. in 2009).

[/ QUOTE ]

By this I meant
For most business purposes these years wont be required to enter in 2009 in most of the cases. As no-one is going to enter application, I had assumed that UI won't allow to do so. So I also mentioned to confirm the year range from client.

10. ## Re: RE: Boundary Value conditions for MM/DD/YYYY

[ QUOTE ]
As no-one is going to enter application, I had assumed that UI won't allow to do so.

[/ QUOTE ]

That's an interesting assumption.

#### 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.