I am currently involved in an operating system upgrade process that will test all company application (mainframe, client server, web...) and then we will automate the process. Does anyone have any advice or a structured testplan on what key aspects to cover during the functional testing, batch testing... Please send me any info you have regarding this issue. Your help is greatly appreciated!
We are in the middle of doing the same thing. What we decided to do from experience was to pick a few of our processes that run the gamut of what we do and test them. We have done exhaustive tests of every process we run on these things before but got no real added value than if we tested just a couple of our apps. We do message brokering for this company and its various subsidiaries. We are testing one of our applications that goes from our farthest node in and out. That encompasses our entire process. If you have a lot of applications that do a lot of different things you might pare them down to a subset of ones that do much the same kind of process, ie Client/Server, DB, etc. That would at least give you some scope.
The most exciting phrase to hear in science, the one that heralds the most discoveries, is not "Eureka!", but "That's funny..."
Thanks for the info. I just got through explaining the same issue you wrote. I was explaining that we should classify applications such as client server, web... and if we were to have 3 company applications that all are built in MS Excel that we should test the one that utilizes the most functions (because we are testing the application in regards to the operating system and not testing the functional aspect of the application itself). I have basically proposed a structured testing methodology and that will then be converted to automation so when the live production move happens we can execute the tests by automation. Any concerns that you undergo with your project please let me know. Thanks again.