cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

test(e2e): workflow example 17 — explicit container with directory mount (trusted profile) #819

Merged
hurui200320 merged 1 commits from test/e2e-wf17-explicit-container into master 2026-03-30 08:25:36 +00:00
Conversation 5 Commits 1 Files Changed 2
+459
freemo commented 2026-03-13 17:14:33 +00:00
Owner
Copy Link
Copy Source

Summary

E2E test for Specification Workflow Example 17 — Explicit Container with Directory Mount using the trusted automation profile. Exercises the full container workflow: resource registration (git-checkout + container-instance), project linking via separate link-resource calls (following spec's prescribed command sequence), execution environment setting via project context set, plan-level execution-env-priority override via plan use, and complete plan lifecycle with dynamic actor selection.

Additionally includes TDD bug-capture tests for two deferred acceptance criteria where CLI features are not yet implemented, and a regression guard for the now-fixed dual mount registration (bug #1078).

Closes #763

ISSUES CLOSED: #763

What This PR Does

  1. Registers two resource types — git-checkout for the code repo and container-instance (with --image) for the container environment.
  2. Links both resources to the project — uses separate project create then project link-resource calls for each resource, matching the spec's prescribed command sequence.
  3. Sets execution environment — project context set --execution-environment container at the project level, with best-effort persistence verification via project context show (field extraction with graceful fallback if not exposed).
  4. Overrides execution priority — plan use --execution-env-priority override (plan-level override, precedence level 1, used as a workaround since project context set does not yet support --execution-env-priority).
  5. Runs full plan lifecycle — plan use → strategize → execute → diff → lifecycle-apply → status with --automation-profile trusted.
  6. Terminal state assertion — verifies plan phase contains apply after lifecycle-apply, matching M6's Full Flow Apply Step pattern.
  7. Post-apply repository observation — captures HEAD SHA before apply and compares afterwards; logs informational warning if HEAD unchanged (LLM-driven modifications are non-deterministic).
  8. Container routing verification (best-effort) — extracts execution_environment field from plan status JSON and asserts it equals container when present; logs gap warning when absent.
  9. ULID format validation — validates plan_id matches canonical Crockford Base32 ULID pattern ^[0-9A-HJKMNP-TV-Z]{26}$.
  10. Dynamic actor selection — prefers Anthropic Claude when ANTHROPIC_API_KEY is available, falls back to openai/gpt-4o (consistent with M6 pattern).
  11. CI-safe — UUID-based unique suffix on all resource/project names, Skip If No LLM Keys guard on main test, workspace initialization via agents init --force --yes.
  12. Regression guard for dual mount registration — Bug #1078 is now fixed (--mount flag implemented). Test converted from tdd_expected_fail to permanent regression guard with tdd_issue + tdd_issue_1078 tags.
  13. TDD bug-capture tests for remaining deferred ACs (self-contained, no dependency on main test):
    • WF17 TDD Project Level Execution Env Priority Override — AC #3, tracked in #1079 (tdd_expected_fail)
    • WF17 TDD Precedence Level 2 Project Override Resolution — AC #5, tracked in #1080 (tdd_expected_fail)

Acceptance Criteria Status

AC Description Status Notes
#1 Robot Framework test suite tagged E2E ✅ Met Force Tags E2E in Settings
#2 Container-instance with dual mounts ✅ Met (regression guard) Bug #1078 fixed — --mount now on CLI. tdd_expected_fail removed, regression guard active.
#3 Project-level execution-env-priority ⏳ Deferred Flag only on plan use. TDD test added, tracked in #1079
#4 Plan executes and verifies container routing ✅ Met execution_environment field extracted from plan status JSON and asserted as container; full lifecycle completes successfully
#5 Precedence level 2 resolution ⏳ Deferred Depends on #1079. TDD test added, tracked in #1080
#6 Real LLM API keys, no mocking ✅ Met Skip If No LLM Keys guard
#7 Flexible output validation ✅ Met Phase-based assertions, not character-matching

Key Design Decisions

  • --mount now available on CLI — Bug #1078 is fixed. The resource add container-instance --mount command works. TDD test converted to regression guard.
  • --yes flag on lifecycle-apply — Required for non-interactive execution in E2E tests. All other E2E tests use this flag. Added to WF17 to match the established pattern.
  • Plan-level override (precedence level 1) as workaround, not project-level (level 2) — The spec shows --execution-env-priority override on project context set, but the CLI only implements this flag on plan use. Tracked in #1079, #1080.
  • --execution-environment accepts enum values (host/container), not resource names per spec — Known spec divergence documented inline.
  • Container routing verification via plan status JSON — The execution_environment field is extracted from plan status and asserted as container when present. If absent, a warning is logged documenting the gap.
  • project context show does not expose execution_environment — Persistence verification uses field extraction with graceful fallback.
  • Spec's prescribed command sequence for resource linking — Uses separate project create then project link-resource calls.
  • Terminal state assertion matches M6 pattern — Should Contain ${final_phase.lower()} apply.
  • Post-apply repository observation (informational) — Captures HEAD SHA before/after apply and logs delta; does not fail if HEAD unchanged.
  • TDD tests are self-contained — Each TDD test creates its own lightweight project/action, eliminating dependency on the main test's side effects.
  • Correct TDD tag format — Uses tdd_issue + tdd_issue_<N> per CONTRIBUTING.md (not tdd_bug).
  • 300s execute timeout documented — Higher than M6's 180s to account for potential container image pull overhead.
  • 20-minute test timeout — Increased from 15 minutes to accommodate cumulative command timeouts.

Manual Verification

Prerequisites

  • ANTHROPIC_API_KEY or OPENAI_API_KEY environment variable set

Commands

nox -s e2e_tests  # runs all E2E tests including WF17

What to Look For

  • Plan runs with --automation-profile trusted and --execution-env-priority override
  • Container-instance resource registered and linked to project
  • Standard lifecycle completes without error
  • plan status shows terminal apply phase and execution_environment=container
  • No Traceback or INTERNAL in any command's stderr
  • TDD tests invert correctly (fail = expected, meaning CLI gap still exists)
  • Dual mount registration regression guard passes normally
## Summary E2E test for Specification Workflow Example 17 — Explicit Container with Directory Mount using the trusted automation profile. Exercises the full container workflow: resource registration (git-checkout + container-instance), project linking via separate `link-resource` calls (following spec's prescribed command sequence), execution environment setting via project context set, plan-level execution-env-priority override via plan use, and complete plan lifecycle with dynamic actor selection. Additionally includes TDD bug-capture tests for two deferred acceptance criteria where CLI features are not yet implemented, and a regression guard for the now-fixed dual mount registration (bug #1078). Closes #763 ISSUES CLOSED: #763 ## What This PR Does 1. **Registers two resource types** — `git-checkout` for the code repo and `container-instance` (with `--image`) for the container environment. 2. **Links both resources to the project** — uses separate `project create` then `project link-resource` calls for each resource, matching the spec's prescribed command sequence. 3. **Sets execution environment** — `project context set --execution-environment container` at the project level, with best-effort persistence verification via `project context show` (field extraction with graceful fallback if not exposed). 4. **Overrides execution priority** — `plan use --execution-env-priority override` (plan-level override, precedence level 1, used as a workaround since `project context set` does not yet support `--execution-env-priority`). 5. **Runs full plan lifecycle** — `plan use` → strategize → execute → diff → lifecycle-apply → status with `--automation-profile trusted`. 6. **Terminal state assertion** — verifies plan phase contains `apply` after lifecycle-apply, matching M6's `Full Flow Apply Step` pattern. 7. **Post-apply repository observation** — captures HEAD SHA before apply and compares afterwards; logs informational warning if HEAD unchanged (LLM-driven modifications are non-deterministic). 8. **Container routing verification (best-effort)** — extracts `execution_environment` field from plan status JSON and asserts it equals `container` when present; logs gap warning when absent. 9. **ULID format validation** — validates `plan_id` matches canonical Crockford Base32 ULID pattern `^[0-9A-HJKMNP-TV-Z]{26}$`. 10. **Dynamic actor selection** — prefers Anthropic Claude when `ANTHROPIC_API_KEY` is available, falls back to `openai/gpt-4o` (consistent with M6 pattern). 11. **CI-safe** — UUID-based unique suffix on all resource/project names, `Skip If No LLM Keys` guard on main test, workspace initialization via `agents init --force --yes`. 12. **Regression guard for dual mount registration** — Bug #1078 is now fixed (`--mount` flag implemented). Test converted from `tdd_expected_fail` to permanent regression guard with `tdd_issue` + `tdd_issue_1078` tags. 13. **TDD bug-capture tests** for remaining deferred ACs (self-contained, no dependency on main test): - `WF17 TDD Project Level Execution Env Priority Override` — AC #3, tracked in #1079 (`tdd_expected_fail`) - `WF17 TDD Precedence Level 2 Project Override Resolution` — AC #5, tracked in #1080 (`tdd_expected_fail`) ## Acceptance Criteria Status | AC | Description | Status | Notes | |----|-------------|--------|-------| | #1 | Robot Framework test suite tagged `E2E` | ✅ Met | `Force Tags E2E` in Settings | | #2 | Container-instance with dual mounts | ✅ Met (regression guard) | Bug #1078 fixed — `--mount` now on CLI. `tdd_expected_fail` removed, regression guard active. | | #3 | Project-level execution-env-priority | ⏳ Deferred | Flag only on `plan use`. TDD test added, tracked in #1079 | | #4 | Plan executes and verifies container routing | ✅ Met | `execution_environment` field extracted from plan status JSON and asserted as `container`; full lifecycle completes successfully | | #5 | Precedence level 2 resolution | ⏳ Deferred | Depends on #1079. TDD test added, tracked in #1080 | | #6 | Real LLM API keys, no mocking | ✅ Met | `Skip If No LLM Keys` guard | | #7 | Flexible output validation | ✅ Met | Phase-based assertions, not character-matching | ## Key Design Decisions - **`--mount` now available on CLI** — Bug #1078 is fixed. The `resource add container-instance --mount` command works. TDD test converted to regression guard. - **`--yes` flag on `lifecycle-apply`** — Required for non-interactive execution in E2E tests. All other E2E tests use this flag. Added to WF17 to match the established pattern. - **Plan-level override (precedence level 1) as workaround, not project-level (level 2)** — The spec shows `--execution-env-priority override` on `project context set`, but the CLI only implements this flag on `plan use`. Tracked in #1079, #1080. - **`--execution-environment` accepts enum values (`host`/`container`), not resource names per spec** — Known spec divergence documented inline. - **Container routing verification via plan status JSON** — The `execution_environment` field is extracted from plan status and asserted as `container` when present. If absent, a warning is logged documenting the gap. - **`project context show` does not expose `execution_environment`** — Persistence verification uses field extraction with graceful fallback. - **Spec's prescribed command sequence for resource linking** — Uses separate `project create` then `project link-resource` calls. - **Terminal state assertion matches M6 pattern** — `Should Contain ${final_phase.lower()} apply`. - **Post-apply repository observation (informational)** — Captures HEAD SHA before/after apply and logs delta; does not fail if HEAD unchanged. - **TDD tests are self-contained** — Each TDD test creates its own lightweight project/action, eliminating dependency on the main test's side effects. - **Correct TDD tag format** — Uses `tdd_issue` + `tdd_issue_<N>` per CONTRIBUTING.md (not `tdd_bug`). - **300s execute timeout documented** — Higher than M6's 180s to account for potential container image pull overhead. - **20-minute test timeout** — Increased from 15 minutes to accommodate cumulative command timeouts. ## Manual Verification ### Prerequisites - `ANTHROPIC_API_KEY` or `OPENAI_API_KEY` environment variable set ### Commands ```bash nox -s e2e_tests # runs all E2E tests including WF17 ``` ### What to Look For - Plan runs with `--automation-profile trusted` and `--execution-env-priority override` - Container-instance resource registered and linked to project - Standard lifecycle completes without error - `plan status` shows terminal apply phase and `execution_environment=container` - No `Traceback` or `INTERNAL` in any command's stderr - TDD tests invert correctly (fail = expected, meaning CLI gap still exists) - Dual mount registration regression guard passes normally
freemo added the
State
In Review
Type
Testing
 labels 2026-03-13 17:14:39 +00:00
freemo added this to the v3.7.0 milestone 2026-03-13 17:14:40 +00:00
freemo force-pushed test/e2e-wf17-explicit-container from f82bbc85af to 2a1c15b60f 2026-03-13 17:29:01 +00:00 Compare
freemo force-pushed test/e2e-wf17-explicit-container from 2a1c15b60f to 81a1c6f7b7 2026-03-13 17:46:59 +00:00 Compare
freemo force-pushed test/e2e-wf17-explicit-container from 81a1c6f7b7 to 135891ec45 2026-03-13 18:13:15 +00:00 Compare
freemo force-pushed test/e2e-wf17-explicit-container from 135891ec45 to 097cd71c9d 2026-03-13 18:25:24 +00:00 Compare
freemo force-pushed test/e2e-wf17-explicit-container from 097cd71c9d to 03e3481154 2026-03-13 23:19:52 +00:00 Compare
freemo added the
Priority
Medium
 label 2026-03-14 04:10:24 +00:00
freemo commented 2026-03-14 04:45:25 +00:00
Author
Owner
Copy Link
Copy Source

PM Review — Day 34

Status: Mergeable, 0 reviews, M8 (v3.7.0)
Author: @freemo

E2E test for WF17 (explicit container with directory mount, trusted profile). M8 — low urgency.

Action Items

Who Action Deadline
Peer review deferred to M8 sprint
## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M8 (v3.7.0) **Author**: @freemo E2E test for WF17 (explicit container with directory mount, trusted profile). M8 — low urgency. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | Peer review deferred to M8 sprint | | |
freemo added a new dependency 2026-03-16 02:42:20 +00:00
#627 Implement @tdd_expected_fail tag handling in Behave environment
freemo added a new dependency 2026-03-16 02:42:20 +00:00
#628 Implement @tdd_expected_fail tag handling in Robot Framework
freemo commented 2026-03-16 09:35:06 +00:00
Author
Owner
Copy Link
Copy Source

PM Status — Day 36 (2026-03-16)

Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days.

Priority note: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order.

Assigned reviewer: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.

## PM Status — Day 36 (2026-03-16) Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days. **Priority note**: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order. **Assigned reviewer**: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.
hurui200320 was assigned by freemo 2026-03-16 22:17:38 +00:00
freemo commented 2026-03-16 22:18:48 +00:00
Author
Owner
Copy Link
Copy Source

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on #628 and #966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on https://git.cleverthis.com/cleveragents/cleveragents-core/issues/628 and https://git.cleverthis.com/cleveragents/cleveragents-core/issues/966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.
freemo commented 2026-03-17 18:34:04 +00:00
Author
Owner
Copy Link
Copy Source

PM Status — Day 37

Reviewers assigned. This PR needs at least 2 approving reviews per CONTRIBUTING.md before merge.

Author: Please ensure this PR is rebased on latest master and all quality gates pass before requesting merge.

PM status — Day 37

## PM Status — Day 37 Reviewers assigned. This PR needs at least 2 approving reviews per `CONTRIBUTING.md` before merge. **Author**: Please ensure this PR is rebased on latest `master` and all quality gates pass before requesting merge. --- *PM status — Day 37*
freemo requested review from hamza.khyari 2026-03-17 18:34:18 +00:00
hurui200320 force-pushed test/e2e-wf17-explicit-container from 03e3481154 to e89174e503 2026-03-18 08:35:47 +00:00 Compare
freemo commented 2026-03-19 04:58:02 +00:00
Author
Owner
Copy Link
Copy Source

Code Review — PR #819

(Cannot submit formal approval — self-authored PR.)

E2E test for WF17. Well-structured with proper labels, milestone, and issue linkage. No issues found.

## Code Review — PR #819 *(Cannot submit formal approval — self-authored PR.)* E2E test for WF17. Well-structured with proper labels, milestone, and issue linkage. No issues found.
freemo requested review from brent.edwards 2026-03-19 05:19:59 +00:00
freemo requested review from CoreRasurae 2026-03-19 05:19:59 +00:00
hurui200320 force-pushed test/e2e-wf17-explicit-container from e89174e503 to b0968d27b9 2026-03-20 07:05:05 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from b0968d27b9 to e720b34c57 2026-03-20 08:02:07 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from e720b34c57 to 78f98c8e24 2026-03-20 08:42:17 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from 78f98c8e24 to 693f002555 2026-03-20 10:17:19 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from 693f002555 to 33293811fc 2026-03-23 04:10:58 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from 33293811fc to 6b876e638a 2026-03-24 05:40:20 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from 6b876e638a to 9a8a27241c 2026-03-27 10:00:08 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from 9a8a27241c to 5eca78c6f2 2026-03-30 04:34:34 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from 5eca78c6f2 to 9c36c21722 2026-03-30 04:35:39 +00:00 Compare
hurui200320 force-pushed test/e2e-wf17-explicit-container from 9c36c21722 to 5ddc04bcc7 2026-03-30 08:05:52 +00:00 Compare
hurui200320 merged commit 5ddc04bcc7 into master 2026-03-30 08:25:36 +00:00
hurui200320 deleted branch test/e2e-wf17-explicit-container 2026-03-30 08:25:37 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
hamza.khyari
brent.edwards
CoreRasurae
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Priority
Medium
State
In Review
Type
Testing
Milestone
No items
No Milestone v3.7.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees hurui200320
2 Participants
Notifications
Due Date
No due date set.
Depends on
#627 Implement @tdd_expected_fail tag handling in Behave environment
cleveragents/cleveragents-core
#628 Implement @tdd_expected_fail tag handling in Robot Framework
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#819
Delete Branch "test/e2e-wf17-explicit-container"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?