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

test(e2e): workflow example 1 — Hello World, fix a single bug (manual profile) #788

Closed
freemo wants to merge 1 commits from test/e2e-wf01-hello-world into master
pull from: test/e2e-wf01-hello-world
merge into: cleveragents:master
Conversation 5 Commits 1 Files Changed 2
+306
freemo commented 2026-03-12 22:20:33 +00:00
Owner
Copy Link
Copy Source

Summary

E2E test for Specification Workflow Example 1: Hello World — Fix a Single Bug. Exercises the complete manual automation profile workflow with full plan lifecycle under human oversight. A developer fixes a bug where the /health endpoint returns HTTP 500 when the database is unavailable (should return 200 with degraded status).

Zero mocking — real CLI, real LLM API keys, real subprocess execution. Robot Framework test tagged @E2E.

Changes

  • Added robot/e2e/wf01_hello_world.robot implementing the full workflow:
    1. agents init --yes --force
    2. Create fixture git repo with buggy /health endpoint
    3. agents resource add git-checkout — register the repo
    4. agents project create — create and link project
    5. agents validation add + agents validation attach — register and attach a validation (unit tests) per spec Example 1
    6. agents action create — create action from YAML config
    7. agents plan use — create plan with --automation-profile manual
    8. agents plan execute — strategize phase (with error-pattern assertions)
    9. agents plan tree + agents plan explain — inspect decision tree (with non-empty assertions)
    10. agents plan execute — execute phase (with error-pattern assertions)
    11. agents plan diff — review changeset (with non-empty output assertion)
    12. agents plan apply --yes — apply changes (with error-pattern assertions)
    13. Post-apply git commit verification (HEAD SHA change detection)
  • Updated CHANGELOG.md with entry at top of Unreleased section

Security

  • Fixed Python code injection risk in Evaluate calls: replaced raw string interpolation (r'''${stdout}''') with Robot Framework module variable syntax ($combined) to prevent arbitrary code execution if CLI output contains triple-quote sequences.

Known Limitations

  • --arg bug_description=... is not passed to plan use due to a pre-existing UNIQUE constraint violation bug in plan_arguments table when arguments are defined both in action schema and passed via CLI --arg. This is tracked as a separate issue.
  • Post-apply commit verification uses a soft check (warning log) when HEAD SHA doesn't change, since plan apply --yes may succeed without producing a new commit depending on sandbox strategy and LLM output.
  • Test-level timeout set to 20 minutes to accommodate worst-case LLM execution times.

Closes #747

## Summary E2E test for Specification Workflow Example 1: Hello World — Fix a Single Bug. Exercises the complete `manual` automation profile workflow with full plan lifecycle under human oversight. A developer fixes a bug where the `/health` endpoint returns HTTP 500 when the database is unavailable (should return 200 with degraded status). **Zero mocking** — real CLI, real LLM API keys, real subprocess execution. Robot Framework test tagged `@E2E`. ## Changes - Added `robot/e2e/wf01_hello_world.robot` implementing the full workflow: 1. `agents init --yes --force` 2. Create fixture git repo with buggy `/health` endpoint 3. `agents resource add git-checkout` — register the repo 4. `agents project create` — create and link project 5. `agents validation add` + `agents validation attach` — register and attach a validation (unit tests) per spec Example 1 6. `agents action create` — create action from YAML config 7. `agents plan use` — create plan with `--automation-profile manual` 8. `agents plan execute` — strategize phase (with error-pattern assertions) 9. `agents plan tree` + `agents plan explain` — inspect decision tree (with non-empty assertions) 10. `agents plan execute` — execute phase (with error-pattern assertions) 11. `agents plan diff` — review changeset (with non-empty output assertion) 12. `agents plan apply --yes` — apply changes (with error-pattern assertions) 13. Post-apply git commit verification (HEAD SHA change detection) - Updated `CHANGELOG.md` with entry at top of Unreleased section ## Security - Fixed Python code injection risk in `Evaluate` calls: replaced raw string interpolation (`r'''${stdout}'''`) with Robot Framework module variable syntax (`$combined`) to prevent arbitrary code execution if CLI output contains triple-quote sequences. ## Known Limitations - `--arg bug_description=...` is not passed to `plan use` due to a pre-existing UNIQUE constraint violation bug in `plan_arguments` table when arguments are defined both in action schema and passed via CLI `--arg`. This is tracked as a separate issue. - Post-apply commit verification uses a soft check (warning log) when HEAD SHA doesn't change, since `plan apply --yes` may succeed without producing a new commit depending on sandbox strategy and LLM output. - Test-level timeout set to 20 minutes to accommodate worst-case LLM execution times. Closes #747
freemo added this to the v3.0.0 milestone 2026-03-12 22:20:39 +00:00
freemo added the
Type
Testing
 label 2026-03-12 22:20:40 +00:00
freemo force-pushed test/e2e-wf01-hello-world from 9ff64667bf to ec6ace99c0 2026-03-13 16:10:08 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from ec6ace99c0 to 7a2dc016dc 2026-03-13 16:23:45 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from 7a2dc016dc to 18f38781d9 2026-03-13 16:31:33 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from 18f38781d9 to 3b56da9abb 2026-03-13 16:42:17 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from 3b56da9abb to a159ce695c 2026-03-13 16:56:59 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from a159ce695c to 422ef2e142 2026-03-13 17:28:33 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from 422ef2e142 to 1c4d8e1270 2026-03-13 17:46:47 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from 1c4d8e1270 to 282855a26a 2026-03-13 17:51:46 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from 282855a26a to 020d35824b 2026-03-13 18:18:51 +00:00 Compare
freemo force-pushed test/e2e-wf01-hello-world from 020d35824b to 952551bcd3 2026-03-13 20:56:27 +00:00 Compare
freemo added the
State
In Review
 label 2026-03-13 21:16:27 +00:00
