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
38 lines
2.0 KiB
Gherkin
38 lines
2.0 KiB
Gherkin
Feature: Devcontainer Health Check Coverage
|
|
Additional scenarios that exercise previously uncovered code paths
|
|
in the devcontainer_health module, specifically the TOCTOU guard
|
|
breaks and ValueError exception handlers in _health_check_loop.
|
|
|
|
Background:
|
|
Given the devcontainer health module is imported
|
|
|
|
Scenario: Unhealthy probe breaks when state changed concurrently before transition
|
|
Given a tracker in RUNNING state for resource "res-unhealthy-break"
|
|
And a run_command that returns a non-zero exit code
|
|
And get_lifecycle_tracker returns STOPPED state on re-read under lock
|
|
When I run the health check loop for one iteration
|
|
Then the loop exits via the TOCTOU guard break for unhealthy probe
|
|
|
|
Scenario: Unhealthy probe catches ValueError from transition_state
|
|
Given a tracker in RUNNING state for resource "res-unhealthy-valerr"
|
|
And a run_command that returns a non-zero exit code
|
|
And get_lifecycle_tracker always returns RUNNING state
|
|
And transition_state raises ValueError on call
|
|
When I run the health check loop for one iteration
|
|
Then the ValueError is caught and a debug message is logged for "res-unhealthy-valerr"
|
|
|
|
Scenario: Probe exception breaks when state changed concurrently before transition
|
|
Given a tracker in RUNNING state for resource "res-exc-break"
|
|
And a run_command that raises an OSError
|
|
And get_lifecycle_tracker returns STOPPED state on re-read under lock
|
|
When I run the health check loop for one iteration
|
|
Then the loop exits via the TOCTOU guard break for probe exception
|
|
|
|
Scenario: Probe exception catches ValueError from transition_state
|
|
Given a tracker in RUNNING state for resource "res-exc-valerr"
|
|
And a run_command that raises an OSError
|
|
And get_lifecycle_tracker always returns RUNNING state
|
|
And transition_state raises ValueError on call
|
|
When I run the health check loop for one iteration
|
|
Then the ValueError is caught and a debug message is logged for "res-exc-valerr"
|