From 1c627bcc3005e2b50b366df3d3ed1989eee6a19a Mon Sep 17 00:00:00 2001 From: Ed_ Date: Sat, 6 Jun 2026 09:34:38 -0400 Subject: [PATCH] fix(docs): correct section order in guide_testing (patterns before See Also) + fix LF/CRLF --- docs/guide_testing.md | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/docs/guide_testing.md b/docs/guide_testing.md index 8b22f0f2..01b5eeb2 100644 --- a/docs/guide_testing.md +++ b/docs/guide_testing.md @@ -644,16 +644,6 @@ See `src/gui_2.py:601-606` for the canonical implementation. This pattern unbloc --- -## See Also - -- **[guide_simulations.md](guide_simulations.md)** — Older guide focused on the Puppeteer pattern; still relevant for the test scenarios it documents -- **[guide_meta_boundary.md](guide_meta_boundary.md)** — Application vs Meta-Tooling domain separation; the test suite is in the Application domain -- **[guide_architecture.md](guide_architecture.md#the-task-pipeline-producer-consumer-synchronization)** — Threading model that the `live_gui` test fixture respects -- **`src/api_hook_client.py`** — The Python wrapper for the Hook API used in integration tests -- **`tests/conftest.py`** — The canonical source of all fixtures documented in this guide - ---- - ## Pattern: Narrow Test Paths vs. Kitchen-Sink Functions **Anti-pattern: calling a kitchen-sink function.** A test that does `gui_2.render_main_interface(app_instance)` requires mocking 50+ imgui/imscope methods because `render_main_interface` dispatches to dozens of nested render functions. Adding a single mock for `imscope.window` (to return a tuple) just reveals the next un-mocked dependency (e.g. `imgui.begin` returning bool where a 2-tuple is expected). The test never reaches its assertion. @@ -681,4 +671,13 @@ See the `prior_session_test_harden_20260605` plan in `docs/superpowers/plans/` f **How to fix:** Re-indent the affected method to 2-space class level. Run the failing test to confirm. See the `live_gui_test_hardening_v2_20260605` track in `conductor/tracks.md` for the concrete example (where `_capture_workspace_profile` was being parsed as nested inside `_apply_snapshot` due to a 1-space indentation drift after a cleanup commit). -See [guide_architecture.md](guide_architecture.md) for the overall architecture and [conductor/workflow.md](../../conductor/workflow.md) for the TDD protocol that the test suite implements. +--- + +## See Also + +- **[guide_simulations.md](guide_simulations.md)** — Older guide focused on the Puppeteer pattern; still relevant for the test scenarios it documents +- **[guide_meta_boundary.md](guide_meta_boundary.md)** — Application vs Meta-Tooling domain separation; the test suite is in the Application domain +- **[guide_architecture.md](guide_architecture.md#the-task-pipeline-producer-consumer-synchronization)** — Threading model that the `live_gui` test fixture respects +- **`src/api_hook_client.py`** — The Python wrapper for the Hook API used in integration tests +- **`tests/conftest.py`** — The canonical source of all fixtures documented in this guide +