Coding standards and unit testing--Why bother?
Rix Groenboom
Parasoft
<rix.groenboom@parasoft.com>
Many developers think that the industry "best practices" of coding standards and unit testing are a waste of time: They require additional effort, but they don't seem to make your life any easier, or your code any better. This is not surprising.

This session explains how developers can apply coding standards and unit testing to improve their code and prevent the number of problems they need to identify, diagnose and fix over the course of the project. The first half teaches you how to apply coding standards to prevent errors related to code functionality, security and performance. The second part focuses on how you can extend traditional unit testing to expose reliability problems that could lead to instability, unexpected results or even crashes or security vulnerabilities. We will also discuss how these test cases can be leveraged to build a project-wide automated regression system that runs in the background each night and immediately alerts the team when code modifications or additions break previously verified functionality.


Rix Groenboom




Last modified: Sun, 16 Oct 2005 20:50:27 +0200