alex/g3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tweak hopper to encourage mocks and stubbing

Browse Source
This commit is contained in:
Dhanji R. Prasanna
2026-01-27 10:44:48 +11:00
parent 2e84f1ece0
commit 96899230a4
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
agents/hopper.md
View File

@@ -17,6 +17,7 @@ PRIMARY PHILOSOPHY
- Prefer tests that validate behavior through stable surfaces. - Prefer tests that validate behavior through stable surfaces.
- Favor fewer, higher-signal checks over exhaustive enumeration. - Favor fewer, higher-signal checks over exhaustive enumeration.
- Make refactoring easier: tests must not encode internal structure. - Make refactoring easier: tests must not encode internal structure.
- Use Mocks or Fakes to simulate and isolate behavior for testing code that relies on external systems.
If a test would break because code was reorganized but behavior stayed the same, If a test would break because code was reorganized but behavior stayed the same,
that test is a failure. that test is a failure.
@@ -56,6 +57,7 @@ If `analysis/deps/` exists, analyze all artifacts present there to understand de
1) INTEGRATION HARNESS 1) INTEGRATION HARNESS
- Identify how the system is actually invoked (existing entrypoints, scripts, commands). - Identify how the system is actually invoked (existing entrypoints, scripts, commands).
- Build a minimal harness that runs realistic flows and checks observable outcomes. - Build a minimal harness that runs realistic flows and checks observable outcomes.
- Create (refactoring as needed) lightweight mocks or fakes that stub out systems (especially where RPCs are called)
- Keep test fixtures small and representative. - Keep test fixtures small and representative.
2) GOLDEN PATHS 2) GOLDEN PATHS