<The following is a copy of the Autograder output, with explanation notes shown enclosed in angle brackets.
These explanations include how to submit incomplete versions of your project to get feedback on the components you have completed.
See the course web pages about the autograder for more details.>
------------------------------
<The Console output tests first build your complete program, with your list implementation for Ordered_container. If the build fails, the output includes the compile/link error messages. They then test whether your program as a whole behaves correctly by giving your program a test scenario along the same lines as the provided samples. Using redirected I/O, an input file is provided for stdin, emulating console input, and the resulting stdout output file is compared to the one produced by my version of the program. If the output matches, your program passes the test.
*** Important: You need to submit *all* of the specified files, even if they are incomplete. This is because the autograder builds an executable by copying the .h and .c files into a test directory and then executing a makefile similar to the supplied one. If some of the specified files are missing, the copy operation will fail and so the build will fail.
*** Important: You can test separate components (like your Ordered_container) by submitting *all* of the specified files. The builds will fail if some functions are required that you didn't define. However, if the build succeeds, then it will be run and tested, giving you feedback on the components that you supplied.
To produce the clearest and simplest reports from the autograder, do the following:
1. your p1_main.c should contain at least a dummy do-nothing main() function.
2. submit all of the supplied header files.
3. Utility.h should contain at least the include guard code and an implementation of the supplied skeleton code.
4. Your .c files for the components should contain at least the #include of the corresponding header file.
For example, to test your Ordered_container implementations, supply all of the specified files (even if incomplete). Your Utility component will always be included with the rest of your code. My test driver will call only the Ordered_container functions.
>
Check of Console Output Correctness
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test 0 (normal sample (list))
standard output, worth 1 points: passed
Test 1 (errors sample)
standard output, worth 1 points: passed
Test 2 (typeahead sample)
standard output, worth 1 points: passed
<The following tests cover a variety of scenarios, ranging from very simple, to fairly complex. The name of the test is basically what it is about, but remember that to test most commands, the program first has to be given some data, and be asked to produce various kinds of output. So the name of the test suggests what is emphasized, but in most cases, many other commands and conditions will be involved.>
Test 3 (quit test)
standard output, worth 1 points: passed
Test 4 (empty lists)
standard output, worth 1 points: passed
Test 5 (reschedule fun)
standard output, worth 1 points: passed
Test 6 (no room and/or meeting)
standard output, worth 1 points: passed
Test 7 (big input)
standard output, worth 1 points: passed
Test 8 (many people)
standard output, worth 1 points: passed
Test 9 (add room fun)
standard output, worth 1 points: passed
Test 10 (errors and typeahead issues)
standard output, worth 1 points: passed
Test 11 (memory counting)
standard output, worth 1 points: passed
Test 12 (stress test)
standard output, worth 1 points: passed
Test 13 (restore state)
standard output, worth 1 points: passed
Test 14 (bad restore)
standard output, worth 1 points: passed
Test 15 (Invalid data)
standard output, worth 1 points: passed
Score for Project 1 Output: 16 out of 16
<The following tests examine whether the save file produced by your program has correct content.>
Check of Output File Correctness
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test 0 (save state)
indirect output, worth 1 points: passed
Score for Project 1 Output: 1 out of 1
<In the following component tests, the autograder does multiple builds to combine components of your program with components of mine, to see if your components implement and assume the specified interface and behaviors. In these tests, your Utility module is always part of the build. Each test has two parts: compilation and standard output. If the compilation fails, it means that there is a mismatch between specifications of the modules and their interfaces. The autograder will send back the compilation/link error messages. If the standard output test fails, it means that the output of the program was incorrect, meaning that your component did not behave correctly. The description of the test includes "array" or "list" to indicate whether the test used the array or list implementation of Ordered_container, and describes which of the above inputs were used in the standard output test - the normal sample in most cases.>
Check of Project 1 Components
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<The first two tests combine your list and array implementations of Ordered_container with a special testing driver. If your code fails these tests, but passes most others, it is most likely due to a missing or incorrect implementation of some of the container functions that you did not test thoroughly or did not use in your own code. Note that your Utility component is included in the build.>
Test 0 (Ordered_container test(list))
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 1 (Ordered_container test(array))
compilation, worth 1 points: passed
standard output, worth 1 points: passed
<The next three tests use all of your code, but with the array implementation to see if it behaves correctly. If your code fails the above tests on these inputs, and/or the array component test above, you should not expect it to pass these.>
Test 2 (Your code (array) normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 3 (Your code (array) memory counting)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 4 (Your code (array) stress test)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
<In each of the following, some of my modules are combined with yours, and the resulting whole program is tested with the normal sample test input. If your code fails the normal sample test, you can expect it to fail one of more of the following, and the pattern of the failure can help isolate which module is at fault. But if your code passes the normal sample test, but fails some of these, it most likely means that one of your modules is incorrect in some way, and another module is also incorrect, but compensates for the first module, so that the overall output is correct. For example, if the wrong module emits a certain message, you can get this effect. Another example: if your code defines the comparison functions with the comparisons reversed from the specifications, it will mismatch my components. Again, the pattern of failures can help isolate the defective modules.>
Test 5 (My p1_main, your others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 6 (My Person, your others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 7 (My Meeting, your others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 8 (My Room, your others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 9 (My OC list, your others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 10 (My OC array, your others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 11 (Your OC list, my others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Test 12 (Your OC array, my others, normal sample)
compilation, worth 1 points: passed
standard output, worth 1 points: passed
Score for Project 1 Component Tests: 26 out of 26
<Your total score and the bonus expressed as a proportion (0.1 = 10%) is the last result.>
Project score: 43
Bonus days: 0.1
------------------------------