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
55 lines
2.6 KiB
Gherkin
55 lines
2.6 KiB
Gherkin
Feature: Cloud Handler Coverage
|
|
Scenarios that exercise previously uncovered code paths in the
|
|
cloud resource handler module (resource/handlers/cloud.py).
|
|
|
|
Background:
|
|
Given the cloud handler module is imported
|
|
|
|
# --- extract_provider: hierarchical prefix matching (lines 249-251) ---
|
|
|
|
Scenario: extract_provider returns aws for hierarchical aws-account type
|
|
When I extract the provider from type name "aws-account"
|
|
Then the extracted provider should be "aws"
|
|
|
|
Scenario: extract_provider returns gcp for hierarchical gcp-project type
|
|
When I extract the provider from type name "gcp-project"
|
|
Then the extracted provider should be "gcp"
|
|
|
|
Scenario: extract_provider returns azure for hierarchical azure-vm type
|
|
When I extract the provider from type name "azure-vm"
|
|
Then the extracted provider should be "azure"
|
|
|
|
# --- extract_provider: returns None for generic cloud-* (line 253) ---
|
|
|
|
Scenario: extract_provider returns None for generic cloud base type
|
|
When I extract the provider from type name "cloud-generic"
|
|
Then the extracted provider should be None
|
|
|
|
# --- resolve_credentials: explicit properties take priority (lines 302-303) ---
|
|
|
|
Scenario: resolve_credentials uses explicit properties over env vars
|
|
Given chcov the environment variable "AWS_ACCESS_KEY_ID" is set to "env-key"
|
|
When I resolve credentials for provider "aws" with explicit property "access-key-id" set to "explicit-key"
|
|
Then the resolved credential "access-key-id" should be "explicit-key"
|
|
|
|
# --- validate_credentials: unknown provider (lines 331-333) ---
|
|
|
|
Scenario: validate_credentials returns errors for unknown provider
|
|
When I validate credentials for unknown provider "digitalocean"
|
|
Then the validation errors should mention unknown provider "digitalocean"
|
|
|
|
# --- CloudResourceHandler.resolve: generic cloud-* type (lines 420-423) ---
|
|
|
|
Scenario: CloudResourceHandler.resolve raises NotImplementedError for generic cloud type
|
|
Given I have a cloud resource with type "cloud-storage"
|
|
When I call resolve on the cloud resource handler
|
|
Then a NotImplementedError should be raised mentioning generic type "cloud-storage"
|
|
|
|
# --- CloudResourceHandler.resolve: unknown provider mapping (lines 428-431) ---
|
|
|
|
Scenario: CloudResourceHandler.resolve raises ValueError for unknown provider mapping
|
|
Given I have a cloud resource with type "fake-cloud-type"
|
|
And extract_provider is mocked to return "digitalocean"
|
|
When I call resolve on the cloud resource handler expecting a ValueError
|
|
Then a ValueError should be raised mentioning unknown provider "digitalocean"
|