Reference solutions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
Sometimes it make sense to have hidden users just for the sake of having a way to test solutions in the actual contest environment. I propose to have a way to attach to a task one or more submission together with, optionally, their expected results. CMS could then retest these submission after every modification to the task data in order to inform the admins of any mismatch between the expected and actual results.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating how CMS stores task data and submissions and how task-data changes trigger retesting; done means tasks can have reference submissions with optional expected results and admins are informed when actual results differ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100