My goal for OpenAFS for Windows is to release a stable build approximately once a month containing new features. As everyone has probably noticed, over the last ten days there have been three releases of OAFW. One to introduce new features and performance improvements (1.5.22) and two more in rapid succession to fix bugs (1.5.23 and 1.5.24) introduced in the feature release. The bugs were introduced in code paths for which I do not have sufficient test suites. Eye ball reviews of the source code changes by multiple developers familiar with the code did not identify the issues. The test suites I do have cover most of the code paths used by typical Windows applications. What I don't have are scripts to test the non-Windows operations.
I am looking for someone to step forward to spend several hours developing a set of scripts that can be executed on a Windows client that will test all of the fs commands, the symlink commands, as well as basic operations such as directory creation, rename, deletion, and traversal, file creation, rename, read, write, deletion, etc. The scripts can be written using the scripting language of your choice whether it be perl, python, vbscript, etc. I simply want something that I can execute and which will report errors if unexpected behaviors occur. The idea is to expand the number of code paths that are tested as part of any given release. If you can help, please contact me. Jeffrey Altman I will give a free copy of OpenAFS for Windows to the selected volunteer. :-)
smime.p7s
Description: S/MIME Cryptographic Signature
