Skip to content

[CI-6550] Add a page on running Maestro tests on Bitrise - #385

Merged
zoltan-baba merged 5 commits into
mainfrom
claude/maestro-test-docs-531906
Oct 26, 2026
Merged

zoltan-baba merged 5 commits into
mainfrom
claude/maestro-test-docs-531906

Conversation

@AndrasEszes

Copy link
Copy Markdown
Member

Adds a page on running Maestro flows with the new Maestro Test Step: Workflow Editor and YAML setup for Android and iOS, flow variables, tag filtering, and sharding across parallel Pipeline Workflows. The testing pages that list Steps or E2E tools now link to it.

Details
  • Draft until the Maestro Test Step is in the Steplib. Until then, the maestro-test Step ID in the YAML examples doesn't resolve.
  • The page sits at sidebar position 6, right after Device testing with Firebase, so the four pages after it moved down by one.

The page sits at the top level of the Testing section, not under a
platform folder: the Step runs Android and iOS flows, and React Native
and Flutter apps too, like the Firebase device testing pages next to it.
Inserting it at sidebar position 6 shifts the four pages after it.

The page leaves out the Step's input table. The Steplib page and the
Workflow Editor already show it, and a copy here would drift with every
Step release.
@github-actions

Copy link
Copy Markdown

The other procedures in the Testing section start at the Step itself,
or at most with one line that opens the Workflow. The shared login and
navigation partial added three steps here that a reader looking for a
test setup doesn't need.
Maestro has its own cloud, so without saying it, a reader can't tell
whether the Step runs the flows on the Bitrise VM or uploads them. The
device sentence pointed at an earlier Step without naming it.
Maestro also runs flows in a browser, but the Step only accepts an .apk
or a simulator .app, so a reader with web flows would only find out from
the Step's error.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Publication of maestro-test in Steplib needs confirmation before the draft documentation can safely be merged.

No open issues 🎉

What changed in this PR

Adds a Maestro testing guide to the Bitrise CI documentation and links it from related testing pages.

Changes:

  • Documents Android and iOS setup through the Workflow Editor and YAML, including variables, tag filtering, parallel execution, and test results.
  • Adds Maestro links to React Native, Flutter, sharding, and test-reporting guides.
  • Adjusts sidebar positions to place the new guide after Firebase device testing.
File Description
docs/​bitrise-ci/​testing/​testing-react-native-apps/​running-unit-and-ui-tests-for-react-native-apps.mdx Adds Maestro as an end-to-end testing option.
docs/​bitrise-ci/​testing/​testing-flutter-apps/​running-unit-and-ui-tests-on-flutter-apps.mdx Links to Maestro for UI testing.
docs/​bitrise-ci/​testing/​test-sharding.mdx Links to Maestro sharding instructions and adjusts sidebar position.
docs/​bitrise-ci/​testing/​running-maestro-tests-on-bitrise.mdx Adds the Maestro setup, execution, and troubleshooting guide.
docs/​bitrise-ci/​testing/​measuring-your-code-coverage-with-codecov.mdx Adjusts sidebar position.
docs/​bitrise-ci/​testing/​detecting-and-quarantining-flaky-tests.mdx Adjusts sidebar position.
docs/​bitrise-ci/​testing/​deploying-and-viewing-test-results.mdx Lists Maestro Test as supported and adjusts sidebar position.

Review effort: Balanced

The prerequisites are now the first step of each Android and iOS
procedure, and the device sentence became a short overview of how a
Maestro Workflow runs. The single-device warning moved next to the
device steps.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@zoltan-baba
zoltan-baba merged commit 3d30dbb into main Oct 26, 2026
3 checks passed
@zoltan-baba
zoltan-baba deleted the claude/maestro-test-docs-531906 branch October 26, 2026 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants