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
27 lines
1.5 KiB
Gherkin
27 lines
1.5 KiB
Gherkin
Feature: Actor Service Coverage Boost
|
|
Additional scenarios that exercise previously uncovered code paths
|
|
in the actor_service module (lines 106-107, 150-157, 161-162).
|
|
|
|
Background:
|
|
Given the actsvc coverage module is imported
|
|
|
|
Scenario: upsert_actor rejects non-local prefix when is_built_in is False
|
|
Given I have an actsvc service with a mock unit of work
|
|
And the actsvc repo has no existing actor for "openai/gpt4"
|
|
When I call actsvc upsert_actor with name "openai/gpt4" provider "openai" model "gpt4" and is_built_in False
|
|
Then an actsvc ValidationError should be raised with message "Custom actors must use the 'local/<id>' naming pattern"
|
|
|
|
Scenario: remove_actor emits ENTITY_DELETED event via event bus on success
|
|
Given I have an actsvc service with a working event bus
|
|
And the actsvc repo has an existing local actor named "local/deletable"
|
|
When I call actsvc remove_actor with name "local/deletable"
|
|
Then the actsvc actor should be deleted successfully
|
|
And the actsvc event bus should have received an ENTITY_DELETED event for "local/deletable"
|
|
|
|
Scenario: remove_actor logs warning when event bus emit raises an exception
|
|
Given I have an actsvc service with a failing event bus
|
|
And the actsvc repo has an existing local actor named "local/failing-emit"
|
|
When I call actsvc remove_actor with name "local/failing-emit"
|
|
Then the actsvc actor should be deleted despite the emit failure
|
|
And the actsvc warning about audit_emit_failed should have been logged
|