Files
cleveragents-core/robot/cli_lifecycle_e2e.robot
T
HAL9000 afe89964df
CI / push-validation (pull_request) Successful in 26s
CI / helm (pull_request) Successful in 50s
CI / lint (pull_request) Successful in 52s
CI / build (pull_request) Successful in 51s
CI / quality (pull_request) Successful in 52s
CI / security (pull_request) Successful in 1m15s
CI / typecheck (pull_request) Successful in 1m35s
CI / unit_tests (pull_request) Successful in 5m25s
CI / docker (pull_request) Successful in 1m34s
CI / integration_tests (pull_request) Failing after 10m26s
CI / coverage (pull_request) Failing after 18m51s
CI / status-check (pull_request) Has been cancelled
chore(tests): remove stale tdd_expected_fail tags from tests now passing on master
The tdd_expected_fail listener (robot/tdd_expected_fail_listener.py and
features/environment.py) inverts test results: a test tagged
@tdd_expected_fail that PASSES is forced to FAIL with the message
"Bug appears to be fixed. Remove the tdd_expected_fail tag…".

After rebasing onto master, 22 scenarios across 11 files were triggering
that forced-failure path because the underlying bugs (#4199, #4201,
#4202, #4203, #4205, #4206, #4243, #4252, #4301, #4303, #4304) have
been fixed on master but the @tdd_expected_fail tags were never removed.
This commit removes the stale tag (keeping @tdd_issue and
@tdd_issue_<N> for traceability, per the master-side pattern in
robot/tdd_skill_add_regression.robot:9 "tag removed after bug fix").

Files touched (lines: where the stale tag was):
  features/plan_cli_spec_alignment.feature (121, 128, 136)
  robot/a2a_facade.robot (40)
  robot/actor_cli_show.robot (13, 30)
  robot/actor_configuration.robot (8)
  robot/actor_context_export_import.robot (20, 71, 92)
  robot/cli_extensions.robot (61)
  robot/cli_formats.robot (14, 23, 30, 48, 57, 85)
  robot/cli_lifecycle_e2e.robot (77, 87)
  robot/config_project_scope.robot (37)
  robot/config_resolution.robot (13)
  robot/container_tool_exec.robot (137)

Verified locally: targeted unit_tests run on
features/plan_cli_spec_alignment.feature now passes 20/20 (was 17/20
with 3 scenarios forced-failed by the inversion).

ISSUES CLOSED: #3677
2026-06-03 03:22:59 -04:00

94 lines
4.2 KiB
Plaintext

*** Settings ***
Documentation End-to-end smoke tests for action -> plan -> execute -> apply lifecycle via CLI helpers
Resource ${CURDIR}/common.resource
Suite Setup Setup Test Environment
Suite Teardown Cleanup Test Environment
*** Variables ***
${HELPER} ${CURDIR}/helper_cli_lifecycle_e2e.py
*** Test Cases ***
Action Create From Config Via CLI
[Documentation] Create an action from a YAML config file and verify it succeeds
${result}= Run Process ${PYTHON} ${HELPER} action-create cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-action-create-ok
Plan Use Creates Plan In Strategize Phase
[Documentation] Use an action to create a plan in Strategize phase
${result}= Run Process ${PYTHON} ${HELPER} plan-use cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-use-ok
Plan Execute Transitions To Execute Phase
[Documentation] Execute a plan, transitioning from Strategize to Execute
${result}= Run Process ${PYTHON} ${HELPER} plan-execute cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-execute-ok
Plan Lifecycle Apply Transitions To Apply Phase
[Documentation] Apply a plan, transitioning from Execute to Apply
${result}= Run Process ${PYTHON} ${HELPER} plan-apply cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-apply-ok
Plan Status Shows Plan Details
[Documentation] Verify plan status renders plan details
${result}= Run Process ${PYTHON} ${HELPER} plan-status cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-status-ok
Plan Cancel Cancels Non-Terminal Plan
[Documentation] Cancel a non-terminal plan
${result}= Run Process ${PYTHON} ${HELPER} plan-cancel cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-cancel-ok
Full Lifecycle Action To Apply
[Documentation] End-to-end: create action, use it, execute, apply
${result}= Run Process ${PYTHON} ${HELPER} full-lifecycle cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-full-e2e-ok
Plan Lifecycle List Shows Plans
[Documentation] Verify list renders plan table
${result}= Run Process ${PYTHON} ${HELPER} plan-list cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-list-ok
Plan List Namespace Option Filters By Namespace
[Documentation] Verify agents plan list --namespace myteam returns only plans in that namespace
[Tags] tdd_issue tdd_issue_4301
${result}= Run Process ${PYTHON} ${HELPER} plan-list-namespace cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-list-namespace-ok
Plan List Short Namespace Option Works
[Documentation] Verify agents plan list -n myteam short-form alias works correctly
[Tags] tdd_issue tdd_issue_4301
${result}= Run Process ${PYTHON} ${HELPER} plan-list-namespace-short cwd=${WORKSPACE}
Log ${result.stdout}
Log ${result.stderr}
Should Be Equal As Integers ${result.rc} 0
Should Contain ${result.stdout} cli-lifecycle-plan-list-namespace-short-ok