| || |
Testing Operating System Upgrades
Does anyone have a checklist of tests that they run after Upgrading an Operating System. My current application runs on NT4 and the OS is being upgraded to 2000. I'm not looking for application specific tests but more OS level tests (i.e. modems, security, etc.) Thanks!
Re: Testing Operating System Upgrades
Check the basic operations of the operating system. For example, do file associations still work correctly?
Check if the device manager still works and if it is now reporting anything not working correctly (either a red or yellow dot).
Check if Web browing abilities are still there. Also check if the network "browsing" abilities are still there (via "My Network Places") in Win2000.
Make sure any environment variables made the change smoothly, particularly your system variables.
Make sure that any profiles that were setup are, in fact, still extant.
Make sure the control panel applets still function. (Some of that would have been covered in the above tasks.)
If you had IIS on the NT machine, make sure you can still access not only the PWS component but the Internet Services component as well. (Sometimes during an upgrade from NT to 2000 the Management Console files in the OS get mixed up and cannot be opened.)
Make sure your event viewer is empty before you do the upgrade and then make sure that it is working after you do the upgrade (by making sure the OS reported the basic boot-up events).
Make sure all local security policies, ODBC sources, and any automatic services are all present and account for. (Some services during an upgrade get hung in a "starting" state and that is something to look for.)
Any peripherals that worked under NT, particularly things like external drives, scanners, printers, etc. should be checked to make sure they were incorporated into the new operating system.
There are various other things you can do but this gives you the general gist. Just check the things that rely on the full operations of the operating system.