I haven’t tested a cookie in a long time, so long I realized I didn’t know where cookies are stored on Vista. Finding cookies on Vista is more of a headache than I can recall in any other Windows versions. There are two directories:

C:\Users\[username]\AppData\Roaming\Microsoft\Windows\Cookies\
C:\Users\[username]\AppData\Roaming\Microsoft\Windows\Cookies\Low\

Even though I had the path, I still couldn’t find the cookies. I finally learned what I needed to do was to remove a protection setting. (Even though I’m an administrator on the Vista laptop I was using and I have the annoying user control protection turned off, I still had to turn this file protection setting off as well.) I found two pieces of information especially helpful:

Coverity™, Inc., the leader in improving software quality and security, today announced Coverity Prevent™ for C#.

by Miško Hevery, Jonathan Wolter, Russ Ruffer, Brad Cross, and lots of other test infected Googlers

This guide lists principles that will help you write impossible to tests code. Or, avoiding these techniques will help you write code that can be tested.

• Make Your Own Dependencies - Instantiate objects using new in the middle of methods, don't pass the object in. This is evil because whenever you new up an object inside a block of code and then use it, anyone that wants to test that code is also forced to use that concrete object you new'ed up. They can't "inject" a dummy, fake, or other mock in to simplify the behavior or make assertions about what you do to it.

A short list of Software Testing PDFs to enjoy and learn from.The CAST 2008 proceedingsOWASP WebGoat and WebScarab - teach yourself some penetration testingThe FitNesse Fixture GalleryGetting fit with .NetPerformance Testing Guidance for Web Applications