Ahh, I see the confusion. It's not Just Witango we're testing, but the interfaces with other software as well. We have Spitfire Charts, Popcharts, Schedule Wizard, and a bunch more. We have FTP programs that download from corporate every 10 minutes and other FTP jobs that run once a day. We have Witango programs that read flat files downloaded from other systems and update database information.
We have Witango hooks to ADP payroll systems and uploads of flat files to our own corporate ERP system. If I were only testing Witango it would probably take 10 minutes. Before I turn on a new server I need to make sure all the hooks into these other systems are working as well. This is what takes the time. Did we overlook something that another system relies on that we run in to only once every other week (ADP Upload)? I was just curious as how other places did things like this. Maybe we're unique in that we are a large defense company and are using Witango only internally. I was just wondering how other people did migrations like this. >From you're response it looks like it's not that big a deal. ;) -----Original Message----- From: Ben Johansen [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 11:36 AM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: General Question - Testing Witango So are you testing the server itself, because you are already running multi-processors witango? I guess I don't see where adding 2 more processors is going to need that much testing :-b Really you should contact Sophie or Phil at With on arrangements for temp licenses ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
