freemo
051ee7c290
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 21s
CI / quality (pull_request) Successful in 31s
CI / typecheck (pull_request) Successful in 47s
CI / security (pull_request) Successful in 52s
CI / build (pull_request) Successful in 56s
CI / e2e_tests (pull_request) Successful in 5m1s
CI / integration_tests (pull_request) Successful in 5m30s
CI / unit_tests (pull_request) Successful in 5m42s
CI / docker (pull_request) Successful in 58s
CI / coverage (pull_request) Successful in 7m35s
CI / build (push) Successful in 21s
CI / docker (push) Has been skipped
CI / benchmark-regression (pull_request) Failing after 49m24s
CI / lint (push) Successful in 22s
CI / quality (push) Successful in 39s
CI / security (push) Successful in 48s
CI / typecheck (push) Successful in 1m26s
CI / benchmark-regression (push) Has been skipped
CI / e2e_tests (push) Successful in 5m53s
CI / coverage (push) Successful in 9m4s
CI / benchmark-publish (push) Successful in 19m10s
CI / integration_tests (push) Failing after 19m18s
CI / unit_tests (push) Failing after 19m20s
Added 52 new .feature files and corresponding _steps.py files targeting previously uncovered code paths in the following areas: - TUI layer: app, commands, persona (state/schema/registry), widgets, input (shell_exec, reference_parser) - Application services: plan lifecycle/service/executor, session, project, repo indexing, correction, checkpoint, actor, llm_actors, strategy coordinator, resource file watcher, service retry wiring - CLI commands: session, resource, repl, plan, db, automation_profile - Domain models: retry_policy, resource_type, cost_budget, docker_compose_analyzer, detail_level, _sql_string_aware, _postgresql_helpers - Core: circuit_breaker, retry_service_patterns - Infrastructure: repositories, transaction_sandbox, strategy_registry, plugins/loader, container - Config: settings - Agents: plan_generation, context_analysis, auto_debug - A2A: facade All new tests follow the Behave/Gherkin BDD standard. Resolved step definition collisions with unique prefixes. Fixed Alembic fileConfig logger disabling issue (disable_existing_loggers=False). ISSUES CLOSED: #1068
95 lines
4.3 KiB
Gherkin
95 lines
4.3 KiB
Gherkin
Feature: Cost Budget Model Coverage
|
|
Additional scenarios that exercise previously uncovered code paths
|
|
in the cost_budget domain model (SessionCostBudget, OrgCostAccumulator,
|
|
ThreadSafeOrgCostAccumulator).
|
|
|
|
Background:
|
|
Given the cost budget module is imported
|
|
|
|
# ── SessionCostBudget ──────────────────────────────────────────────
|
|
|
|
Scenario: Session utilization returns None when max_cost_usd is zero
|
|
Given a session budget with max cost USD 0.0
|
|
When I query the session utilization
|
|
Then the session utilization should be None
|
|
|
|
Scenario: Session can_afford returns True when budget is unlimited
|
|
Given a session budget with no spending cap
|
|
When I check if the session can afford 999.99
|
|
Then the session can_afford result should be True
|
|
|
|
Scenario: Session can_afford returns True when cost fits within budget
|
|
Given a session budget with max cost USD 10.0
|
|
When I check if the session can afford 5.0
|
|
Then the session can_afford result should be True
|
|
|
|
Scenario: Session can_afford returns False when cost exceeds budget
|
|
Given a session budget with max cost USD 10.0
|
|
And I record a session cost of 8.0
|
|
When I check if the session can afford 5.0
|
|
Then the session can_afford result should be False
|
|
|
|
Scenario: Session reset clears accumulated cost to zero
|
|
Given a session budget with max cost USD 100.0
|
|
And I record a session cost of 42.5
|
|
When I reset the session budget
|
|
Then the session total cost should be 0.0
|
|
|
|
# ── OrgCostAccumulator ─────────────────────────────────────────────
|
|
|
|
Scenario: Org utilization returns None when max_cost_usd is zero
|
|
Given an org accumulator for "org-zero" with max cost USD 0.0
|
|
When I query the org utilization
|
|
Then the org utilization should be None
|
|
|
|
Scenario: Org can_afford returns True when budget is unlimited
|
|
Given an org accumulator for "org-unlimited" with no spending cap
|
|
When I check if the org can afford 999.99
|
|
Then the org can_afford result should be True
|
|
|
|
Scenario: Org can_afford returns True when cost fits within budget
|
|
Given an org accumulator for "org-fits" with max cost USD 50.0
|
|
When I check if the org can afford 25.0
|
|
Then the org can_afford result should be True
|
|
|
|
Scenario: Org can_afford returns False when cost exceeds budget
|
|
Given an org accumulator for "org-over" with max cost USD 50.0
|
|
And I record an org cost of 45.0
|
|
When I check if the org can afford 10.0
|
|
Then the org can_afford result should be False
|
|
|
|
Scenario: Org reset clears accumulated cost to zero
|
|
Given an org accumulator for "org-reset" with max cost USD 100.0
|
|
And I record an org cost of 73.0
|
|
When I reset the org accumulator
|
|
Then the org total cost should be 0.0
|
|
|
|
# ── ThreadSafeOrgCostAccumulator ───────────────────────────────────
|
|
|
|
Scenario: Thread-safe wrapper exposes org_id property
|
|
Given a thread-safe org accumulator for "org-tsafe"
|
|
When I read the thread-safe org_id
|
|
Then the thread-safe org_id should be "org-tsafe"
|
|
|
|
Scenario: Thread-safe wrapper allows setting max_cost_usd
|
|
Given a thread-safe org accumulator for "org-setter"
|
|
When I set the thread-safe max_cost_usd to 200.0
|
|
Then the thread-safe max_cost_usd should be 200.0
|
|
|
|
Scenario: Thread-safe can_afford delegates correctly
|
|
Given a thread-safe org accumulator for "org-canafford" with max cost USD 30.0
|
|
When I check if the thread-safe accumulator can afford 15.0
|
|
Then the thread-safe can_afford result should be True
|
|
|
|
Scenario: Thread-safe can_afford returns False when over budget
|
|
Given a thread-safe org accumulator for "org-canafford2" with max cost USD 30.0
|
|
And I record a thread-safe cost of 28.0
|
|
When I check if the thread-safe accumulator can afford 5.0
|
|
Then the thread-safe can_afford result should be False
|
|
|
|
Scenario: Thread-safe reset delegates correctly
|
|
Given a thread-safe org accumulator for "org-tsreset" with max cost USD 100.0
|
|
And I record a thread-safe cost of 60.0
|
|
When I reset the thread-safe accumulator
|
|
Then the thread-safe total cost should be 0.0
|