See if this helps

[Kiran Kumar <kiranjk@YAHOO.COM>]

I'll tell you briefly about what we did and few problems we faced. May
be you'll get an idea.
    We Basically took each piece of Psft(SQR, PSTOOLS, People Code
etc...) We Categorized them as No-Impact(No date manipulations),
Review( Look into it once again to make sure it is Y2K compliant) and
Run and Review. For Run and review, we go into the psuedo-environment,
test it for the dates like dec31 1999 roll over to 1st Jan 2000, feb
29th etc. We never encountered any PSFT problems except but few panels,
which were customized that didnt had the Display century button turned
on. We had problems with the SQRs becoz the beginning of the century is
still 1900 but we were working under the 2000 environment.

Coming to documentation, we had the list of all we did and as soon as
we felt they are y2k ready we put them under a list and got it signed
off. For the SQRS which were Run and review, we had to test them
individually, show the test results and get them signed off.
If this doesn't help I'm sorry.
Fell free to ask me if you need anything else.
-Kiran

--- "Johnson, Joe" <JoeJo@SNELLINGCORP.COM> wrote:
> Kiran,My work is testing some customized programs
> that interface with
> PeopleSoft HRMS and Financials (version 7)using
> Oracle 8, Unix/NT.We have
> mapped out the steps taken by the user for each of
> the customized programs,
> and will test these steps with various system dates
> to cross over Dec-Jan
> and for Feb 29.My question is, what is the most
> efficient way to document
> our results?At this point, we are looking at a
> checklist of items tested,
> Pass/Fail status, and the date and initials of the
> tester with comments
> where appropriate. If an item fails, we will route
> it through our regular
> Software Modification procedures.Do you think we
> need more extensive
> documentation than this?We have certifications from
> our hardware/software
> providers about their Y2K status, so we are only
> concerned about our
> customized work in PS and the interfaces.Any
> pointers?Thanks,
> Joe Johnson
>
>
> -----Original Message-----
> From:   Kiran Kumar [mailto:kiranjk@YAHOO.COM]
> Sent:   Friday, August 27, 1999 5:51 PM
> To:     Multiple recipients of list SQR-USERS
> Subject:        Re: Y2K Stuff
>
> Joe, I worked on the Y2k Stuff. What kinda info are
> you exactly looking
> for
>
> -Kiran
>
> --- Joe <jejohn1216@SURFREE.COM> wrote:
> > Hello, Group.
> >
> > Does anybody have or does anybody know someone who
> > has a good sample of Y2K testing documentation.
> >
> > We are checking for compliance (why do today what
> > you can put off til tomorrow, right?) and we
> realize
> > that we could either produce an epic waste of
> > time/paper/resources in an attempt to cover our
> > legal cushions or we could not document well
> enough
> > to avoid being sued.  We want to create a lean,
> mean
> > document that shows our complete testing results.
> >
> > Any help would be -------- well, helpful!
> >
> > TIA
> >
> > ~~ JEJ ~~   ;{)
> >
> > __________________________________________
> > $14.95 a month Unlimited Internet Access.
> > Get your first month for $1.00.
> > http://www.surfree.com/promo
> >
>
> __________________________________________________
> Do You Yahoo!?
> Bid and sell for free at http://auctions.yahoo.com
>

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com