FC Test 1.0: Closer Look
So this is the new incarnation of the FC Test:
The interface is left barren and low-key – as a regular work tool, it doesn’t need any embellishments. The deepest menu element is the New item:
Here you can create a new pattern (a description of a set of files) or a file-list. A file-list differs from a pattern in its being fixed to a definite logical disk. It describes a set of files that are really on the drive, while a pattern…Well, the screenshots below explain themselves:
As you may guess, the left screenshot shows a pattern file opened in the Notepad, while the right one contains a file-list. The pattern just says it includes 100 files, 1MB each, but the file-list not only identifies the precise location of the files (the logical disk D), but also calls each file by its name. If you are creating a file-list by scanning a specific folder on the drive, all files in this folder, and all files in the subfolders, will be included into the file-list. The relative path to every file will also be stored in the file-list.
For a fast calculation of the amount of data described by the file-list, it stores the size of each file independently.
The Open menu item was also redesigned:
Now it offers a file filter for supported file types (i.e. files with .ptn and .fls extensions) and contains icons of quick access to places of a probable location of the desired files.
Now, new to the FC Test, the menu contains the Run Script item.
After choosing this item, you can select a file with an algorithm of the benchmark’s operation and put it in execution. The script is stored in .SPT files. If you use relative file paths, the directory with the script is considered as the current directory. It is also in this directory that the log-file is created (it has the same name as the script plus the .log extension). The script’s progress is recorded in this file in the CSV format.
And that’s how a script may look from the inside:
As you see, we deal with a simplest command processor.
Each command takes one line of the script; blanks at the beginning and the end of the line are ignored. Operands are separated by blanks. If an operand contains a blank, it should be taken into single or double quotes. An operand with single quotes should be taken into double ones and vice versa. Empty lines or lines that start from the “#” symbol are ignored.