.NET languages are becoming increasingly popular for driving the application
logic for business-critical SOA and Web applications. In these contexts,
functional errors are simply not acceptable, and reliability, security, and
performance problems can have serious repercussions. Yet, few development
teams have the resources to ensure that their code is free of implementation
errors, let alone also worry about reliability, security, and performance.
Whether or not your team has a satisfactory strategy for functional testing,
you're taking several significant risks if you haven't yet implemented a
comprehensive team-wide quality-management strategy:
New code might cause the application to become unstable, produce unexpected
results, or even crash when the application is used in a way that you didn't
anticipate (and didn't test for). New code might open the only door tha... (more)
Developer testing done early in the software's lifecycle is known to have a
high positive impact on application quality, since this is the phase where
finding and fixing bugs is cheapest, easiest, and fastest. Ideally, coding
standard checking and unit testing would be done on every piece of code
before it was added to a team's code base. However, this is not always
practical. Many organizations don't give developers the time and resources
needed for this testing. Moreover, most organizations don't develop
applications "from scratch" by writing new code for all required
functio... (more)