You Are Not Done Yet: Filenames

You are not done testing yet unless...
You have tested the following boundary conditions for filenames:

• Single character filenames
• Short filenames
• Long filenames
• Extra-long filenames
• Filenames using text test cases
• Filenames containing reserved words
• Just the filename (file.ext)
• The complete path to the file (c:\My\Directory\Structure\file.ext)
• A relative path into a subfolder (Sub\Folder\file.ext)
• A relative path into the current folder (.\file.ext)
• A relative path into a parent folder (..\Parent\file.ext)
• A deeply nested path (Some\Very\Very\Very\Very\Very\Deeply\Nested\File\That\You\Will\Never\Find\Again\file.ext)

Filenames are interesting creatures and a common source of bugs. Microsoft Windows applications that don't guard against reserved words set themselves up for a DOS attack. Applications on any operating system that allow any old file to be opened/saved/modified leave a gaping hole onto "secured" files. Some users stuff every document they've ever created into their user folder. Other users create a unique folder for each document. Certain characters are allowed in filenames that aren't allowed elsewhere, and vice versa. Spending some focused time in this area will be well worth your while.

Posted by The Braidy Tester at 07:30 AM  Permalink