Page MenuHomePhabricator

QA – Verify Contribution Creation Hooks, Acoustic Export, and Triggers
Open, Needs TriagePublic

Description

Summery:
Perform QA checks to ensure that contribution creation (including pending and completed statuses) correctly triggers all expected hooks and downstream processes.

Scope / Areas to Test:

CiviCRM Contribution Creation:

  • Verify that contributions are created with correct status (Pending, Completed, or Failed).
  • Confirm all expected metadata (e.g., transaction ID, payment method) is stored properly.

Civi Hooks / Post-Processing:

  • Ensure any hooks or related triggers fire correctly after contribution creation or status update.
  • Validate that webhook-based updates also trigger these hooks when a pending payment becomes completed.

Acoustic Export:

  • Confirm that new contributions (only send when complete) are correctly queued/exported to Acoustic.
  • Check that no duplicate or missing records occur.

Email / Trigger Logic:

  • Verify Thank You email is not sent for pending status.
  • Verify Thank You email is sent upon completion.
  • Confirm no email is sent for failed transactions.

Acceptance Criteria:

  • All hooks fire as expected on contribution creation and updates.
  • Acoustic exports reflect the latest contribution state accurately.
  • Email triggers match the defined business logic.
  • Logs show no unhandled errors.

Event Timeline

I am not sure if this would be covered under the Acceptance Criteria, but @krobinson raised the question:

What will happen if a donor is on an email list and they have essentially donated but it hasn't completed? Will the scan look for pendings and exclude them from fundraising emails like it does completed donations?