From fd19e8bb4828be5ccad285c120b892e687cbfca8 Mon Sep 17 00:00:00 2001 From: Bartok9 Date: Thu, 28 May 2026 22:42:14 -0400 Subject: [PATCH] test(config): update placeholder usage assertion for --force flag MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CI caught test_config_set_usage_marks_placeholders failing on this PR's new usage line ('Usage: hermes config set [--force] ' vs the previous 'Usage: hermes config set '). The usage change is intentional — it documents the --force escape hatch this PR adds for bypassing schema validation. Update the assertion to require the placeholder markers and --force keyword without pinning the exact wording, so future doc tweaks (e.g. wrapping or color codes) don't re-break this test. Confirmed locally: 4/4 placeholder tests pass. Co-authored-by: Cursor --- tests/hermes_cli/test_placeholder_usage.py | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/tests/hermes_cli/test_placeholder_usage.py b/tests/hermes_cli/test_placeholder_usage.py index 3479d8f5703b..b21834927cb9 100644 --- a/tests/hermes_cli/test_placeholder_usage.py +++ b/tests/hermes_cli/test_placeholder_usage.py @@ -18,7 +18,15 @@ def test_config_set_usage_marks_placeholders(capsys): assert exc.value.code == 1 out = capsys.readouterr().out - assert "Usage: hermes config set " in out + # The usage line documents the optional --force flag added in #34067 + # (schema validation for unknown keys). Placeholder convention is preserved: + # the literal ```` and ```` markers must still be present so + # downstream tooling can detect placeholder syntax. + assert "Usage: hermes config set" in out + assert "" in out + assert "" in out + # --force escape hatch must be documented in the usage line. + assert "--force" in out def test_config_unknown_command_help_marks_placeholders(capsys):