TEST-INFRA: [coverage-gaps] Add coverage for UKO Layer 3 vocabulary insertions #5397

Open
opened 2026-04-09 06:19:35 +00:00 by HAL9000 · 2 comments
Owner

Metadata

  • Branch: test/uko-layer3-vocabulary-insertion-coverage
  • Commit Message: test(acms): add Behave scenarios for UKO Layer 3 vocabulary detail level map insertions
  • Milestone: (backlog — see note below)
  • Parent Epic: #4943

Description

The features/acms/uko_layer3_vocabularies.feature file contains tests for the Python, TypeScript, Rust, and Java vocabularies. However, it only tests the vocabulary structure (namespace, prefix, layer, classes, properties, etc.) and the DetailLevelMap. It does not contain any tests for the specific logic of each vocabulary.

The layer3 Python files (layer3_ts.py, layer3_rs.py, layer3_py.py, layer3_java.py) define the specific vocabularies for each language. Each of these files contains a build_detail_level_map call with specific insertions for that language. These insertions are not tested in the uko_layer3_vocabularies.feature file.

This represents a coverage gap, as the specific logic of the Layer 3 vocabularies is not being tested.

Proposed Solution

Add new scenarios to the uko_layer3_vocabularies.feature file to test the build_detail_level_map function with the specific insertions of each language.

For example, for the Python vocabulary, a new scenario should be added to verify that the DECORATED_SIGNATURES, TYPE_STUBS, and WITH_TESTS levels are correctly inserted into the DetailLevelMap.

Subtasks

  • Audit layer3_py.py, layer3_ts.py, layer3_rs.py, and layer3_java.py for all build_detail_level_map insertions
  • Add Behave scenarios to features/acms/uko_layer3_vocabularies.feature for Python vocabulary DetailLevelMap insertions
  • Add Behave scenarios for TypeScript vocabulary DetailLevelMap insertions
  • Add Behave scenarios for Rust vocabulary DetailLevelMap insertions
  • Add Behave scenarios for Java vocabulary DetailLevelMap insertions
  • Verify nox -e unit_tests passes with new scenarios
  • Verify nox -e coverage_report shows >= 97% coverage for the affected modules

Definition of Done

  • All build_detail_level_map insertions in each language's Layer 3 vocabulary file are covered by at least one Behave scenario
  • nox -e unit_tests passes with no failures
  • nox -e coverage_report shows >= 97% coverage
  • nox -e lint and nox -e typecheck pass without errors
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone v3.5.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.


Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: new-issue-creator

## Metadata - **Branch**: `test/uko-layer3-vocabulary-insertion-coverage` - **Commit Message**: `test(acms): add Behave scenarios for UKO Layer 3 vocabulary detail level map insertions` - **Milestone**: *(backlog — see note below)* - **Parent Epic**: #4943 ## Description The `features/acms/uko_layer3_vocabularies.feature` file contains tests for the Python, TypeScript, Rust, and Java vocabularies. However, it only tests the vocabulary structure (namespace, prefix, layer, classes, properties, etc.) and the `DetailLevelMap`. It does not contain any tests for the specific logic of each vocabulary. The `layer3` Python files (`layer3_ts.py`, `layer3_rs.py`, `layer3_py.py`, `layer3_java.py`) define the specific vocabularies for each language. Each of these files contains a `build_detail_level_map` call with specific insertions for that language. These insertions are not tested in the `uko_layer3_vocabularies.feature` file. This represents a coverage gap, as the specific logic of the Layer 3 vocabularies is not being tested. ## Proposed Solution Add new scenarios to the `uko_layer3_vocabularies.feature` file to test the `build_detail_level_map` function with the specific insertions of each language. For example, for the Python vocabulary, a new scenario should be added to verify that the `DECORATED_SIGNATURES`, `TYPE_STUBS`, and `WITH_TESTS` levels are correctly inserted into the `DetailLevelMap`. ## Subtasks - [ ] Audit `layer3_py.py`, `layer3_ts.py`, `layer3_rs.py`, and `layer3_java.py` for all `build_detail_level_map` insertions - [ ] Add Behave scenarios to `features/acms/uko_layer3_vocabularies.feature` for Python vocabulary `DetailLevelMap` insertions - [ ] Add Behave scenarios for TypeScript vocabulary `DetailLevelMap` insertions - [ ] Add Behave scenarios for Rust vocabulary `DetailLevelMap` insertions - [ ] Add Behave scenarios for Java vocabulary `DetailLevelMap` insertions - [ ] Verify `nox -e unit_tests` passes with new scenarios - [ ] Verify `nox -e coverage_report` shows >= 97% coverage for the affected modules ## Definition of Done - [ ] All `build_detail_level_map` insertions in each language's Layer 3 vocabulary file are covered by at least one Behave scenario - [ ] `nox -e unit_tests` passes with no failures - [ ] `nox -e coverage_report` shows >= 97% coverage - [ ] `nox -e lint` and `nox -e typecheck` pass without errors - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.5.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator
Author
Owner

Label compliance fix applied:

  • Added missing labels to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog — Coverage for UKO Layer 3 vocabulary insertions is a coverage gap that should be addressed but doesn't block any active milestone.
  • Milestone: None (backlog — as noted in issue body)
  • Story Points: 3 — M — Adding Behave scenarios for 4 language vocabularies (Python, TypeScript, Rust, Java) with verification, 4-8 hours.
  • MoSCoW: MoSCoW/Should have — Maintaining >=97% coverage is a hard project requirement. This coverage gap should be closed to maintain the threshold.
  • Parent Epic: #4943 (as noted in issue body)

Valid coverage improvement issue. The >=97% coverage requirement makes this a Should Have — coverage gaps must be addressed.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — Coverage for UKO Layer 3 vocabulary insertions is a coverage gap that should be addressed but doesn't block any active milestone. - **Milestone**: None (backlog — as noted in issue body) - **Story Points**: 3 — M — Adding Behave scenarios for 4 language vocabularies (Python, TypeScript, Rust, Java) with verification, 4-8 hours. - **MoSCoW**: MoSCoW/Should have — Maintaining >=97% coverage is a hard project requirement. This coverage gap should be closed to maintain the threshold. - **Parent Epic**: #4943 (as noted in issue body) Valid coverage improvement issue. The >=97% coverage requirement makes this a Should Have — coverage gaps must be addressed. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#5397
No description provided.