This simplistic shell script was created as a quick and dirty way to automatically run a program against a set of inputs and evaluate the validity of the outputs. The typical use-case I had in mind was programming competitions. It's important to notice that this script does not provide any sandboxing so make sure any code you are evaluating is not malicious.
Disclaimer: At the time of writing I admit I did not have the expertise of writing good software and especially software that works well across platforms. As a consequence there are probably many bugs in the code which I have not come across if they didn't appear on my platform. I recently tried patching some of those bugs (see CHANGELOG) that people brought to my attention but I'm sure there are many more. Feel free to contact me for bugs, suggestions and general feedback at marsenis 'at' gmail 'dot' com.
There are a couple of things you can configure manually in the script. (unfortunately not much yet..)
Those are:
- input/output filename format (defaults are 'input.#.txt' and 'output.#.txt')
- time limit (default is 1 second)
- the compiler and compiling options for each language (the language is detected based on the file extension)
Note: the '#' character in the input/output filename description will be replaced by 1, 2, 3, ... for each test case. For example 'input.#.txt' means that the input files are: input.1.txt , input.2.txt , ... up to the maximum numbered test case existing in the current directory.
Just run the script with one parameter, the source code filename.
Example: ./grader.sh test.cpp
The above command will first compile test.cpp and then run the executable for each test case of the form described by the user. After each run (and if the program terminates with exit code 0 within the time limit), the output is judged based on the given correct output files.
- Your program should read data from stdin and write on stdout. The required input/output redirections are handled automatically by the script.
- Output is judged based on the given correct output files using the diff tool. As a result, the grading script might give wrong results for problems in which more than one outputs are considered correct by the problem statement.
- The script, the source code and the test cases should be placed under the same directory.
Copyright (c) 2012 Makis Arsenis
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.