mattpocock / mattpocock/evalite
Add describe/it or other ways to better organize evals within a file
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
To better categorize classes of eval, I'd love to have a method that provides the same structure offered by describe/it in test frameworks.
I'm personally partial to those two method names — they're familiar and declarative, but I understand if you have an another API in mind.
At the moment, evals have a flat structure within one eval file.
I'd love to be able to have orchistrator.ts be associated with orchistrator.eval.ts, within which, I can organize across categories of eval:
describe("Subagent routing", () => {
it("correctly routes to the knowledge search subagent", () => { ... });
it("correctly routes to the plan creation subagent", () => { ... });
});
describe("Policy enforcement", () => {
it("formats output as valid markdown", () => { ... });
it("refuses to disclose prompt", () => { ... });
});
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 locating how eval files such as orchistrator.eval.ts are discovered and how their individual evals are executed and reported. Compare the current flat structure with the proposed describe/it grouping and determine how nested names should appear in results. Done means evals can be organized into categories while still executing and reporting each case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100