HAL9000
1297f093c3
CI / lint (pull_request) Successful in 56s
CI / typecheck (pull_request) Successful in 57s
CI / security (pull_request) Successful in 1m5s
CI / quality (pull_request) Successful in 51s
CI / push-validation (pull_request) Successful in 44s
CI / build (pull_request) Successful in 1m2s
CI / helm (pull_request) Successful in 1m8s
CI / unit_tests (pull_request) Successful in 4m40s
CI / docker (pull_request) Successful in 1m37s
CI / integration_tests (pull_request) Successful in 8m16s
CI / coverage (pull_request) Successful in 9m9s
CI / status-check (pull_request) Successful in 3s
The CREATE_TRACKING_ISSUE and CREATE_ANNOUNCEMENT_ISSUE scenarios in
features/automation_tracking_mandatory_labels.feature used Behave tables
without explicit column headers, but the step implementations index rows
by row["name"] / row["value"]. Behave was treating the first data row as
the heading row, raising KeyError('"value" is not a row heading') and
erroring both scenarios.
Add the missing `| name | value |` header row to both tables so the
indexed access works as written. Also apply `ruff format` to the steps
module to satisfy the lint/format gate (trailing commas in dict literals
and parenthesised long assert messages).
ISSUES CLOSED: #3105
38 lines
1.9 KiB
Gherkin
38 lines
1.9 KiB
Gherkin
Feature: Automation Tracking Manager applies mandatory labels to tracking issues
|
|
|
|
Background:
|
|
Given a Forgejo repository is available
|
|
And the automation-tracking-manager agent is configured
|
|
|
|
Scenario: CREATE_TRACKING_ISSUE applies mandatory labels to status tracking issues
|
|
When the automation-tracking-manager creates a status tracking issue with:
|
|
| name | value |
|
|
| agent-prefix | AUTO-TEST-SUP |
|
|
| tracking-type | Test Status |
|
|
| body | Test tracking issue body |
|
|
| sleep-interval-default | 60 |
|
|
Then the created tracking issue should have the following mandatory labels:
|
|
| label |
|
|
| Automation Tracking |
|
|
| Priority/Medium |
|
|
And the issue title should match the pattern "[AUTO-TEST-SUP] Status: Test Status (Cycle N)"
|
|
|
|
Scenario: CREATE_ANNOUNCEMENT_ISSUE applies mandatory labels to announcement issues
|
|
When the automation-tracking-manager creates an announcement issue with:
|
|
| name | value |
|
|
| agent-prefix | AUTO-TEST-SUP |
|
|
| message | Test Announcement |
|
|
| priority | Priority/Critical |
|
|
| body | Test announcement body |
|
|
Then the created announcement issue should have the following mandatory labels:
|
|
| label |
|
|
| Automation Tracking |
|
|
| Priority/Critical |
|
|
And the issue title should match the pattern "[AUTO-TEST-SUP] Announce: Test Announcement"
|
|
|
|
Scenario: CREATE_TRACKING_ISSUE fails gracefully if labels cannot be applied
|
|
When the automation-tracking-manager attempts to create a status tracking issue
|
|
And the forgejo-label-manager fails to apply labels
|
|
Then the created issue should be deleted
|
|
And an error message should be returned explaining the label application failure
|