1. ## Date.....

Hi,

Are there any boudary limit values (start and end ) for the year(s) too like (01-12 for mm), (01-31 for dd) that one can restrict while doing testing ?

Year:
YY (eg 01)
YYYY (eg 1997)
Year and month:
YYYY-MM (eg 1997-07)
Complete date:
YYYY-MM-DD (eg 1997-07-16)

where:
YY = two-digit year ( ---- ?? ---- )
YYYY = four-digit year ( ---- ???? ---- )
MM = two-digit month (01=January, 12 = December)
DD = two-digit day of month (01 through 31)

Thanks for the Info,
Chandra

------------------
Chandra

2. ## Re: Date.....

Are system uses 18/11/1752 as a null date so the first valid date is 19/11/1752. The are several good websites about dates although I can't remember the URL's I will post them later if I can find them. There is an ISO standard for dates and date handling.

One of the reasons we picked this date is it the minimium date of one of the third party products. These appear to support different date ranges.

------------------

3. ## Re: Date.....

I'd think that would depend on the software and how it's programmed. One of mine won't allow dates outside of 1/1/1900 - 12/31/2099.

I hate to say this, but you'll have to check the specs.

------------------
Jordan Gottlieb
Qualitech Solutions, Inc.
jgottlieb@qualitechsolutions.com

4. ## Re: Date.....

Ahh, good question. I am trying to remember the Y2K testing frenzy...

Well, I can't remember. But, I think most software today has four digit years. I would think it would vary from application to application depending on how the data type is stored. If it's just a integer, then I suppose 9999 would be the upper limit (unless it's not, if that makes any sense). Or it might be sometime around 2037 (unless it's not). Time and Dates can be stored many different ways, the best way to find out is to ask. (As Jorden said, there should be a spec.) I have seen low limits as high as 1980.

How about punching numbers to find the boundaries yourself? Then determine if they are correct for whatever it is that the date is being used for.

Two digit years should have a rollover date. I've had some apps do it 14, some at 32. If there is calculation to be performed, say to determine age from birth date, it would be best to force a four digit year.

------------------
Michael S.

[This message has been edited by msnide (edited 08-08-2001).]

5. ## Re: Date.....

While we are here, I've had software that would convert dates like this:

01/40/02 = 02/09/02

------------------
Michael S.

6. ## Re: Date.....

Arrggh! Y2K flashbacks!

Couple of things to consider:
<UL><LI>On 64-bit UNIX systems, the integer which stores the system time will overflow some time in 2037 (I dont't recall the exact date/time).
<LI>An application may handle its dates fine, until the OS's current date/time reaches some critical point (such as the UNIX thing above, or some other arbitrary roll-over point). Therefore, it may be necessary to change the system time to a particular date, not just try entering various dates into the application's interfaces.
<LI>Check the Leap Year conditions:
IF (year % 4 == 0) AND ((year % 100 != 0) OR (YR % 400 == 0)) THEN year = leapYear[/list]

------------------
Charles Reace

Software Testing (n): 1. The art of trying to increase your confidence in a piece of software by finding everything that is wrong with it.

[This message has been edited by creace (edited 08-08-2001).]

7. ## Re: Date.....

November 18, 1752? That's an odd date. Out of curiousity is it an important date for some reason?

------------------
Jordan Gottlieb
Qualitech Solutions, Inc.
jgottlieb@qualitechsolutions.com

8. ## Re: Date.....

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by jgottlieb:
November 18, 1752? That's an odd date. Out of curiousity is it an important date for some reason?

<HR></BLOCKQUOTE>

That was the day Sir Edmund "It works on my Machine" Byte published his definitive paper on modern programming techniques. It was a little noticed event, as computers wouldn't be invented for over hundred and fourty years.

------------------

9. ## Re: Date.....

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by rob_itd:
Are system uses 18/11/1752 as a null date so the first valid date is 19/11/1752.

One of the reasons we picked this date is it the minimium date of one of the third party products. These appear to support different date ranges.

<HR></BLOCKQUOTE>
OK....I can not for the life of me envision a product that is nearly 250 years old....And does this third party by chance still "support" this product???

------------------

10. ## Re: Date.....

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by DanB:
Originally posted by rob_itd:
Are system uses 18/11/1752 as a null date so the first valid date is 19/11/1752.

One of the reasons we picked this date is it the minimium date of one of the third party products. These appear to support different date ranges.

<HR></BLOCKQUOTE>
OK....I can not for the life of me envision a product that is nearly 250 years old....And does this third party by chance still "support" this product???
What if I said the "product" was my house?
I hope that my Insurance company still supports it!

Clearly, all software must decide the range of values to be supported in their date fields. The range they choose depends on how the software will be used.

-A carbon-dating program may have one range
-An insurance program will have another
-A web site sign-up page will have another

------------------
- Joe (strazzerj@aol.com)

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.