Add Maestro smoke tests for automated UI testing#15413
Draft
JorgeMucientes wants to merge 1 commit intotrunkfrom
Draft
Add Maestro smoke tests for automated UI testing#15413JorgeMucientes wants to merge 1 commit intotrunkfrom
JorgeMucientes wants to merge 1 commit intotrunkfrom
Conversation
Adds 18 Maestro flow files covering login, dashboard stats, orders, products, hub menu, Blaze, Google for Woo, and POS scenarios based on the P2 smoke testing flows. Credentials are passed via environment variables and never hardcoded. Includes reusable subflows for login and tab navigation, a workspace config with execution ordering, and a README documenting coverage and usage.
Collaborator
Generated by 🚫 Danger |
JorgeMucientes
force-pushed
the
maestro-smoke-tests-experiment
branch
from
7c3d27e to
d773560
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds automated UI smoke tests using Maestro that cover the manual testing flows defined in the Smoke Testing P2 post : P91TBi-bVe-p2.
What's included
config.yaml) with execution ordering and tags-eflagsKey learnings
testTags are not visible to Maestro withouttestTagsAsResourceId— text-based selectors are used instead for Compose UICoverage
17 of 18 flows validated against a real Android emulator (POS requires tablet). See README for full coverage matrix vs P2 smoke testing flows.
Test plan
curl -fsSL "https://get.maestro.mobile.dev" | bash./gradlew :WooCommerce:installWasabiDebugmaestro test -e WOO_EMAIL="..." -e WOO_PASSWORD="..." -e WOO_STORE_URL="..." .maestro/flows/login_successful.yamlmaestro test -e WOO_EMAIL="..." -e WOO_PASSWORD="..." -e WOO_STORE_URL="..." .maestro/flows/