M-2: harness scenarios S-SET-001..008 in both transport modes (UQ-5) #108

Open
opened 2026-05-12 19:36:58 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-05-12 19:36:58 +00:00 (Migrated from github.com)

Goal

File harness scenarios S-SET-001..008 covering Settings round-trip per-field, hotkey collision, API-key validate (mock provider via UQ-1). Both transport modes mandatory.

Scope

  • 8 scenarios with deterministic assertions
  • API-key validate uses ProviderOverrides mock (UQ-1 gate)
  • Hotkey collision scenario asserts bindFailed emit
  • getSettings.confirmationTimeoutSeconds round-trip vs ConfigStore.perTurn().confirmationPolicy.timeoutSeconds

Files

  • packages/Harness/Tests/HarnessTests/SettingsScenarioTests.swift (new)

Acceptance

  • 8 scenarios filed
  • All run in both transport modes
  • Hotkey collision: bindFailed emit observed
  • confirmationTimeoutSeconds round-trip asserted
  • All green

Test

swift test --package-path packages/Harness --filter SettingsScenarioTests green.

Parent epic

#6

Source

.planning/architecture/JARVIS-API-MIGRATION-PLAN.md §2.3 (M-2.4)
.planning/architecture/JARVIS-API-TEST-CONTRACT.md Settings coverage

## Goal File harness scenarios S-SET-001..008 covering Settings round-trip per-field, hotkey collision, API-key validate (mock provider via UQ-1). Both transport modes mandatory. ## Scope - 8 scenarios with deterministic assertions - API-key validate uses `ProviderOverrides` mock (UQ-1 gate) - Hotkey collision scenario asserts `bindFailed` emit - `getSettings.confirmationTimeoutSeconds` round-trip vs `ConfigStore.perTurn().confirmationPolicy.timeoutSeconds` ## Files - `packages/Harness/Tests/HarnessTests/SettingsScenarioTests.swift` (new) ## Acceptance - [ ] 8 scenarios filed - [ ] All run in both transport modes - [ ] Hotkey collision: `bindFailed` emit observed - [ ] `confirmationTimeoutSeconds` round-trip asserted - [ ] All green ## Test `swift test --package-path packages/Harness --filter SettingsScenarioTests` green. ## Parent epic #6 ## Source `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md` §2.3 (M-2.4) `.planning/architecture/JARVIS-API-TEST-CONTRACT.md` Settings coverage
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#108