// Use this file to list those test suite skeleton files in the parent directory's fmt and x-fmt sub directories, where
// DROID is not expected to return an identification.
// Normally we would expect the identification to match the start of the filename e.g. x-fmt-384-signature-id-212.mov
// to be identified as x-fmt/384.
// Enter each file on a new line.  You may add comments on the same line by using a tab separator, also entries can be
//commented out by prefacing with //.
fmt-59-signature-id-76.xlw    //GUI identifies only by extension
x-fmt-384-signature-id-212.mov
x-fmt-384-signature-id-691.mov
x-fmt-384-signature-id-717.mov
x-fmt-384-signature-id-760.mov
x-fmt-384-signature-id-780.mov
//x-fmt-412-signature-id-199.jar //Not identified in GUI.  Test identifies as x-fmt/412 but normal no profile run as x-fmt/263
//fmt-292-signature-id-309.odp      -Not identified in GUI but name-based identification in test.
//fmt-292-signature-id-310.odp      -Not identified in GUI but name-based identification in test.
//fmt-293-signature-id-311.odp      -Not identified in GUI but name-based identification in test.
//fmt-294-signature-id-312.ods      -Not identified in GUI but name-based identification in test.
//fmt-294-signature-id-313.ods      -Not identified in GUI but name-based identification in test.
//fmt-295-signature-id-314.ods      -Not identified in GUI but name-based identification in test.
//fmt-482-signature-id-906.ibooks   -Not identified in GUI but name-based identification in test.
//fmt-483-signature-id-905.epub     -Not identified in GUI but name-based identification in test.
