test(integration): workflow example 5 — database schema migration with safety nets (review profile) #769

Closed
opened 2026-03-12 19:38:59 +00:00 by freemo · 0 comments
Owner

Metadata

  • Commit Message: test(integration): workflow example 5 — database schema migration with safety nets (review profile)
  • Branch: test/int-wf05-db-migration

Background

Integration test for Specification Workflow Example 5: Database Schema Migration with Safety Nets. Exercises the review automation profile with mixed resource types, custom skills with database tools, phased child plans, checkpointing, and rollback using mocked LLM providers.

Runs within the standard nox -s integration_tests session using mocked LLM providers.

Expected Behavior

The integration test validates the database migration workflow with mocked LLM and mocked database operations. Custom resource registration, skill creation, phased execution, and checkpoint/rollback are all exercised.

Acceptance Criteria

  • Robot Framework test suite in robot/ directory (standard integration tests)
  • Test registers custom resource type and custom skill with database tools
  • Test uses integration-appropriate mocking (mocked LLM providers, mocked DB)
  • Test exercises phased child plan execution
  • Test exercises checkpoint creation and rollback
  • Test passes via nox -s integration_tests
  • Coverage >=97% maintained

Subtasks

  • Write Robot Framework integration test suite for workflow example 5
  • Configure mocked LLM and database responses
  • Create temp project fixture with database migration scenario
  • Implement review-profile workflow with custom resources and skills
  • Verify via nox -s integration_tests
  • Verify coverage >=97% via nox -s coverage_report
  • Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above 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.
  • 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.
## Metadata - **Commit Message**: `test(integration): workflow example 5 — database schema migration with safety nets (review profile)` - **Branch**: `test/int-wf05-db-migration` ## Background Integration test for Specification Workflow Example 5: Database Schema Migration with Safety Nets. Exercises the `review` automation profile with mixed resource types, custom skills with database tools, phased child plans, checkpointing, and rollback using mocked LLM providers. Runs within the standard `nox -s integration_tests` session using mocked LLM providers. ## Expected Behavior The integration test validates the database migration workflow with mocked LLM and mocked database operations. Custom resource registration, skill creation, phased execution, and checkpoint/rollback are all exercised. ## Acceptance Criteria - [x] Robot Framework test suite in `robot/` directory (standard integration tests) - [x] Test registers custom resource type and custom skill with database tools - [x] Test uses integration-appropriate mocking (mocked LLM providers, mocked DB) - [x] Test exercises phased child plan execution - [x] Test exercises checkpoint creation and rollback - [x] Test passes via `nox -s integration_tests` - [x] Coverage >=97% maintained ## Subtasks - [x] Write Robot Framework integration test suite for workflow example 5 - [x] Configure mocked LLM and database responses - [x] Create temp project fixture with database migration scenario - [x] Implement review-profile workflow with custom resources and skills - [x] Verify via `nox -s integration_tests` - [x] Verify coverage >=97% via `nox -s coverage_report` - [x] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above 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. - 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.
freemo added this to the v3.3.0 milestone 2026-03-12 19:38:59 +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".

No due date set.

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