test(e2e): add M1 source-code plan lifecycle suite #156

Closed
opened 2026-02-22 23:39:41 +00:00 by freemo · 1 comment
Owner

Metadata

  • Commit Message: test(e2e): add M1 source-code plan lifecycle suite
  • Branch: feature/m1-e2e-sourcecode

Background

End-to-end test fixtures and helper steps cover the minimal source-code workflow: a git repo fixture, a git-checkout resource config, and a minimal action YAML with strategy/execution actors. Helper steps create temp projects, link resources, and capture plan IDs for subsequent CLI verification.

Acceptance Criteria

  • Add E2E fixtures for a minimal git repo, a git-checkout resource config, and a minimal action YAML with strategy/execution actors.
  • Add helper steps that create a temp project + resource link and capture plan IDs for subsequent CLI steps.
  • Update docs/development/testing.md with M1 source-code smoke run instructions and failure triage tips.

Definition of Done

This issue is complete when:

  • All subtasks below are completed and checked off.
  • A Git commit is created where the first line of the commit message matches
    the Commit Message in Metadata exactly, followed by a blank line, then
    additional lines providing relevant details about the implementation. The
    commit body should be appropriate in size for a commit message and relatively
    complete in describing what was done.
  • The commit is pushed to the remote on the branch matching the Branch in
    Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and
    merged before this issue is marked done.

Subtasks

  • Add E2E fixtures for a minimal git repo, a git-checkout resource config, and a minimal action YAML with strategy/execution actors.
  • Add helper steps that create a temp project + resource link and capture plan IDs for subsequent CLI steps.
  • Update docs/development/testing.md with M1 source-code smoke run instructions and failure triage tips.
  • Tests (Behave): Add features/m1_sourcecode_smoke.feature covering action create, project/resource link, plan use, execute, diff, apply.
  • Tests (Robot): Add Robot CLI smoke suite for M1 end-to-end flow using --format plain to stabilize assertions.
  • Tests (ASV): Add benchmarks/m1_sourcecode_smoke_bench.py for baseline runtime.
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M1: Minimal Local Source-Code Workflow (Target: Day 7, recovery path)
Status: Open

## Metadata - **Commit Message**: `test(e2e): add M1 source-code plan lifecycle suite` - **Branch**: `feature/m1-e2e-sourcecode` ## Background End-to-end test fixtures and helper steps cover the minimal source-code workflow: a git repo fixture, a `git-checkout` resource config, and a minimal action YAML with strategy/execution actors. Helper steps create temp projects, link resources, and capture plan IDs for subsequent CLI verification. ## Acceptance Criteria - [ ] Add E2E fixtures for a minimal git repo, a `git-checkout` resource config, and a minimal action YAML with strategy/execution actors. - [ ] Add helper steps that create a temp project + resource link and capture plan IDs for subsequent CLI steps. - [ ] Update `docs/development/testing.md` with M1 source-code smoke run instructions and failure triage tips. ## Definition of Done This issue is complete when: - All subtasks below are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. The commit body should be appropriate in size for a commit message and relatively complete in describing what was done. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. ## Subtasks - [ ] Add E2E fixtures for a minimal git repo, a `git-checkout` resource config, and a minimal action YAML with strategy/execution actors. - [ ] Add helper steps that create a temp project + resource link and capture plan IDs for subsequent CLI steps. - [ ] Update `docs/development/testing.md` with M1 source-code smoke run instructions and failure triage tips. - [ ] Tests (Behave): Add `features/m1_sourcecode_smoke.feature` covering action create, project/resource link, plan use, execute, diff, apply. - [ ] Tests (Robot): Add Robot CLI smoke suite for M1 end-to-end flow using `--format plain` to stabilize assertions. - [ ] Tests (ASV): Add `benchmarks/m1_sourcecode_smoke_bench.py` for baseline runtime. - [ ] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M1: Minimal Local Source-Code Workflow (Target: Day 7, recovery path) **Status**: Open
freemo added this to the v3.0.0 milestone 2026-02-22 23:39:41 +00:00
Author
Owner

Expected completion updated (Day 15 rebaseline): Day 18 / 2026-02-26 (previously Day 17 / 2026-02-25)

**Expected completion updated (Day 15 rebaseline):** Day 18 / 2026-02-26 (previously Day 17 / 2026-02-25)
freemo added the due date 2026-02-24 2026-02-23 18:41:24 +00:00
brent.edwards 2026-02-25 21:06:50 +00:00
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".

2026-02-24

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