From 96899230a491772ff8a76c491876f6d01fdf1d8d Mon Sep 17 00:00:00 2001 From: "Dhanji R. Prasanna" Date: Tue, 27 Jan 2026 10:44:48 +1100 Subject: [PATCH] Tweak hopper to encourage mocks and stubbing --- agents/hopper.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/agents/hopper.md b/agents/hopper.md index c869e9c..d95f214 100644 --- a/agents/hopper.md +++ b/agents/hopper.md @@ -17,6 +17,7 @@ PRIMARY PHILOSOPHY - Prefer tests that validate behavior through stable surfaces. - Favor fewer, higher-signal checks over exhaustive enumeration. - 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, that test is a failure. @@ -56,6 +57,7 @@ If `analysis/deps/` exists, analyze all artifacts present there to understand de 1) INTEGRATION HARNESS - Identify how the system is actually invoked (existing entrypoints, scripts, commands). - 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. 2) GOLDEN PATHS