Visitors Edition
Membership Help?
Need help? Our Trial Membership program will get you help on any IT project you're working on. You'll get access to our research, tools, advice and project help.
Start your free trial membership now:
Want to learn more about our membership options, pricing, or to get a product demo? Get in touch with one of our reps using an option below.
Learn more About Info-Tech
Click to Chat
  • 2
(Personalize the message)

Email 1:


Email 2:


Email 3:


Email 4:


Email 5:


Why Test New Software Releases?

More Details
Access this Note FREE by giving us your email address.

When you register you will also receive:
  • A Free Trial Membership which provides additional free research and help on your projects
  • Access to survey data, contribute to our research, community involvement and much more
CAUTION: This content has been retired, and is no longer being maintained. It may contain information or links that are out of date and/or broken. Please use this note with caution.

(By Info-Tech Analyst William Terrill - Printed with permission from Processor magazine www.processor.com).

When an IT department deploys new software without adequate (or any) testing, it tends to get what it deserves—lots of headaches, late nights in the data center, and extra work. What the business and users receive from this oversight can be disastrous. IT staff need to understand that any new software or upgrade to a critical system must be tested in real-world environments.

IT staff have a lot on their plates. One critical responsibility is the deployment of new mission-critical applications or updates to those systems. When staff shortchanges testing of new code, it also shortchanges clients and, in the process, causes more trouble and headaches. Bypassing or limiting testing of new releases, whether that code is from reputable software vendors or developed in-house, is not a good idea.


Already a member?
Please Login