Automate e2e tests completely , sync to fb and verify the sync #3603

immadhavv · 2025-09-12T18:08:43Z

Description

Existing E2E tests were only being run on the client side , but not tested if they got synced to Meta properly.

This diff enables the team to do that.

Updated the plugin installation to use the required config to connect to a test Meta Catalog. This enables the sync.
Fixed the failing e2e tests and updated the tests to verify the sync entirely using a Validator
Added a Validator that just takes a productId and verifies it completely e2e
Flow:
- get data from both local WooCommerce and Meta Catalog
- check sync status - (synced if ALL products/variations exist in Meta and ALL products/variations belong to the same product group)
- compare field values
- report in detail
After validation, clean up the product from Meta Catalog

Detailed Doc to be attached.
Note: Access Token needs to be added as a secret in the facebook-for-woocommerce repository

Type of change

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

added QA automation framework to completely automate e2e tests.

Test Plan

Test runs -
https://github.com/immadhavv/facebook-for-woocommerce/actions/runs/17680660730/job/50253827914
https://github.com/immadhavv/facebook-for-woocommerce/actions/runs/17681217766/job/50255647335

Screenshots

Before

NA

After

Test Recording -
https://github.com/user-attachments/assets/3f54aee4-f261-46b3-be40-858940d2ce60

facebook-github-bot · 2025-09-12T18:18:15Z

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

Summary: ## Description Solving the bug mentioned here - https://www.internalfb.com/tasks/?t=235977313 Bug on stock update - Item now has +1 variant count and a new variant has been created. If QTY was changed for the new variant all sizes example - 'S|M|L|XL' are listed as the variants value ### Type of change Please delete options that are not relevant - Fix (non-breaking change which fixes an issue) ## Checklist - [yes] I have commented my code, particularly in hard-to-understand areas, if any. - [yes] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [yes] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [yes] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [] 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]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Fixes variant product sync for stock updates to commerce manager Pull Request resolved: facebook#3602 Test Plan: Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. ## Screenshots Please provide screenshots or snapshots of the system/state both before and after implementing the changes, if appropriate ### Before Logs when broken 3+1 extra got synced https://www.internalfb.com/phabricator/paste/view/P1944192224 product with attribute "size":"S | M | L" got synced ### After only 3 got synced https://www.internalfb.com/phabricator/paste/view/P1944194179 Reviewed By: guansu-meta Differential Revision: D82313000 Pulled By: rithikb24 fbshipit-source-id: 7f170a213abceab2361a30217da1a86b2d4bacbe

…book#3607) Summary: ## Description Fix Resize issue by listening to WA specific Resize PostMessage ### Type of change - Fix (non-breaking change which fixes an issue) ## Changelog entry Fix Resize issue by listening to WA specific Resize PostMessage Pull Request resolved: facebook#3607 Test Plan: ## Screenshots ### Before https://github.com/user-attachments/assets/a500326e-48bb-4572-b11a-5639e591aa32 ### After https://github.com/user-attachments/assets/aaedac5a-5d5d-4f06-abc1-f309c8842e58 Differential Revision: D82562773 Pulled By: sharunaanandraj fbshipit-source-id: 6c8ded51e5cf0f18cf0cd3ef8be5dcc2941976a2

Summary: ## Description The query params were not added to url hence locale wasn't being set in iframe_management url. Fixing this. ### Type of change Please delete options that are not relevant - Fix (non-breaking change which fixes an issue) ## Changelog entry Fix Iframe Management Url Stefi API Call Pull Request resolved: facebook#3608 Test Plan: ### Before - Locale not set in management uri > https://www.76872.od.commercepartnerhub.com/whatsapp_utility_integration/onboarding/?app_id=753591807210902&wa_installation_id=24132996163048732&external_business_id=sharuna-local-store-68c9a664ab340&access_token=--sanitized-- ### After - Locale set in management uri >https://www.76872.od.commercepartnerhub.com/whatsapp_utility_integration/onboarding/?app_id=753591807210902&locale=en&wa_installation_id=24132996163048732&external_business_id=sharuna-local-store-68c9a664ab340&access_token=--sanitized-- Reviewed By: woo-ardsouza Differential Revision: D82578917 Pulled By: sharunaanandraj fbshipit-source-id: bf07a0d3c638523697e4abf2d3e0e611088cfd01

