Automated E2E tests for CAPI/Pixel events

[immadhavv]

Description

QA team performs E2E testing manually to verify CAPI Pixel events functionality and it is not scalable/reliable. It also delays feature /plugin release and the whole process is very manual.

This change automates the same by:

1. Simulating situations that trigger CAPI/Pixel events ,
2. Capturing Pixel events from network calls and CAPI events by intercepting the API call and logging both events
3. Validating event fires, fields, values, deduplication

Design Doc:

Type of change

Please delete options that are not relevant

• Add (non-breaking change which adds functionality)

Checklist

• [✅] I have commented my code, particularly in hard-to-understand areas, if any.
• [✅] I have confirmed that my changes do not introduce any new PHPCS warnings or errors.
• [✅] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors.
• [✅] I followed general Pull Request best practices. Meta employees to follow this wiki.
• [✅] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes.
• [✅] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality.
• [] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this wiki.

Changelog entry

Automated E2E tests for CAPI Pixel events

Test Plan

Successful Github Run - https://github.com/immadhavv/facebook-for-woocommerce/actions/runs/19720843464

Screenshots

Before

NA

After

https://github.com/immadhavv/facebook-for-woocommerce/actions/runs/19720843464

[meta-codesync]

@immadhavv has imported this pull request. If you are a Meta employee, you can view this in D87974468.