story-kit: start 108_story_test_coverage_http_agents_rs_to_70
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Test Coverage: io/shell.rs to 95%"
|
||||
---
|
||||
|
||||
# Story 105: Test Coverage: io/shell.rs to 95%
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want io/shell.rs to have at least 95% test coverage, so that regressions in shell execution edge cases are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] server/src/io/shell.rs reaches at least 95% line coverage (currently 84%, 15 lines missed)
|
||||
- [ ] cargo clippy passes with no warnings
|
||||
- [ ] cargo test passes with all tests green
|
||||
- [ ] No changes to production code, only test code added
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Test Coverage: http/settings.rs to 80%"
|
||||
---
|
||||
|
||||
# Story 106: Test Coverage: http/settings.rs to 80%
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want http/settings.rs to have at least 80% test coverage, so that regressions in settings get/set handlers are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] server/src/http/settings.rs reaches at least 80% line coverage (currently 59%, 35 lines missed)
|
||||
- [ ] cargo clippy passes with no warnings
|
||||
- [ ] cargo test passes with all tests green
|
||||
- [ ] No changes to production code, only test code added
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Test Coverage: http/assets.rs to 85%"
|
||||
---
|
||||
|
||||
# Story 107: Test Coverage: http/assets.rs to 85%
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want http/assets.rs to have at least 85% test coverage, so that regressions in static asset serving are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] server/src/http/assets.rs reaches at least 85% line coverage (currently 70%, 18 lines missed)
|
||||
- [ ] cargo clippy passes with no warnings
|
||||
- [ ] cargo test passes with all tests green
|
||||
- [ ] No changes to production code, only test code added
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Test Coverage: http/agents.rs to 70%"
|
||||
---
|
||||
|
||||
# Story 108: Test Coverage: http/agents.rs to 70%
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want http/agents.rs to have at least 70% test coverage, so that regressions in REST agent status/control endpoints are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] server/src/http/agents.rs reaches at least 70% line coverage (currently 38%, 155 lines missed)
|
||||
- [ ] cargo clippy passes with no warnings
|
||||
- [ ] cargo test passes with all tests green
|
||||
- [ ] No changes to production code, only test code added
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,21 @@
|
||||
---
|
||||
name: "Add test coverage for LozengeFlyContext, SelectionScreen, and ChatHeader components"
|
||||
---
|
||||
|
||||
# Story 109: Add test coverage for LozengeFlyContext, SelectionScreen, and ChatHeader components
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want better test coverage for LozengeFlyContext.tsx, SelectionScreen.tsx, and ChatHeader.tsx, so that regressions are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] LozengeFlyContext.tsx reaches 100% coverage (currently 98.1%, 5 lines missing)
|
||||
- [ ] SelectionScreen.tsx reaches 100% coverage (currently 93.5%, 5 lines missing)
|
||||
- [ ] ChatHeader.tsx reaches 95% coverage (currently 87.7%, 25 lines missing)
|
||||
- [ ] All vitest tests pass
|
||||
- [ ] No production code changes are made
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Add test coverage for api/settings.ts"
|
||||
---
|
||||
|
||||
# Story 110: Add test coverage for api/settings.ts
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want better test coverage for api/settings.ts, so that regressions in the settings API wrapper are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] api/settings.ts reaches 90% coverage (currently 55%, 18 lines missing)
|
||||
- [ ] Tests use fetch mocks to exercise all API wrapper functions
|
||||
- [ ] All vitest tests pass
|
||||
- [ ] No production code changes are made
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Add test coverage for api/agents.ts"
|
||||
---
|
||||
|
||||
# Story 111: Add test coverage for api/agents.ts
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want better test coverage for api/agents.ts, so that regressions in the agent API wrapper are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] api/agents.ts reaches 80% coverage (currently 29.5%, 67 lines missing)
|
||||
- [ ] Tests use fetch mocks to exercise all agent API wrapper functions
|
||||
- [ ] All vitest tests pass
|
||||
- [ ] No production code changes are made
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Add test coverage for App.tsx"
|
||||
---
|
||||
|
||||
# Story 112: Add test coverage for App.tsx
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want better test coverage for App.tsx, so that regressions in the main application component are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] App.tsx reaches 85% coverage (currently 73.1%, 43 lines missing)
|
||||
- [ ] Tests cover additional integration-style scenarios for the main app component
|
||||
- [ ] All vitest tests pass
|
||||
- [ ] No production code changes are made
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Add test coverage for usePathCompletion hook"
|
||||
---
|
||||
|
||||
# Story 113: Add test coverage for usePathCompletion hook
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want better test coverage for the usePathCompletion hook, so that regressions in path completion behavior are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] usePathCompletion.ts reaches 95% coverage (currently 81.7%, 26 lines missing)
|
||||
- [ ] Tests use renderHook to exercise all hook code paths
|
||||
- [ ] All vitest tests pass
|
||||
- [ ] No production code changes are made
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: "Test Coverage: http/health.rs to 100%"
|
||||
---
|
||||
|
||||
# Story 99: Test Coverage: http/health.rs to 100%
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want http/health.rs to have 100% test coverage, so that regressions in health check endpoints are caught early.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] server/src/http/health.rs reaches 100% line coverage (4 missing lines covered)
|
||||
- [ ] cargo clippy passes with no warnings
|
||||
- [ ] cargo test passes with all tests green
|
||||
- [ ] No changes to production code, only test code added
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
Reference in New Issue
Block a user