…facebook#3612) Summary: ## Description Add Logs for WooCommerce WhatsApp Iframe Infra to Help with Debugging ### Type of change - Add (non-breaking change which adds functionality) ## Changelog entry Add Logs for WooCommerce WhatsApp Iframe Infra to Help with Debugging Pull Request resolved: facebook#3612 Test Plan: Success logs <img width="1543" height="509" alt="Screenshot 2025-09-18 at 5 00 55 PM" src="https://github.com/user-attachments/assets/429892f4-fa89-4efc-bf7b-35ca9b65ec63" /> Failure Logs <img width="1391" height="40" alt="Screenshot 2025-09-18 at 5 04 43 PM" src="https://github.com/user-attachments/assets/5a5f3901-8e22-4bfa-95d7-b01ec96cbdb4" /> Reviewed By: woo-ardsouza Differential Revision: D82780392 Pulled By: sharunaanandraj fbshipit-source-id: f36b7081ea65f4742bd8befb461e18aecd435625

…led (facebook#3611) Summary: ## Description Changes to call the Customer Events API at Meta to send Order Fulfilled Utility WhatsApp Messages for the Iframe Integration ### Type of change - Add (non-breaking change which adds functionality) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. ## Changelog entry Add call to Meta Event Processor when order status is completed Pull Request resolved: facebook#3611 Test Plan: Steps to reproduce: 1. Add Business id to dogfooding gk 2. Place order on WooCommerce site 3. Update order status to Completed 4. Validate Whatsapp Utility Message for Order Shipped is sent to phone number https://github.com/user-attachments/assets/aba87162-a680-4911-96cc-200dd393985c Reviewed By: sharunaanandraj Differential Revision: D82774935 Pulled By: woo-ardsouza fbshipit-source-id: f28777b2cc34b2790cc54bc567965aeb93b7ff6e

…3610) Summary: ## Description A privacy vulnerability has been identified where ajax call can be exploited without any authentication. This is due to the lack of nonce check. In this PR we add the missing nonce check to the identified ajax calls. ### Type of change - Fix (non-breaking change which fixes an issue) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality. - some buttons are no longer available in the latest version, but closing the banners seem to still work. - [] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this [wiki]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Add check_admin_referer to ajax calls. Pull Request resolved: facebook#3610 Test Plan: Using the script exploiting ajax calls: ([link](https://patchstack-database.s3.us-east-2.amazonaws.com/files/cee826db-a2eb-48e7-8245-adaa7bbf47cf/f5733814-bb1c-4f69-919c-e626d5004102.txt?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIATLPOZUEKEA5CDFOJ%2F20250918%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20250918T153413Z&X-Amz-SignedHeaders=host&X-Amz-Expires=604800&X-Amz-Signature=4abb2f7956aa9efd77f5730f9989ab460be104439be8b9b281bc34acc554daea) to script) - Before: received success response - After: received expired response See screenshots below. ## Screenshots ### Before <img width="773" height="307" alt="image" src="https://github.com/user-attachments/assets/88d122d4-f627-4b4d-98a3-742cecc367d6" /> ### After testing wc_facebook_sync_all_products <img width="722" height="314" alt="image" src="https://github.com/user-attachments/assets/010986f1-18b1-493d-b6d8-c3a7cbb76eeb" /> testing wc_facebook_opt_out_of_sync <img width="783" height="307" alt="image" src="https://github.com/user-attachments/assets/06c5befe-2b6a-47e7-aee7-6a1dbc81358d" /> Reviewed By: ajello-meta Differential Revision: D82740585 Pulled By: guansu-meta fbshipit-source-id: 037914a2b0509775aa006b7058f4d2e9c8e945a1

