Nothing really earth-shattering, but I thought there were some good ideas here nonetheless:

Good Tests for Bad Parameters

This document started as a one page guide, and turned into a five page list of interesting tests as it passed from tester to tester in the developer division. Please don’t consider this a comprehensive list and assume we covered everything. It was and is only meant as a starting point to help get the creative juices flowing around building your test plan. The more people that see it the more good examples we’ve added so feel free to contribute to any gaping holes in this guide!

Some examples of things to test for include:

• File Tests: Does your code rely on files?
• File Paths: Are file paths ever given as an input to your program?
• Input from registry: Use the registry to store/retrieve information?
• Strings: Most apps have at least one location where strings are used as an input.
• Numeric Values
• Inputs to Web Applications
• Network Connectivity Tests