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
40 lines
2.1 KiB
Gherkin
40 lines
2.1 KiB
Gherkin
Feature: ProjectService Coverage Boost
|
|
Additional scenarios that exercise previously uncovered code paths
|
|
in the project_service module (lines 29, 248-249, 270-271, 465-466,
|
|
483-494).
|
|
|
|
Background:
|
|
Given the project service coverage module is imported
|
|
|
|
Scenario: get_current_project returns None when Project constructor fails with name file present
|
|
Given a temporary directory tree with .cleveragents and a project.name file
|
|
And the database returns no project for the stored name
|
|
And the Project constructor is patched to raise an exception
|
|
When I call get_current_project from inside the temp directory
|
|
Then get_current_project should return None
|
|
|
|
Scenario: get_current_project returns None when Project constructor fails for legacy project
|
|
Given a temporary directory tree with .cleveragents but no project.name file
|
|
And the Project constructor is patched to raise an exception
|
|
When I call get_current_project from inside the temp directory
|
|
Then get_current_project should return None
|
|
|
|
Scenario: get_project_filters raises NotFoundError when project not in database
|
|
Given a ProjectService backed by an in-memory database
|
|
And the database contains no project named "ghost-project"
|
|
When I call get_project_filters with a project named "ghost-project"
|
|
Then a NotFoundError should be raised with message "Project not found"
|
|
|
|
Scenario: delete_project emits ENTITY_DELETED event via event bus
|
|
Given a ProjectService backed by an in-memory database with an event bus
|
|
And a project named "event-project" exists in the database
|
|
When I call delete_project on "event-project"
|
|
Then the event bus should have received an ENTITY_DELETED event for "event-project"
|
|
|
|
Scenario: delete_project swallows event bus exception and logs warning
|
|
Given a ProjectService backed by an in-memory database with a failing event bus
|
|
And a project named "fail-event-project" exists in the database
|
|
When I call delete_project on "fail-event-project"
|
|
Then no exception should propagate from delete_project
|
|
And a warning about audit_emit_failed should have been logged
|