Summary: ## Description Changes to call the Customer Events API at Meta to send Order Refunded Utility WhatsApp Messages for the Iframe Integration ### Type of change - Add (non-breaking change which adds functionality) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. ## Changelog entry Add call to Meta Event Processor when order status is refunded Pull Request resolved: facebook#3614 Test Plan: Steps to reproduce: 1. Add Business id to dogfooding gk 2. Place order on WooCommerce site 3. Update order status to Completed 4. Validate Whatsapp Utility Message for Order Shipped is sent to phone number 5. Update order status to Redunded 6. Validate Whatsapp Utility Message for Order Refunded is sent to phone number https://github.com/user-attachments/assets/283be9cc-655a-4217-8cbe-714d905f911c Reviewed By: sharunaanandraj Differential Revision: D82798292 Pulled By: woo-ardsouza fbshipit-source-id: 32bbaaa61c1982a7be31b18e336da1cbf9e4cc6c

Summary: ## Description Changes to call the Customer Events API at Meta to send Order Placed Utility WhatsApp Messages for the Iframe Integration ### Type of change - Add (non-breaking change which adds functionality) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. ## Changelog entry Add call to Meta Event Processor when order status is processing Pull Request resolved: facebook#3615 Test Plan: Steps to reproduce: * Add Business id to dogfooding gk * Place order on WooCommerce site * Validate Whatsapp Utility Message for Order Placed is sent to phone number * Update order status to Completed * Validate Whatsapp Utility Message for Order Shipped is sent to phone number * Update order status to Redunded * Validate Whatsapp Utility Message for Order Refunded is sent to phone number https://github.com/user-attachments/assets/e63afd59-1091-4e42-aa40-57d579f3ff15 Tested url redirect works as expected https://github.com/user-attachments/assets/37383864-06e0-47c8-866c-d9e56f558a76 Reviewed By: sharunaanandraj Differential Revision: D82828349 Pulled By: woo-ardsouza fbshipit-source-id: 29ba42db42ada6a634605173ff412d421c3d9db5

…#3618) Summary: ## Description Return Error Banner if Iframe Management Url Fetching Fails. Error banner has two buttons: 1. Reload to Refetch the iframe Url 2. Reset - If there is an issue with fetching the iframe management url then we should allow reset the connection ### Type of change - Add (non-breaking change which adds functionality) ## Changelog entry Return Error Banner if Iframe Management Url Fetching Fails Pull Request resolved: facebook#3618 Test Plan: Before <img width="1723" height="957" alt="Screenshot 2025-09-19 at 11 10 04 AM" src="https://github.com/user-attachments/assets/fa3ae1f1-ab4e-4428-8afd-a1a4c43682b4" /> After https://github.com/user-attachments/assets/2cebc08f-f7a0-4d47-9ec2-2a61b0f01475 Reviewed By: woo-ardsouza Differential Revision: D82847718 Pulled By: sharunaanandraj fbshipit-source-id: 91f7efd305d7fb97d816c11b4513e7d5fa92fb45

Summary: ## Description Removed Graph API product delete functionality since this is being done through Batch API already ### Type of change - Tweak (non-breaking change which fixes code modularity, linting or phpcs issues) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality. - [x] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this [wiki]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Removed Graph API product delete functionality Pull Request resolved: facebook#3621 Reviewed By: ajello-meta Differential Revision: D82894836 Pulled By: vinkmeta fbshipit-source-id: 9ed47ed9d50bf135b81c47e72879f97da7ab614a

Summary: ## Description Deprecated product group update functionality ### Type of change - Tweak (non-breaking change which fixes code modularity, linting or phpcs issues) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality. - [x] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this [wiki]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Deprecated product group update functionality Pull Request resolved: facebook#3619 Reviewed By: ajello-meta Differential Revision: D82894655 Pulled By: vinkmeta fbshipit-source-id: b1154b4e2574d4131a90de883a145fe6d4e2944c

…acebook#3627) Summary: ## Description Update switch from only dogfooding GK to one combined with prod GK ### Type of change - Add (non-breaking change which adds functionality) ## Changelog entry Update switch from only dogfooding GK to one combined with prod GK Pull Request resolved: facebook#3627 Test Plan: The API fetch is successful, unable to fetch in UI since graph api is not working on OD in wordpress site <img width="1726" height="961" alt="Screenshot 2025-09-22 at 10 33 13 PM" src="https://github.com/user-attachments/assets/355b5566-0483-4aa4-b10b-ee50bb7b459f" /> Reviewed By: woo-ardsouza Differential Revision: D83031771 Pulled By: sharunaanandraj fbshipit-source-id: 0b134be444add878f367de534a7e1e9aff1f3e92

