Introduction to WCF Testing Strategies
Applies to: Windows Communication Foundation
Published: June 2011
Author: Alex Culp
Typically, software maintenance accounts for 40 to 80 percent of software lifecycle costs. This means that, on average, 60 percent of a project's costs are spent to maintain the software after it goes into production. This statistic does not take into account the cost of possible losses in revenue or productivity if the software fails. To make your project the exception to the rule, the best approach is to invest in quality early on. Advance planning makes it easier to upgrade software and not break existing features. Similarly, the earlier you identify problems, the less it costs to resolve the issues.
Management support is crucial if you want to institute the best practices that this article discusses. All too often, when faced with deadlines and concerns about time to market, quality is sacrificed in order to ship the software. If tests are not ready before the software is released, it is unlikely that they will be written after the release. The strategies proposed here do increase the cost of development, but only to reduce the maintenance costs that are the real reason so many projects are expensive. Management must be persuaded to make an up-front investment.
Previous article: Things to Consider When Implementing a Load Balancer with WCF
Continue on to the next article: General Service Testing Best Practices