AGENTS.md: require new integration tests to join an existing directory suite

Open Beginner friendly
#3,187 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Start with AGENTS.md, sections "Testing" and "Code shape", plus the PR-review checklist; both need the new rule. Read xtask/src/lanes.rs (ISOLATED) and xtask/src/plan.rs (SLOW_BINARIES) so the exemptions are named accurately, and skim docs/decisions/3169-gate-unit-sweep.md and the #919 comment for rationale. Done means both documents state the directory-suite rule and its exemptions, and the PR body carries Process change: yes.

Written by the indexing model from the issue text.

Description

area:build effort:low enhancement P5 source:agent

Between 2026-11-11 and 2026-11-21, workspace integration test binaries grew from 412 to 1,020 (crates/app/tests/ grew from 267 to 622). Only one directory suite (crates/motion/tests/rest_adaptive/main.rs) exists even though #927 shipped.

Each integration test binary in camcraft-app takes about 103.5 MB on Linux (about 100 MB with .pdb on Windows, docs/decisions/3169-gate-unit-sweep.md). One target set uses 82.07 GB for integration binaries out of 83.89 GB total.

Add the fourth rule from #919 Q5 to AGENTS.md ("Testing" and "Code shape") and to the PR-review checklist:

  • Add a new integration test to an existing domain directory suite (tests/<suite>/<submod>.rs) before creating a new top-level binary.
  • Exempt ISOLATED (xtask/src/lanes.rs) and SLOW_BINARIES (xtask/src/plan.rs) suites, which must stay separate binaries.
  • A new top-level integration test file requires a one-line reason in the PR body.

Wait for the xtask directory-suite prerequisite (Part of #919) so assets.rs and quick.rs handle directory suites before the rule takes effect.

Evidence and measurements: https://github.com/NeoTech/Camcraft/issues/919#issuecomment-7065686766

Done means: AGENTS.md and the PR-review checklist state the rule and its exemptions, and the PR body includes Process change: yes.

Part of #919

Dominant language
Rust
Stars
8
Forks
11
Avg merge
8h 12m
Merged PRs (30d)
928

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NeoTech/Camcraft

All issues in NeoTech/Camcraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.