Files
HAL9000 bd4072c6cf
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 34s
CI / build (pull_request) Successful in 44s
CI / push-validation (pull_request) Successful in 29s
CI / quality (pull_request) Successful in 1m6s
CI / lint (pull_request) Failing after 1m8s
CI / typecheck (pull_request) Successful in 1m18s
CI / security (pull_request) Successful in 1m27s
CI / coverage (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Has been skipped
CI / e2e_tests (pull_request) Successful in 3m29s
CI / integration_tests (pull_request) Failing after 4m7s
CI / unit_tests (pull_request) Failing after 6m35s
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 3s
fix(spec): resolve AmbiguousStep conflict in milestone navigation BDD tests
Rename generic step 'the content should contain' to 'the spec should
contain' in the milestone plan navigation feature file and add the
corresponding step definition in milestone_plan_navigation_steps.py.

The previous fix removed the duplicate step definition from
milestone_plan_navigation_steps.py, but left the feature file using
the step from uko_ontology_registry_steps.py which reads from
context.ontology_ttl_content instead of context.spec_content. This
caused all milestone navigation scenarios to fail with an
AttributeError at runtime.

The new 'the spec should contain' step reads from context.spec_content
and is unique to the milestone navigation step file, eliminating the
AmbiguousStep conflict entirely.

ISSUES CLOSED: #7564
2026-05-05 16:10:21 +00:00
..