norrisaftcc / norrisaftcc/algorithm-liza
M3: Eval task format and the first ten tasks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
A tasks/ directory where each task is a directory containing a prompt, a pytest file, and a manifest declaring the expected entry point.
Ten tasks minimum, deliberately spanning the range from trivially easy to reliably-failing, so the suite has headroom in both directions. A suite where everything passes and a suite where everything fails are equally uninformative. Draw from real intro-Python coursework: string formatting, loops and conditionals, a small class, file I/O, a recursive function, a function with awkward edge cases.
Done when the tasks exist with their tests, and each test file has been verified against a known-good reference solution.
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 inspecting the repository and the proposed tasks/ directory structure, then identify how pytest files and manifests should describe each task's expected entry point. Create at least ten introductory Python tasks spanning the listed difficulty range, with prompts, tests, and manifests. Verify every test file against a known-good reference solution and confirm the suite includes both passing and reliably failing cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100