Test that replay detects a changed input

Open Beginner friendly
  • Is something wrong?
#150 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
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
backend, testing

Research direction

Read src/meridian/manifest/replay.py and the existing cases in tests/unit/test_replay_verification.py. Add a test for each pinned input—suite hash, image digest, harness version, and config—that changes that field and asserts replay reports a mismatch. Done when every pinned field has a test proving its change is detected.

Written by the indexing model from the issue text.

Description

area: tests size: M tests
Context

manifest/replay.py decides whether a re-run reproduced the original. Its core promise is that any unpinned change is caught, but about half the file is untested.

What to do

For each pinned input (suite hash, image digest, harness version, config), change it and assert replay reports the mismatch.

Done when

Every pinned field has a test proving a change to it is caught.

Where to look

src/meridian/manifest/replay.py, tests/unit/test_replay_verification.py

New here? Read CONTRIBUTING.md and comment on this issue to say you are taking it.

Generated by Claude Code

Dominant language
Python
Stars
0
Forks
0
Avg merge
1h 54m
Merged PRs (30d)
14

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 patsypppe/meridian

All issues in patsypppe/meridian

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.