Instructor: The OS161 AutoTester
We have provided you a program called os161-tester that allows you to 1) test your code with various test cases, and 2) allows simulating the way we will be marking your code automatically. Please use this program before submitting your code so that you can catch obvious svn checkout errors, compilation errors, etc.
Testing your code
Please use the following commands after you have built your kernel:
% cd ~/ece344/root % os161-tester [assignment_nr]
You will need to run the tester from the OS161 root directory. If you specify the assignment number then the tests will be run for that assignment. Otherwise, the tests will be run for all assignments. For each test, you will see one or more PASS or FAIL results. You can see more verbose output from the tester by specifying the -v or the -V options to the tester. Please use os161-tester -h for more details.
The output of the tester will be stored in two files in the root directory:
| os161.log: | Shows the output of your kernel when running the os161 tester. |
| os161-mark.txt: | Summarizes the marks for the various tests. |
You can simulate the marker with the following commands:
% cd ~/ece344 # make a brand new directory % mkdir marker % cd marker % os161-tester -m [assignment_nr]
The -m option will simulate the marker functionality. It will checkout your code from SVN using the assignment's end tag (e.g., asst0-end), build the code, and then run the testing functionality on this code.
The output of the marker will be stored in four files in the ~/marker directory. The last two files are copies of the outputs of the tester.
| os161-marker-<group-nr>.log: | Shows the output of svn checkout, and configuring and building the os161 code. |
| os161-tester-<group-nr>.log: | Shows the output of running the os161 tester functionality. |
| os161-<group-nr>.log: | Shows the output of your kernel when running the os161 tester. |
| os161-mark-<group-nr>.txt: | Summarizes the marks for the various tests. |