> a. Should be able to excercise all the possible creation, read, write
and other options i support.
Yes, it should. Do buffered/unbuffered/mapped
/whatever.
b. Should be able to vary the payloads.
What do you mean ?
Well, what I meant was again related to different threads trying to clog up
the driver at the same time.
c. Multithreading should be excercised.
Well simply run several instances of your bot. Be lazy. 
He, he, that was good…only then we need to read and write different files
also, to decrease the caching and increase the load on the driver.
d. All failure states should be excercised.
Use driver verifier to inject faults.
This is interesting…honestly, didn’t think of it before reading your
mail.
Is your file system meant for removable devices ? If you do, you should do
the “violent removal test”.
yes, it has to support every possible media type windows supports.
Which is, do a long read, remove the device. Same for writing. It should
not crash the system (but of course the read/write will faulty).
You should try your fs on different hardware if possible. Also, test it
on a multi cpu machine. Funny things happen sometimes. ^^
Yes, multi CPU is also one thing i should add in the list. Is multi CPU
testing too much different from a hyper threaded cpu test??? Or can I use
teh same one for both?
amitr0