freemo
66ac33b185
CI / lint (pull_request) Successful in 27s
CI / quality (pull_request) Successful in 33s
CI / typecheck (pull_request) Successful in 50s
CI / security (pull_request) Successful in 1m28s
CI / build (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 23s
CI / unit_tests (pull_request) Successful in 6m47s
CI / e2e_tests (pull_request) Successful in 18m21s
CI / integration_tests (pull_request) Successful in 23m14s
CI / docker (pull_request) Successful in 1m24s
CI / coverage (pull_request) Successful in 11m22s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 56m50s
- Replace ctrl+tab with ctrl+t for preset cycling in _CONTEXT_ITEMS Main Screen context, matching the actual BINDINGS registered in app.py - Remove the tab/Cycle to next persona entry from Main Screen context since no such binding exists in app.BINDINGS (tracked separately in #3338) - Add Behave BDD scenarios asserting that help panel keybindings match the actual registered BINDINGS: ctrl+t present, ctrl+tab absent, no stale tab entry for persona cycling - Add step definition for 'should not contain' assertion to support the new negative-assertion scenarios Resolves the double-inconsistency where users following the help panel instructions (ctrl+tab) would press the wrong key and get no response. ISSUES CLOSED: #3444
41 lines
2.0 KiB
Gherkin
41 lines
2.0 KiB
Gherkin
Feature: TUI Help Panel Overlay Coverage
|
|
Scenarios exercising the context-sensitive help overlay widget.
|
|
|
|
Scenario: resolve_help_context detects the active prompt mode
|
|
When I resolve help context for an empty prompt
|
|
Then the resolved help context should be "Main Screen"
|
|
When I resolve help context for prompt text "/persona list"
|
|
Then the resolved help context should be "Slash Commands"
|
|
When I resolve help context for prompt text "inspect @README.md"
|
|
Then the resolved help context should be "Reference Picker"
|
|
When I resolve help context for prompt text "!ls"
|
|
Then the resolved help context should be "Shell Mode"
|
|
|
|
Scenario: help panel overlay renders context-specific content
|
|
Given a fresh help panel overlay
|
|
When I show help for context "Main Screen"
|
|
Then the standalone help panel text should contain "Help: Main Screen"
|
|
And the standalone help panel text should contain "ctrl+q"
|
|
And the standalone help panel text should contain "enter"
|
|
|
|
Scenario: help panel overlay toggle hides the current context
|
|
Given a fresh help panel overlay
|
|
When I toggle help for context "Slash Commands"
|
|
Then the help panel should be visible
|
|
And the standalone help panel text should contain "Help: Slash Commands"
|
|
When I toggle help for context "Slash Commands"
|
|
Then the help panel should be hidden
|
|
|
|
Scenario: help panel Main Screen keybindings match actual app BINDINGS
|
|
Given a fresh help panel overlay
|
|
When I show help for context "Main Screen"
|
|
Then the standalone help panel text should contain "ctrl+t"
|
|
And the standalone help panel text should not contain "ctrl+tab"
|
|
And the standalone help panel text should not contain "tab"
|
|
|
|
Scenario: help panel global keybindings match actual app BINDINGS
|
|
Given a fresh help panel overlay
|
|
When I show help for context "Main Screen"
|
|
Then the standalone help panel text should contain "ctrl+q"
|
|
And the standalone help panel text should contain "F1"
|