freemo force-pushed test/e2e-wf01-hello-world from 952551bcd3 to 4b218021c7 2026-03-13 23:19:30 +00:00 Compare
freemo commented 2026-03-14 04:44:20 +00:00
Author
Owner
Copy Link
Copy Source

PM Review — Day 34

Status: Mergeable, 0 reviews, M1 (v3.0.0), State/In Review
Author: @freemo

E2E test for WF01 (Hello World, fix a single bug — manual profile). Retroactive M1 acceptance coverage.

Action Items

Who Action Deadline
@brent.edwards Peer review Day 37
## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M1 (v3.0.0), State/In Review **Author**: @freemo E2E test for WF01 (Hello World, fix a single bug — manual profile). Retroactive M1 acceptance coverage. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @brent.edwards | **Peer review** | Day 37 |
freemo added the
MoSCoW
Must have
Points
3
 labels 2026-03-14 22:10:35 +00:00
freemo modified the milestone from v3.0.0 to v3.2.0 2026-03-16 00:31:58 +00:00
freemo added a new dependency 2026-03-16 02:42:13 +00:00
#627 Implement @tdd_expected_fail tag handling in Behave environment
freemo added a new dependency 2026-03-16 02:42:14 +00:00
#628 Implement @tdd_expected_fail tag handling in Robot Framework
freemo commented 2026-03-16 09:26:37 +00:00
Author
Owner
Copy Link
Copy Source

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

Day 34 review assignment deadline check. This PR has been in review for 2+ days with 0 reviewer activity.

Reminder: Assigned reviewer — please post your review by Day 37 EOD or flag any blockers. These E2E test PRs are foundational for milestone acceptance gates and cannot remain unreviewed indefinitely.

If you are unable to review by the deadline, please comment so the review can be reassigned.

## PM Status — Day 36 (2026-03-16) Day 34 review assignment deadline check. This PR has been in review for 2+ days with 0 reviewer activity. **Reminder**: Assigned reviewer — please post your review by **Day 37 EOD** or flag any blockers. These E2E test PRs are foundational for milestone acceptance gates and cannot remain unreviewed indefinitely. If you are unable to review by the deadline, please comment so the review can be reassigned.
freemo reviewed 2026-03-16 16:14:59 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

PM Day 36 Triage: MERGE CONFLICT. Needs rebase onto master before review can proceed. This is an M3 E2E test (v3.2.0) — lower priority than active bug fixes and TDD infrastructure work. Will queue for review after critical path items clear.

PM Day 36 Triage: MERGE CONFLICT. Needs rebase onto master before review can proceed. This is an M3 E2E test (v3.2.0) — lower priority than active bug fixes and TDD infrastructure work. Will queue for review after critical path items clear.
hurui200320 was assigned by freemo 2026-03-16 22:23:48 +00:00
freemo commented 2026-03-16 22:23:53 +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.
hurui200320 force-pushed test/e2e-wf01-hello-world from 4b218021c7 to a3455c33ef 2026-03-18 08:46:35 +00:00 Compare
freemo requested review from CoreRasurae 2026-03-22 16:40:07 +00:00
freemo requested review from brent.edwards 2026-03-22 16:40:07 +00:00
hurui200320 force-pushed test/e2e-wf01-hello-world from a3455c33ef to 460552379b 2026-03-24 07:33:55 +00:00 Compare
hurui200320 force-pushed test/e2e-wf01-hello-world from 460552379b to 0d94de9972 2026-03-26 08:10:44 +00:00 Compare
hurui200320 force-pushed test/e2e-wf01-hello-world from 0d94de9972 to 95d0c6a3c6 2026-03-27 09:58:39 +00:00 Compare
hurui200320 was unassigned by freemo 2026-04-02 06:15:25 +00:00
freemo self-assigned this 2026-04-02 06:15:25 +00:00
freemo commented 2026-04-02 17:35:36 +00:00
Author
Owner
Copy Link
Copy Source

🤖 Backlog Groomer (groomer-1): Closing as duplicate of #747.

Issue #747 (test(e2e): workflow example 1 — hello world, fix a single bug) is the canonical version with full labels (MoSCoW/Must have, Priority/Critical, State/In Review, Type/Testing) and milestone v3.2.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #747. Issue #747 (`test(e2e): workflow example 1 — hello world, fix a single bug`) is the canonical version with full labels (`MoSCoW/Must have`, `Priority/Critical`, `State/In Review`, `Type/Testing`) and milestone `v3.2.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:35:51 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 26s
Required
Details
CI / lint (pull_request) Successful in 3m26s
Required
Details
CI / typecheck (pull_request) Successful in 4m2s
Required
Details
CI / quality (pull_request) Successful in 4m20s
Required
Details
CI / security (pull_request) Successful in 4m43s
Required
Details
CI / integration_tests (pull_request) Successful in 7m38s
Required
Details
CI / unit_tests (pull_request) Successful in 8m14s
Required
Details
CI / docker (pull_request) Successful in 1m8s
Required
Details
CI / e2e_tests (pull_request) Successful in 13m58s
Details
CI / coverage (pull_request) Successful in 13m59s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 1h3m48s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
freemo
CoreRasurae
brent.edwards
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
MoSCoW
Must have
Points
3
State
In Review
Type
Testing
Milestone
No items
No Milestone v3.2.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 freemo
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#788
Delete Branch "test/e2e-wf01-hello-world"

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?