Home > Guides > Programming > .NET and Windows Programming

Toggle Open Guide Table of ContentsGuide Contents

Close Table of ContentsGuide Contents

Close Table of Contents

Best Practices - Testing

Last updated Jun 10, 2005.

Programmers have a reputation (deserved in some cases) of not testing their code thoroughly before calling it done. This is unfortunate, because it's much easier for a programmer to spend a relatively short amount of time testing prior to sending the latest creation off to QA than to come back to the code a few days or weeks later after a QA tech submits a bug. Not only is the bug harder to find than it would have been to identify and squash before integration, but now there's a bug in the system that will require follow-up testing and regression testing with each new release. It's just easier and a lot less embarrassing to find and fix bugs before they ever make it to the checked-in code.

The best way to ensure higher-quality code is to thoroughly test each addition or change to the program at the time you make it. Bugs that are found early during the development cycle are much easier to fix and a lot less embarrassing. "Test as you go" should be the rule. There are three types of testing that you should perform when during development.

Discussions

Copies of the array?
Posted Dec 23, 2008 03:40 PM by luige21
1 Replies
Hi
Posted Dec 5, 2008 05:10 AM by ajay2000bhushan
2 Replies
You have no clue.
Posted Jun 10, 2008 03:28 PM by theinternetmaster
1 Replies

Make a New Comment

You must log in in order to post a comment.

Related Resources

Jim Mischel"Highly unlikely" does not mean "impossible"
By Jim MischelJuly 18, 2009 No Comments

One of my programs crashed the other day in a very unexpected place.  A call to System.Threading.ConcurrentQueue.TryDequeue (from the Parallel Extensions to .NET) resulted in an OverflowException being thrown.  Investigation revealed a pretty serious bug in the System.Random constructor.

It's Here; Put Away Your Pre-Conceptions on What an OS Must Be: Part II
By John TraenkenschuhMay 24, 2009 No Comments

In the last blog in this series, Traenk relates his first experiences with computers and with coding.  But now, some years have passed. . .

It's Here; Put Away Your Pre-Conceptions on What an OS Must Be: Part I
By John TraenkenschuhMay 24, 2009 No Comments

Traenk relates his past experience with Operating Systems that goes back 25 years, ok, more than that but he ain't tellin'

See More Blogs

Informit Network