Test Case Format

Test Case Files

Each test case contains two files:

input file

The file that your program should *read* in order to compute the result.

output file

The *exact* output that your program should *produce*. This is the value that would be entered into the result box on the assignment submission page.

If the assignment has multiple submission boxes for the same input, each box's value will be on a new line.

File Names

File names contain the following tokens, each separated by a single "_" character.

• [input/output]
• [contributor OR description]
• [index] (arbitrary)
• [problem size]

For example, the file input_beaunus_1_2.txt is beaunus's input file for a problem size of 2. The file output_beaunus_1_2.txt is the corresponding output file for that input.

Similarly, the files input_completeRandom_35_8192.txt and output_completeRandom_35_8192.txt are corresponding files for completeRandom test cases of problem size 8192.

Why is the contributor's name or description included?

• Individual contributors have control over the indices in their files.
• Developers can easily batch delete and create their own files with shell commands like rm *myname*.txt. Other contributor's files are untouched.
• Contributors can easily modify the README.md for a particular assignment if their files require explanation. For example, a contributor may want to state which edge cases their files cover, if any.