Y2K - Testing times ahead
In last week's article I mentioned the need for testing software and hardware for Y2K compliance. This week, I'd like to expand on that following some "discoveries" whilst carrying out testing at work.
Not as safe as you might think
You would imagine that if you bought a brand new PC today that it would automatically be Y2K compliant, especially if the manufacturer claimed that the particular model IS compliant. However, we have had 2 laptops, straight out of the box that failed Y2K BIOS checks.
These are not old models either but the latest versions of the laptops (I'll spare the manufacturer's blushes by not naming them). It goes to show though that the need to test hardware and software is very important even if you have the latest software and hardware. Don't let your guard down and don't trust everything you read on a manufacturers web site!
You may wonder how this can happen (OK, maybe not, but I'm going to tell you anyway!). It happens when old or untested components are added to a "new" machine. Manufacturers often stockpile chips so that they can maintain a constant flow of machines to the market. Often, chips are made in countries that are not so hot on Y2K issues and this is where the problem lies. Slip and old component into a new machine and you may have Y2K compliance issues.
Testing times ahead
Hardware is not the only issue for testing. Software needs testing too. You need to devise a series of tests (known as test packs) that will test your applications to ensure that they will be compliant and work correctly. The tests you do will depend on how you use your applications and which features you employ. You need to cover as many aspects as you can but you also need common sense otherwise you could create so many tests it will take you far into the next millennium to complete them!
It's important that before you test software, you ensure that your hardware is compliant. This is essential, as non-compliant hardware will make software appear to be non-compliant. All testing should be done on a fully compliant system.
I've come up with 5 categories that should cover most events. These are:
· Data storage
· Data retrieval
· Date calculations
· File date stamps
· System date / time tests
These categories will cover applications and operating systems alike. It is doubtful that you would use all categories for every application so only use those that are appropriate. Each category is split into 2 sections. System roll over and system reboot.
Latest Articles