Skip to content

Gravity Flow: live verification against a real Gravity Flow site (blocker before merge) #1

Description

@marceldarvas

The 10 gravityflow_* tools (branch feat/gravity-flow) have routes verified against the Gravity Flow plugin source and full mocked unit coverage, but no endpoint has been exercised live. This is the largest remaining gap before merging into develop.

To do

  • Run npm run verify:tool-names against a live WP install with Gravity Flow (pin GRAVITY_FORMS_* to the local site — see AGENTS.md "Bench" gotchas about not hitting a remote site).
  • Real round-trip smoke on a test entry with an approval workflow:
    • gravityflow_get_workflow_status, _get_current_step, _get_steps_by_entry, _get_steps_by_form
    • gravityflow_process_step (approve, then a separate reject/revert), incl. note + inputs
    • gravityflow_send_to_step, _restart_step, _restart_workflow, _cancel_workflow
    • Confirm step_id: "current" alias resolves on get/process/restart
    • Confirm each action returns the post-action workflow-status body

Suggested target: /Users/marcel/Projects/Kiron/wordpress (has Gravity Flow). See docs/gravity-flow-testing-plan.md.

Branch: feat/gravity-flow

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions