Difference between revisions of "Test Harness"
From PC2wiki
m (→=Run Source Files: fixed typos) |
m (→See also: rename cat) |
||
Line 65: | Line 65: | ||
* [https://ciiwiki.ecs.baylor.edu/index.php/Contest_Control_System ICPC CLICS Finals Contest Control System Standard] | * [https://ciiwiki.ecs.baylor.edu/index.php/Contest_Control_System ICPC CLICS Finals Contest Control System Standard] | ||
− | [[Category: | + | [[Category:CLICS]] |
− | |||
[[Category:Version 9.3]] | [[Category:Version 9.3]] | ||
− | |||
[[Category:Import and Export]] | [[Category:Import and Export]] |
Latest revision as of 10:28, 3 December 2016
The CCS Test Harness is a system to test a CCS by configuring a contest, submitting runs and evaluating the output.
Testing
Input Data Set
Input data list is:
- contest.yaml with problems data and problem.yaml
- runs.tsv - runs to be submitted
- team/run source files see Run Source Files section for more details
- groups.tsv - group/region info
- teams.tsv - team info
- accounts.tsv - account names, logins, passwords
Optional
- passwords.txt - team passwords
These input files are also used to evaluate the same files created by the CCS.
Run Source Files
To submit a run information from runs.tsv and run source files are needed. Each run submission (source file) is created under its own run directory. The run directory is the word run followed by the run id (4 digits zero left padded)
Here is an example of run files in their run directories.
run0001/BadHello.java run0002/Hello.java run0003/BadHello.java run0004/Hello.java run0005/BadHello.java run0006/BadSumit.java run0007/BadSumit.java run0008/Hello.java run0009/BadSumit.java run0010/BadSumit.java run0011/BadSumit.java
Output Data Set
Filename | Source | Command |
---|---|---|
runs.tsv | Extractor | pc2extract submission |
scoreboard.tsv | Extractor | pc2extract scoreboard |
results.tsv | Extractor | pc2extract results |
Full Event Feed | Event Feed Server | nc localhost 4713 |
Frozen Event Feed | Event Feed Server | nc localhost 4714 |