CoreRasurae
007af498b8
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 17s
CI / helm (pull_request) Successful in 33s
CI / lint (pull_request) Successful in 3m42s
CI / security (pull_request) Successful in 4m8s
CI / quality (pull_request) Successful in 4m9s
CI / typecheck (pull_request) Successful in 4m20s
CI / integration_tests (pull_request) Successful in 7m2s
CI / unit_tests (pull_request) Successful in 7m55s
CI / docker (pull_request) Successful in 1m19s
CI / coverage (pull_request) Successful in 8m46s
CI / e2e_tests (pull_request) Successful in 16m1s
CI / status-check (pull_request) Successful in 1s
CI / build (push) Successful in 17s
CI / helm (push) Successful in 22s
CI / quality (push) Successful in 31s
CI / lint (push) Successful in 3m28s
CI / typecheck (push) Successful in 3m54s
CI / benchmark-regression (push) Has been skipped
CI / security (push) Successful in 4m5s
CI / integration_tests (push) Successful in 6m13s
CI / unit_tests (push) Successful in 6m28s
CI / docker (push) Successful in 1m34s
CI / coverage (push) Successful in 12m5s
CI / e2e_tests (push) Successful in 18m47s
CI / status-check (push) Successful in 1s
CI / benchmark-publish (push) Successful in 28m0s
CI / benchmark-regression (pull_request) Successful in 59m48s
Renamed all 11 task-type confidence threshold fields in AutomationProfile from phase-transition semantics to spec-defined task-type semantics. Updated all 8 built-in profiles, CLI formatting, YAML schema, services, and all Behave/Robot tests referencing the old field names. Post-review fixes: - Fixed 24 stale old field names in M6 fixture files (automation_profiles.json, autonomy_guardrails.json) - Added model_validator(mode='before') to detect legacy field names and raise actionable ValueError with rename mapping - Added semantic bridge comments in PlanLifecycleService mapping task-type thresholds to phase-transition gates - Added threshold_field to structured log messages for observability - Restored categorised CLI automation-profile show output to match spec (Phase Transitions / Decision Automation / Self-Repair / Execution Controls) instead of flat list - Added missing access_network field to spec show output examples (Rich, Plain, JSON, YAML variants) - Aligned ADR-017 profile fields table to all 11 fields with descriptions matching spec Automatable Tasks table - Aligned automation_profiles.md threshold descriptions with spec - Added spec section references in phase_reversion.md, error_recovery.md, and plan_execute.md for field naming context - Extended repository roundtrip test to assert all 11 threshold fields - Fixed benchmark _make_profile() passing safety fields as top-level kwargs instead of via SafetyProfile sub-model (incompatible with extra="forbid") - Aligned CLI JSON/YAML output structure for automation-profile show with the specification grouped format (phase_transitions, decision_automation, self_repair, execution_controls) - Moved safety boolean fields into the Execution Controls section of Rich output per spec examples - Reverted auto profile description to "Fully automatic except apply" per specification (line 16703, line 28406) - Improved bridge comments in test steps with semantic context for threshold-to-gate mappings ISSUES CLOSED: #902
77 lines
3.9 KiB
Gherkin
77 lines
3.9 KiB
Gherkin
Feature: Automation Profile CLI coverage boost
|
|
As a developer
|
|
I want to cover remaining branches in automation_profile CLI module
|
|
So that coverage reaches the 97% threshold
|
|
|
|
Background:
|
|
Given an automation profile coverage CLI runner
|
|
|
|
Scenario: Delete from in-memory repo when profile does not exist
|
|
When I delete a non-existent profile from the in-memory repo
|
|
Then a NotFoundError should be raised from the repo
|
|
|
|
Scenario: Threshold summary returns compact string
|
|
When I call threshold summary on a built-in profile
|
|
Then the threshold summary should contain strategize execute and apply values
|
|
|
|
Scenario: Guarded profile config passes docs schema and model
|
|
When I validate a guarded profile config against docs schema and model
|
|
Then the guarded profile config should pass schema and model validation
|
|
|
|
Scenario: Add profile with non-dict YAML content aborts
|
|
Given a YAML file containing a list instead of a dict
|
|
When I run automation-profile add with that non-dict YAML file
|
|
Then the automation-profile coverage command should abort
|
|
And the automation-profile coverage output should contain "mapping"
|
|
|
|
Scenario: Add profile triggers FileNotFoundError from open
|
|
When I run automation-profile add with a config that triggers FileNotFoundError
|
|
Then the automation-profile coverage command should abort
|
|
|
|
Scenario: Add profile triggers ValidationError from service
|
|
Given a YAML file that triggers a ValidationError from the service
|
|
When I run automation-profile add with that validation-error YAML file
|
|
Then the automation-profile coverage command should abort
|
|
And the automation-profile coverage output should contain "Validation"
|
|
|
|
Scenario: Add profile triggers CleverAgentsError from service
|
|
Given a YAML file that triggers a CleverAgentsError from the service
|
|
When I run automation-profile add with that cleveragents-error YAML file
|
|
Then the automation-profile coverage command should abort
|
|
And the automation-profile coverage output should contain "Error"
|
|
|
|
Scenario: Remove profile without --yes prompts confirmation and user declines
|
|
Given a custom coverage profile "acme/removable" has been added
|
|
When I run automation-profile remove "acme/removable" without --yes and decline
|
|
Then the automation-profile coverage output should contain "Cancelled"
|
|
|
|
Scenario: Remove profile without --yes prompts confirmation and user confirms
|
|
Given a custom coverage profile "acme/removable2" has been added
|
|
When I run automation-profile remove "acme/removable2" without --yes and confirm
|
|
Then the automation-profile coverage remove should succeed
|
|
And the automation-profile coverage output should contain "removed"
|
|
|
|
Scenario: Remove profile triggers ValidationError
|
|
Given a custom coverage profile "acme/valerr" has been added
|
|
When I run automation-profile remove "acme/valerr" with validation error
|
|
Then the automation-profile coverage command should abort
|
|
And the automation-profile coverage output should contain "Validation"
|
|
|
|
Scenario: Remove profile triggers CleverAgentsError
|
|
Given a custom coverage profile "acme/caerr" has been added
|
|
When I run automation-profile remove "acme/caerr" with CleverAgentsError
|
|
Then the automation-profile coverage command should abort
|
|
And the automation-profile coverage output should contain "Error"
|
|
|
|
Scenario: List profiles triggers CleverAgentsError
|
|
When I run automation-profile list with a CleverAgentsError from service
|
|
Then the automation-profile coverage command should abort
|
|
|
|
Scenario: Show profile triggers CleverAgentsError
|
|
When I run automation-profile show with a CleverAgentsError from service
|
|
Then the automation-profile coverage command should abort
|
|
|
|
Scenario: Emit automation level deprecation warning directly
|
|
When I call emit_automation_level_deprecation_warning
|
|
Then a DeprecationWarning should be emitted
|