Skip to content

Conversation

@iamgabrielma
Copy link
Contributor

@iamgabrielma iamgabrielma commented Nov 26, 2025

Closes WOOMOB-1644

Description

Screenshot 2025-12-04 at 18 09 15

Changes

  • Runs UI POS screenhot tests on iPads only
  • Moves existing 1-5 iPhone screenshots to default folder
  • Adds 6, 7, and 8 POS screenshots

Test Steps

  • Run WooCommerceScreenshots.testScreenshots() both in iPad and iPhone as your run destination, they should pass (some UI tests are a bit flaky, but on a second run they should normally pass correctly)

Screenshots


  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

@dangermattic
Copy link
Collaborator

1 Message
📖 This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

@iamgabrielma iamgabrielma added the generate screenshots Triggers a GitHub Action to generate screenshots for this PR. label Nov 27, 2025
@wpmobilebot
Copy link
Collaborator

wpmobilebot commented Nov 28, 2025

App Icon📲 You can test the changes from this Pull Request in WooCommerce iOS Prototype by scanning the QR code below to install the corresponding build.

App NameWooCommerce iOS Prototype
Build Numberpr16405-25f2199
Version23.7
Bundle IDcom.automattic.alpha.woocommerce
Commit25f2199
Installation URL60o29u25j37f0
Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

Despite tests passing, the contents of the pos-payment screenshot was incorrect, as lands on the failure case for `checkOrderIsStillEligibleForPayment` when attempting to retrieve the order details, hence showing a “Error: unable to process payment. we could not fetch the latest order details” rather than the payment view.

Despite passing the CPP mock in the POSTabCoordinator, we were never setting it in the test as a launch argument.
Since we run the notification screenshot the last one due to the UI test flow, when we run the create_promo lane then screenshot descriptions are miss-aligned with what they show which fails the job.
At the moment we intersect POS screenshots, but “product-add” screenshot happens as the 7th, while in screenshots.js is set to be the 4rth. This fails the create_promo job as cannot find the correct index along the screenshot name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

generate screenshots Triggers a GitHub Action to generate screenshots for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants