Test cases management

Each test case is represented by three files in the problem directory:

• input file (*.in by default)
• expected output file (*.ans by default)
• actual program output file (*.out by default)

These files are shown in IDE by default. Also, there's a file with the list of all the test cases and program execution results on them. The problem directory is synchronized between the ACHelper application and the file system. Thanks to that, when you launch the tests from the IDE, the execution results are shown immediately in the application. Also, you can create (or download) new test files, and they will be automatically added to the test list.

The problem interface shows a table with all the tests cases (truncated for large files) and supports the following operations:

• create a new test case, edit or delete the selected test case;
• move test case up or down to control the order in which the test cases are launched;
• mark test case as skipped to ignore it;
• mark test case as solved. This will set your program output as expected, allowing to check the new solution against it. This is useful in two cases: 1) you wrote a brute-force solution that is surely correct; 2) you submitted a small output to the Google Code Jam problem and got the Correct verdict. After that, you can work on a faster solution and easily check it's correctness.