MoonshotAI / MoonshotAI/kimi-code
Tests and evidence organization
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
Question
Organize tests following the convention: tests/ sits at the top level, loosely mirroring the structure of src/. Keeping tests out of the shipped tree makes them trivial to exclude from a distribution while remaining easy to run.
For evidence (benchmark output, eval runs, recorded model responses, captured fixtures) — store under tests/ in a directory named for the run, never edit a recorded file after the fact. One directory per run, named for the version or date.
Decision needed: Current test structure is scattered across packages. Need to create top-level tests/ mirroring src/ structure, and establish evidence directory conventions.
Label: wayfinder:task
Part of #2517
Blocks: #2518
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
Inspect the current test locations across the packages and compare them with the top-level src/ structure. Define the top-level tests/ layout and the per-run evidence directories, then verify that tests are outside the shipped tree and that the evidence convention is consistently applied without modifying recorded files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100