Malcolm Greene wrote on 2010-06-09: > I'm working on a set of unit tests designed to stress test some file > handling capabilities of our application. > > Listed below are some file names designed to cause failures when used > with file open, copy, delete, and rename activites. > > Can anyone think of additional scenarios (path names or unusual file > access) that we could test against? My tests will initially be for the > Windows platform (2000-Windows 7), but I would welcome Linux and/or > Mac specific failure conditions as well. > > UNITTEST_DRIVE_NOT_READY = 'a:' > UNITTEST_DRIVE_READ_ONLY = 'g:' # CD drive with CD > UNITTEST_UNC_NOT_EXIST = '\\unc_not_exist' > UNITTEST_FILE_BAD_CHARS = 'path_bad_chars_*<>|' > UNITTEST_FILE_NO_WRITE = 'c:\program files' > UNITTEST_FILE_NOT_EXIST = '\path_not_exist' > UNITTEST_FILE_LOCKED = 'file_locked.tmp' # will be open > unittest_file_locked = fopen( UNITTEST_FILE_LOCKED, 1 ) > UNITTEST_UNICODE_PATH = 'unicode_chars_here' > > Thank you, > Malcolm >
Malcolm, When the parent directory does not have read access. \\network\noread\readwrite I had a customer setup the users "Documents" folder to the network using this scenario. The readwrite is the user directory, the noread folder did not have rights to view the names of any files/folders with in it. Tracy Pearson PowerChurch Software _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/000701cb081d$0e930120$2bb903...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
