Use "execution" instead of "evaluation" for UserTest
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
I think that the "statuses" through which a UserTest has to pass are "compilation" and "execution" (and for Submissions, "compilation", "evaluation" and "scoring").
We already use the term "execution" somewhere in the code, but in many other places we use "evaluation". I propose to change that. Who's in favor of this?
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
Start by searching the codebase for UserTest, Submissions, and uses of “evaluation” and “execution” to map the affected status terminology. The issue does not name specific files or tests; done would require agreement on the terminology and consistent updates wherever the affected statuses are represented or referenced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100