{"id":4698,"date":"2023-05-15T08:00:27","date_gmt":"2023-05-15T07:00:27","guid":{"rendered":"https:\/\/www.diogonunes.com\/blog\/?p=4698"},"modified":"2023-05-22T14:29:53","modified_gmt":"2023-05-22T13:29:53","slug":"framework-review-maestro","status":"publish","type":"post","link":"https:\/\/www.diogonunes.com\/blog\/framework-review-maestro\/","title":{"rendered":"Framework review: Maestro"},"content":{"rendered":"
\"\"
Conductor Eimear Noone \ud83c\udfbc \ud83c\udfae<\/figcaption><\/figure>\n
\n

\ud83c\udfc6 This post was featured in Software Testing Weekly #169<\/a><\/p>\n<\/blockquote>\n

A friend (Hugo<\/a>) told me about this new mobile test automation framework called Maestro<\/a>. At the time, my team was using Appium to test a React Native app, that ran on iOS and Android. I was not 100% happy with Appium, so I gave Maestro a try.<\/p>\n

<\/p>\n

Maestro commands<\/h3>\n
# install\nbrew tap mobile-dev-inc\/tap\nbrew install maestro\n\n# install iOS support\nbrew tap facebook\/fb\nbrew install facebook\/fb\/idb-companion\nxcrun simctl list           # UDID of available iOS devices\nidb_companion --boot {udid} # boots one of those devices\n\n# run\nnpm run start\nnpm run e2e:maestro\n<\/code><\/pre>\n
Maestro code<\/h3>\n
package.json<\/code><\/p>\n
\"e2e:maestro\": \"for i in test-e2e\/maestro\/*.yml; do maestro test $i; done\",\n\"e2e:maestro:ios\": \"maestro test test-e2e\/maestro\/ios\/open-app.test.yml\",\n<\/code><\/pre>\n
open-app.test.yaml<\/code><\/p>\n
appId: com.company.app\n---\n- clearState\n- launchApp\n\n# should render welcome page\n- assertVisible: 'The future is here.'\n- assertVisible: '.*Terms of Service.*'\n\n# should support login with email\n- tapOn: 'Get started'\n- inputText: 'someone@company.com'\n- hideKeyboard\n- tapOn: 'Next'\n\n# should ask for 2FA\n- assertVisible: 'Verification code'\n- assertVisible: '.*Resend code.*'\n\n<\/code><\/pre>\n
My opinion<\/h3>\n
While I experimented with the framework I discovered a few behaviours:<\/p>\n