Write smoke test for eval
Open
enhancement
good first issue
- Dominant language
- Python
- Stars
- 225
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Look at `tests/test_smoke_elicit.py` for a reference
Contributor guide
No contributing guide indexed for this repository
Research direction
Read tests/test_smoke_elicit.py first to understand the existing smoke-test pattern. Determine which eval behavior the new smoke test should cover, then add coverage that runs successfully and confirms the intended eval path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100