Summary: ## Description This PR fixes a PHP 8.2 deprecation notice caused by the use of deprecated string interpolation syntax (`"${var}"`). ### Type of change - Fix (non-breaking change which fixes an issue) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] 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]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Fix: Replace deprecated string interpolation syntax for PHP 8.2 compatibility Pull Request resolved: facebook#3626 Test Plan: ### Steps to Reproduce (Before Fix) 1. On `main`, enable `WP_DEBUG_LOG` in `wp-config.php`. 2. Place a test order. 3. Check `wp-content/debug.log`. 4. Observe the following deprecation notice: `PHP Deprecated: Using ${var} in strings is deprecated, use {$var} instead in app/public/wp-content/plugins/facebook-for-woocommerce/includes/Handlers/WhatsAppUtilityConnection.php on line 389` ### Steps to Verify (After Fix) 1. Switch to this branch. 2. Repeat the steps above (place a test order). 3. Check `wp-content/debug.log`. 4. Confirm that **no deprecation notice** appears. ## Screenshots ### Before ### After Reviewed By: akpurifb Differential Revision: D83038673 Pulled By: vahidkay-meta fbshipit-source-id: 2f398beb4d0d29b3b6aaa7df00b9ff0e5f6ebf9a

Summary: ## Description Removing unnecessary banner for every item create or update operation to reduce unnecessary noise ### Type of change - Tweak (non-breaking change which fixes code modularity, linting or phpcs issues) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality. - [x] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this [wiki]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Removing unnecessary banner for every item publish Pull Request resolved: facebook#3620 Reviewed By: yuriferretti Differential Revision: D83019028 Pulled By: vinkmeta fbshipit-source-id: 5bca38dd37c7345265137bd806a94200042753f0

Summary: This reverts commit 509812d. ## Description I'm reverting the parambuilder, as it blocked the last release, and it's still not in the proper shape to be released ### Type of change Please delete options that are not relevant - Fix (non-breaking change which fixes an issue) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality. - [x] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this [wiki]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Revert "changelog: add parambuilder (facebook#3549)" Pull Request resolved: facebook#3628 Differential Revision: D83043009 Pulled By: vahidkay-meta fbshipit-source-id: 394dcd19d8470c3c54e56c013585f667473cdba3

Summary: ## Description Added a check for the # of posts found in the result of the search query, before proceeding to create a search event. This is to fix issues like [this](https://wordpress.org/support/topic/missing-content_id-warnings-on-empty-woocommerce-search-result-pages/#utm_medium=referral&utm_source=facebook.com&utm_content=social) ### Type of change Please delete options that are not relevant - Fix (non-breaking change which fixes an issue) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality. - [x] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this [wiki]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Fix - Prevent Missing content_id warnings on empty WooCommerce search result pages Pull Request resolved: facebook#3606 Test Plan: Manually tested Reviewed By: rafael-curran Differential Revision: D83047576 Pulled By: vahidkay-meta fbshipit-source-id: 3d6d6271d14104933147e7e093294a2fce9240b6

Summary: ## Description This PR updates the purchase event tracking logic to recognize additional WooCommerce order statuses as valid triggers. Specifically, the statuses on-hold and pending are now included alongside existing statuses (processing, completed). ### Type of change Please delete options that are not relevant - Add (non-breaking change which adds functionality) ## Checklist - [X] I have commented my code, particularly in hard-to-understand areas, if any. - [X] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [X] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [X] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [X] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [X] 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]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Add support for `on-hold` and `pending` order statuses in purchase event tracking Pull Request resolved: facebook#3629 Test Plan: 1. Place a WooCommerce order that enters the pending status. 2. Place a WooCommerce order that enters the on-hold status. 3. Place a WooCommerce order that enters the existing supported statuses (processing, completed). 4. Review logs or use the Meta Pixel Helper extension to confirm that events are correctly dispatched. ## Screenshots ### Before ### After Reviewed By: rafael-curran Differential Revision: D83061862 Pulled By: vahidkay-meta fbshipit-source-id: 891f5d4f409bc82a2ecf495fb16e0804c96451cb

