hurui200320
2005b8ef82
CI / push-validation (push) Successful in 18s
CI / build (push) Successful in 19s
CI / helm (push) Successful in 24s
CI / lint (push) Successful in 29s
CI / security (push) Successful in 1m11s
CI / e2e_tests (push) Successful in 2m56s
CI / quality (push) Successful in 3m40s
CI / typecheck (push) Successful in 3m59s
CI / integration_tests (push) Successful in 4m3s
CI / unit_tests (push) Successful in 4m55s
CI / docker (push) Successful in 10s
CI / coverage (push) Successful in 10m44s
CI / status-check (push) Successful in 1s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Successful in 1h13m28s
## Summary Replaces all 234 bare `@skip` occurrences across 82 Behave feature files with the correct TDD issue-capture tagging system described in CONTRIBUTING.md § Bug Fix Workflow. Previously, the noxfile ran Behave with `--tags=not @skip`, silently excluding all `@skip`-tagged scenarios from every CI run. These tests never ran, never inverted results via the `@tdd_expected_fail` mechanism, and never contributed to coverage — defeating the purpose of TDD issue-capture testing. Every `@skip` occurrence had a commented-out hint line immediately above it showing the intended proper tags (e.g., `# @tdd_issue @tdd_issue_4272 @tdd_expected_fail @skip`), confirming they were all intended for conversion. ## Changes ### Mechanical conversion (234 replacements across 82 files) - Extracted the proper TDD tags from the comment hint above each `@skip` line, removed `@skip` from the tag set, and replaced the `@skip` line with those tags. - Removed the now-redundant comment hint lines alongside each replacement. ### Bug-fixed scenarios — `@tdd_expected_fail` removed (84 scenarios) - After conversion, ran `nox -s unit_tests` to identify which newly-enabled `@tdd_expected_fail` scenarios now **pass** (their referenced bugs have already been fixed). Removed `@tdd_expected_fail` from those 84 scenarios and their corresponding feature-level tags, leaving only the permanent `@tdd_issue @tdd_issue_<N>` regression-guard tags. - Affected features include: `tdd_tool_runner_env_precedence`, `tdd_automation_profile_session_leak`, `tls_certificate_check`, `project_create_persist`, `resource_type_bootstrap_*`, and 18 others. ### Noxfile cleanup - Removed all four `--tags=not @skip` arguments from `noxfile.py` (unit_tests and coverage sessions). With zero `@skip` tags remaining in the codebase, this filter was dead code and its presence would mislead future maintainers into thinking `@skip` is still a supported escape mechanism. ### Regression guard files - Split the regression guards into two focused files: - `tdd_regression_guards_exec_env.feature` for bug #4281 (exec-env precedence) - `tdd_regression_guards_session_list.feature` for bug #4271 (session list summary) - Each file carries only its own `@tdd_issue` tags at the feature level, avoiding cross-contamination via Behave tag inheritance. The `Background` step (`session-list-summary mock`) only appears in the session-list file where it is actually needed. ### Duplicate tag cleanup - Removed duplicate `@tdd_issue @tdd_issue_4287` tag lines in `tdd_skill_add_regression.feature` (lines 20 and 29). ### Inline comment for retained `@tdd_expected_fail` - Added inline comment in `ci_workflow_validation.feature:134` explaining why this specific #4227 scenario retains `@tdd_expected_fail` despite #4227 being closed (CI YAML does not encode threshold as a machine-readable value). ### Known edge cases — `@tdd_expected_fail` retained (closed issues, fix on master, scenarios still fail) The following issues are **closed** and their fixes **are on master**, but the specific test assertions still fail because the fixes address other aspects of the bugs. The `@tdd_expected_fail` tags are functionally correct and must remain until the specific scenario assertions pass: - `tdd_exec_env_resolution_precedence.feature` — bug #1080 (closed 2026-03-31). The precedence-level-2-vs-4 scenario still fails. - `session_list_summary_dedup.feature` — bug #3046 (closed 2026-04-05). The dedup-consistency scenarios still fail. - `actor_add_update_enforcement.feature` — bug #2609 (closed 2026-04-05). The enforcement scenarios still fail. - `ci_workflow_validation.feature:134` — #4227 (closed 2026-04-08). The CI YAML threshold assertion still fails. ## Verification - `grep -r "@skip" features/ --include="*.feature"` → **zero results** ✓ - `grep -n "tags=not @skip" noxfile.py` → **zero results** ✓ - `nox -s unit_tests` → **629 features passed, 0 failed** ✓ (up from ~545 before this PR) - CI all green (coverage ≥ 97%) ✓ - Integration tests (Robot Framework) do not use `@skip` — confirmed no action needed ✓ - E2E tests (Robot Framework) do not use `@skip` — confirmed no action needed ✓ - `CHANGELOG.md` updated with entry for this change ✓ - `CONTRIBUTORS.md` — Rui Hu already listed ✓ ## Issues Addressed Closes #7025 Co-authored-by: CleverThis <hal9000@cleverthis.com> Reviewed-on: #7221 Reviewed-by: HAL 9000 <HAL9000@cleverthis.com> Reviewed-by: HAL9001 <hal9001@cleverthis.com> Co-authored-by: Rui Hu <rui.hu@cleverthis.com> Co-committed-by: Rui Hu <rui.hu@cleverthis.com>
118 lines
5.9 KiB
Gherkin
118 lines
5.9 KiB
Gherkin
Feature: Database models coverage round 2
|
|
Additional Behave scenarios targeting uncovered lines in
|
|
src/cleveragents/infrastructure/database/models.py identified
|
|
from build/coverage.xml.
|
|
|
|
# ---------------------------------------------------------------
|
|
# LifecycleActionModel — safety_profile round-trip (lines 376, 427)
|
|
# ---------------------------------------------------------------
|
|
|
|
Scenario: LifecycleActionModel to_domain deserializes safety_profile_json
|
|
Given a LifecycleActionModel with safety_profile_json populated
|
|
When I convert the action model to domain via to_domain
|
|
Then the domain action has a non-null safety_profile object
|
|
|
|
Scenario: LifecycleActionModel from_domain serializes safety_profile
|
|
Given an Action domain object with a SafetyProfile attached
|
|
When I convert the action to a model via from_domain
|
|
Then the model safety_profile_json contains serialized SafetyProfile data
|
|
|
|
# ---------------------------------------------------------------
|
|
# LifecycleActionModel — string arg_type/requirement (lines 466, 469)
|
|
# ---------------------------------------------------------------
|
|
|
|
Scenario: LifecycleActionModel from_domain with plain-string arg_type and requirement
|
|
Given an Action domain object whose arguments have plain-string arg_type and requirement
|
|
When I convert that action to a model via from_domain
|
|
Then the model argument rows use the plain-string values directly
|
|
|
|
# ---------------------------------------------------------------
|
|
# LifecyclePlanModel — string processing_state (line 882)
|
|
# ---------------------------------------------------------------
|
|
|
|
@tdd_issue @tdd_issue_4245 @tdd_expected_fail
|
|
Scenario: LifecyclePlanModel from_domain with string processing_state
|
|
Given a Plan domain object whose processing_state is a plain string
|
|
When I convert the plan to a model via from_domain
|
|
Then the model processing_state equals the plain string value
|
|
|
|
# ---------------------------------------------------------------
|
|
# LifecyclePlanModel — automation_profile serialization (line 890)
|
|
# ---------------------------------------------------------------
|
|
|
|
@tdd_issue @tdd_issue_4245 @tdd_expected_fail
|
|
Scenario: LifecyclePlanModel from_domain serializes automation_profile
|
|
Given a Plan domain object with a non-null automation_profile
|
|
When I convert the plan to a model via from_domain
|
|
Then the model automation_profile column contains JSON with profile_name
|
|
|
|
# ---------------------------------------------------------------
|
|
# LifecyclePlanModel — fallback namespace (line 906)
|
|
# ---------------------------------------------------------------
|
|
|
|
@tdd_issue @tdd_issue_4245 @tdd_expected_fail
|
|
Scenario: LifecyclePlanModel from_domain falls back to local when namespace missing
|
|
Given a Plan domain object whose namespaced_name has no namespace attribute
|
|
When I convert the plan to a model via from_domain
|
|
Then the model namespace equals "local"
|
|
|
|
# ---------------------------------------------------------------
|
|
# LifecyclePlanModel — error_details serialization (line 923)
|
|
# ---------------------------------------------------------------
|
|
|
|
@tdd_issue @tdd_issue_4245 @tdd_expected_fail
|
|
Scenario: LifecyclePlanModel from_domain serializes error_details
|
|
Given a Plan domain object with non-null error_details
|
|
When I convert the plan to a model via from_domain
|
|
Then the model error_details_json is a JSON string of the details dict
|
|
|
|
# ---------------------------------------------------------------
|
|
# SkillModel — include with overrides (line 2327)
|
|
# ---------------------------------------------------------------
|
|
|
|
Scenario: SkillModel from_domain persists include overrides
|
|
Given a Skill domain object with an include that has overrides
|
|
When I convert the skill to a model via from_domain
|
|
Then the include item_config contains the serialized overrides
|
|
|
|
# ---------------------------------------------------------------
|
|
# DecisionModel — string decision_type fallback (line 2698)
|
|
# ---------------------------------------------------------------
|
|
|
|
Scenario: DecisionModel from_domain with plain-string decision_type
|
|
Given a Decision domain object whose decision_type is a plain string
|
|
When I convert the decision to a model via from_domain
|
|
Then the model decision_type equals the plain string
|
|
|
|
# ---------------------------------------------------------------
|
|
# CheckpointModel — to_domain full path (lines 2823-2852)
|
|
# ---------------------------------------------------------------
|
|
|
|
Scenario: CheckpointModel to_domain converts all fields including metadata
|
|
Given a CheckpointModel with metadata_json containing reason and phase
|
|
When I convert the checkpoint model to domain via to_domain
|
|
Then the domain checkpoint has the correct metadata fields
|
|
|
|
Scenario: CheckpointModel to_domain handles invalid metadata_json gracefully
|
|
Given a CheckpointModel with invalid JSON in metadata_json
|
|
When I convert the checkpoint model to domain via to_domain
|
|
Then the domain checkpoint metadata is empty defaults
|
|
|
|
# ---------------------------------------------------------------
|
|
# CheckpointModel — from_domain full path (lines 2865-2879)
|
|
# ---------------------------------------------------------------
|
|
|
|
Scenario: CheckpointModel from_domain serializes all checkpoint fields
|
|
Given a Checkpoint domain object with full metadata
|
|
When I convert the checkpoint to a model via from_domain
|
|
Then the model has correct checkpoint_id plan_id and metadata_json
|
|
|
|
# ---------------------------------------------------------------
|
|
# get_session function (lines 2907-2908)
|
|
# ---------------------------------------------------------------
|
|
|
|
Scenario: get_session returns a usable SQLAlchemy session
|
|
Given an in-memory SQLAlchemy engine
|
|
When I call get_session with that engine
|
|
Then I receive a valid SQLAlchemy session object
|