Directory structure and files

Each test set should have it's own directory where the information about the test is stored. This information contains the parameters of the test, playlists, the samples and the results. The structure of the test directory is shown below.

1 · Test configuration

The file test.config contains the information needed to perform the test. It tells the type of the test, samples used, number of testees and so on. This file can be created with Test creation module. The test config file is usually named 'test.properties' but the name can be anything you want.

More detailed information: Format of the test.config file

2 · Test items

Test items file contains information on how samples are used together in a test. In it the tester can generate pairs or triples of samples that form the test items. The test items file's name is usually 'items.properties'.

More detailed information: Format of the test items

3 · Playlist

The playlist tells the order the individual test items are presented to the subject. A single test item can be, for example, a certain sample pair in the case of the AB-test. As the result of performing one test item an entry is generated in the results file.

More detailed information: Format of the playlist

4 · Sample list

The sample list relates the sample IDs the test items use to the actual audio samples. The information about a sample contains at least the sample ID and the file name of the audio file. Depending on the type of sample, additional information may be also stored.

More detailed information: Format of the samplelist file

5 · Audio samples

The actual audio sample files are usually kept in its own directory. The available sound sample formats are listed in the Sound Player documentation.

6 · Results

The results from a test session are stored in a file using Java's serialization system. One test session produces one session log or results file. Some information is stored about the session in addition to subjects' answers.

The file name of the session result file is automatically generated from the session ID. It is the form of 'results_sessionID' where sessionID is the session ID of session. Session IDs are generally like 'S14864464' (automatically generated session ID, the letter 'S' followed by a number of minutes after January 1st, 1970) or 'ses03' (explicitly set session ID by tester). A name for a session result file could be, for example: 'results_S14864464.ser' (.ser-suffix is added to show that it is a serialized file).

More detailed information: Format of the results, result processing


· Document index ·

Last modified: Fri Apr 17 16:38:18 EET DST 1998