Summary: ## Description Fix error message in Customer Event Logging ### Type of change - Fix (non-breaking change which fixes an issue) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. ## Changelog entry Fix error message in Customer Event Error Logs Pull Request resolved: facebook#3630 Test Plan: 1. Place an Order on WooCommerce Site 2. Trigger error state artificially by passing empty phone number in api call 3. Validate error log has details on phone number ## Screenshots <img width="1742" height="895" alt="Screenshot 2025-09-23 at 12 06 47 PM" src="https://github.com/user-attachments/assets/de01d1c8-9feb-441d-80d2-fbcf59e16d8e" /> Reviewed By: sharunaanandraj Differential Revision: D83080885 Pulled By: woo-ardsouza fbshipit-source-id: 571160acef26de1f1c30ad24478174d5335a8cd5

Summary: ## Description Cleanup deprecated product delete functionality ### Type of change - Tweak (non-breaking change which fixes code modularity, linting or phpcs issues) ## Checklist - [x] I have commented my code, particularly in hard-to-understand areas, if any. - [x] I have confirmed that my changes do not introduce any new PHPCS warnings or errors. - [x] I have checked plugin debug logs that my changes do not introduce any new PHP warnings or FATAL errors. - [x] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc)). - [x] I have added tests (if necessary) and all the new and existing unit tests pass locally with my changes. - [x] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality. - [x] I have updated or requested update to plugin documentations (if necessary). Meta employees to follow this [wiki]([url](https://fburl.com/wiki/nhx73tgs)). ## Changelog entry Cleanup deprecated product delete functionality Pull Request resolved: facebook#3622 Reviewed By: ajello-meta Differential Revision: D82894834 Pulled By: vinkmeta fbshipit-source-id: c936fecede714939c16a8d6b20dff9adeb6d5f1e

…2e-tests-completely

immadhavv added 5 commits September 12, 2025 18:08

E2E tests fully automated

6621849

added workflow_dispatch to test if e2e tests work correctly

361c301

removed workflow_dispatch after testing

70340bf

renamed the validator file

6f17ceb

renamed the validator file

8091208

immadhavv requested a review from vinkmeta September 12, 2025 18:08

immadhavv self-assigned this Sep 12, 2025

meta-cla bot added the CLA Signed label Sep 12, 2025

immadhavv requested a review from vahidkay-meta September 12, 2025 18:09

immadhavv added the changelog: add A new feature, function, or functionality was added. label Sep 12, 2025

added space

584ac33

immadhavv removed their assignment Sep 12, 2025

immadhavv changed the base branch from automate-e2e-tests-completely to main September 12, 2025 18:16

rithikb24 and others added 16 commits September 24, 2025 14:18

updated IDs to use secrets instead

f75b473

added workflow_dispatch option

42ea50f

updated page_id variable name

64bd3be

update SKU to ensure unique values across runs and avoid collision

dfa203e

ukilla and others added 9 commits September 24, 2025 17:26

add extra waiting period for variable products

90372e3

Merge branch 'facebook:automate-e2e-tests-completely' into automate-e…

313b6c5

…2e-tests-completely

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Automate e2e tests completely , sync to fb and verify the sync #3603

Automate e2e tests completely , sync to fb and verify the sync #3603

immadhavv commented Sep 12, 2025 •

edited

Loading

Uh oh!

facebook-github-bot commented Sep 12, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants

Automate e2e tests completely , sync to fb and verify the sync #3603

Are you sure you want to change the base?

Automate e2e tests completely , sync to fb and verify the sync #3603

Conversation

immadhavv commented Sep 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Type of change

Checklist

Changelog entry

Test Plan

Screenshots

Before

After

Uh oh!

facebook-github-bot commented Sep 12, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants

immadhavv commented Sep 12, 2025 •

edited

Loading