Oct
13
Gah!
October 13, 2005 |
I just got this in my email…
Testing a software application before turning it on in aproduction environment is critical, particularly if theapplication will have a significant impact on the business.Organizations that test applications while they are underdevelopment are likely to save money because it’s moreexpensive to fix problems later on when programs becomemore complex. Download this Premium tool to calculatethe benefits of testing software in your company.
Are there actually companies that promote software into a production enviornment without testing it? I mean, not emergency patches and the like, but entire applications? Custom applications at that?
Jesus. I’ve seen some mighty impressive goofs in my time, even made one or two. But the idea that people have to be convinced that they should test applications at all is just mind-boggling.
Comments
What I'm Reading- Agile Requirements Information Model (4) – Subset For Agile Programs (a): Features and Feature BacklogScaling Software Agility
- The Great Implication of Context-Driven MethodologyJames Bach's Blog
- User stories versus Use CasesBusiness Analyst Blog
- Can Use Cases Possibly be Agile?Agile Product Owner (.com)
- A little bit of levity for the holidays from iRiseThe iRise Blog
- The end of reposiphilia?The Forrester Blog For Technology Product Management & Marketing Professionals
- IT ethics and the recessionIT Project Failures
- Risk Assessment ModelingEDS' Next Big Thing Blog: Read and Respond to What the EDS Fellows Say About Technology
- Test Requirements, Don't Test CodeHerding Cats
- Enterprise architecture is optionalBizRules Blog