Checks student submissions automatically
- Read the solutions.txt file
1.1 Also read the connection data and the tag list. Each tag corresponds to one task of the assignment.
- Read all student submissions
2.1 Extract the (tag -> submissionSQL) mapping from each student submission
-
Apply each mapping extracted in 2. to the solutions file read in 1. Each tag in the solutions file will be replaced by the sql found in the student submission
-
Execute each "replacement" via Fitnesse and DBFit
-
Write the results of 4. to files
5.1 Write to a csv file ("summary")
5.2 Write to a log file ("mistakes")
This section describes the content of the output files. Each file has a unique number in its file name. This is the date/time of its creation in the following format
yyyyMMddHHmmss
Example file names:
- summary_20151003165859.csv
- mistakes_20151003165859.log
The summary file shows the summary of running all the student submissions. Each row corresponds to a student submission, each column corresponds to a count of correct/wrong/faulty/ignored statements and a status label for each query. In the following columns, the table shows the result of running each individual query. An example for the content of a summary file could be:
Submission;Right;Wrong;Ignored;Exceptions;Query1 (1a);Query2
The first field identifies the submission, the following four fields contain counts which show, how many statements were right, wrong, ignored or caused an error. The following columns show the status of each query. These labels can consist of a combination of one of the following letters:
| Letter | Status | Meaning |
|---|---|---|
| p | Passed | The result was either partial or completely correct |
| f | Failed | The result was either partial or completely wrong |
| i | Ignored | Something of this statement was ignored (possibly due to a previous problem) |
| e | Error | Something caused an error |
This log contains one entry per submission. If a submission contains a query which was wrong, ignored or caused an error, then this statement will be written to the log. This consists of the query, which is called, the command, the expected results and any Exceptions.