Add Guise Mummy tests for existing functionality.
Guise Mummy was built so rapidly, it is missing a lot of unit tests. Many more need to be added. Here are an example of some:
Configuring bare file names correctly removes the extension.
Files and directories beginning with _ are not included in navigation menus.
Files and directories beginning with _ (veiled) are renamed to remove it, even as a segment in the middle of a path.
Files and directories beginning with $ (assets) are also considered veiled.
Files and directories beginning with $ (assets) result in no phantom content files being produced for directories.
Files named with post naming conventions result in the correct subdirectory structure.
Relocating a template to a different directory results in the correct references.
Relocating an HTML DOM tree from the source tree to the target tree results in the correct references.
Retargeting references work correctly for a directory content file (e.g. index.html).
Relocated self references work.
Links to target collection resources end in slash, even if the target directory does not exist in the source tree.
Retrieving children of a directory content file (e.g. index.html) returns children of the directory, not including the content file.
Retrieving siblings of a directory content file (e.g. index.html) returns siblings of the of the directory, including the directory.
References to artifacts with i18n names are properly encoded.
S3 resource names are properly encoded.
S3 collection names end in slash.
Generating a navigation list detects a self link even for subsumed artifacts such as index.html.