Process scripts are covered by tests that run in CI

Open
#137 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Start by reading the scripts named in the issue: roadmap.py, sprint.py, conventions.py, check_task_ids.py, i18n.py, and project_state.py, along with their existing tests and the project’s test and CI configuration. Add offline tests in tests/process/ that cover the listed rules, then run uv run just check and confirm the tests finish in under ten seconds. Done means removing any rule causes a test failure and CI runs the process tests.

Written by the indexing model from the issue text.

Description

area:infra

Part of #136. Milestone gate: wayloop init on an empty repository produces a structure that passes wayloop validate.

Outcome

The rules of the process are code: roadmap, sprints, commit conventions, task ids, translations and the session briefing. Today they run without tests, so a change to a script can silently stop enforcing a rule, and every later pull request would pass a check that no longer checks.

Scope

  • Tests in tests/process/ for roadmap.py: canonical form, unique issues, specs that exist and are referenced, releases in order, the pull request body that closes a planned task
  • Tests for sprint.py: lanes with disjoint paths, generated files in one lane, shared state across worktrees, a pull request that leaves its lane
  • Tests for conventions.py: types, scopes, subject rules, bot commits
  • Tests for check_task_ids.py, i18n.py and project_state.py
  • pytest in the dev group; just process runs the tests; a CI step runs them

Acceptance criteria

  • Removing any rule from a script makes at least one test fail
  • The tests run offline and in less than ten seconds

Delivery

PR 1 of the process parity epic: PR 1 tests, forms and title checks; PR 2 bootstrap, required checks, security and maintenance; PR 3 hooks, documentation sync and automated review.

Definition of done

  • Tests written first for every rule the change adds
  • uv run just check passes locally and CI is green
  • The conventions or contributing page updated where a rule changes; Italian edition stamped where the page is translated
  • The task is marked done in roadmap/roadmap.yaml in the same pull request, whose body says Closes #137
  • Review proportional to risk (AGENTS.md): every finding fixed in the same pull request

Generated by Claude Code

Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

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 salvo8519/wayloop

All issues in salvo8519/wayloop

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.