<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Leland Takamine on Medium]]></title>
        <description><![CDATA[Stories by Leland Takamine on Medium]]></description>
        <link>https://medium.com/@leland_40592?source=rss-b5f8fb397d60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*itLzh1773rcxl6Ko</url>
            <title>Stories by Leland Takamine on Medium</title>
            <link>https://medium.com/@leland_40592?source=rss-b5f8fb397d60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:15:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leland_40592/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Fixing Android’s 3-minute screen recording limitation]]></title>
            <link>https://medium.com/@leland_40592/fixing-androids-3-minute-screen-recording-limitation-4839abc74aee?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/4839abc74aee</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Thu, 24 Aug 2023 15:59:02 GMT</pubDate>
            <atom:updated>2025-01-09T19:39:41.728Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we used binary rewriting to remove the 3-minute screen recording limitation on Maestro Cloud</h4><p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*paVAkANOe5_Q18MUL8DGgA.png" /></figure><p>Android provides a nice utility for recording the device screen from the command-line via ADB:</p><pre>adb shell screenrecord</pre><p>Unfortunately, it comes with one BIG caveat: <strong>You can only record up to 180 seconds in one go.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNLUrsIhLaRIR43xWxoQfQ.png" /></figure><p>This was a serious issue for us at Mobile.dev because we rely on this tool for Android screen recordings on <a href="https://mobile.dev/">Maestro Cloud</a>. In fact, the 3-minute recording limit was one of the most common complaints we were hearing from our users.</p><p>We tried several creative approaches, but ultimately only one solution gave us everything we needed:</p><ul><li>Allows recordings beyond 3 minutes</li><li>Produces a single video file that doesn’t skip</li><li>Doesn’t require maintaining many branches of changes on AOSP</li><li>Works on any version of Android</li><li>Works on emulators and production physical devices</li><li>Easy to integrate into our infrastructure codebase</li></ul><h3>What we tried</h3><h4>❌<strong> Run the command multiple times</strong></h4><p>This solution outputs multiple mp4 files. It’s possible to stitch the resulting files together (eg. with ffmpeg) but your recording will skip at the seams between the recordings.</p><h4>❌ <strong>Modify and recompile from source</strong></h4><p>The screenrecording binary is dynamically linked so you’ll need to build a separate binary for each version of Android you want to run this on. Possible, but if you’ve ever dealt with AOSP before, you already know how painful this is.</p><h4>❌ Use scrcpy instead of adb screenrecord</h4><p><a href="https://github.com/Genymobile/scrcpy">scrcpy</a> doesn’t suffer from the 3-minute time limit, but it’s a user-facing product and not built to easily integrate with other tools or existing codebases.</p><h4>❌ Build a statically linked screenrecord binary</h4><p>This would potentially allow a single modified binary to run on multiple Android OS versions. Unfortunately, it’s not possible to compile a statically linked screenrecord binary due to it’s many dynamic library dependencies in AOSP.</p><h3>What ended up working</h3><h4>✅ Edit a few bytes in the screenrecord binary</h4><p>Ultimately, we opted for an approach that allowed us to directly modify the screenrecord maximum time limit. Using binary rewriting, we were able to increase this limit to any duration we wanted.</p><h3>Just tell me how you did it already!</h3><p>Alright, now for the fun stuff:</p><p>The 3-minute limitation in the screenrecord command is hardcoded as a single constant in the <a href="https://cs.android.com/android/platform/superproject/main/+/main:frameworks/av/cmds/screenrecord/screenrecord.cpp;l=101;drc=09977ff16168166a2b4b3eb727ee7a8a4953de0b">AOSP source code</a>. That’s great, because it means it will be relatively easy to modify this value, even in the compiled binary.</p><pre>static const uint32_t kMaxTimeLimitSec = 180;       // 3 minutes</pre><h4>Finding the right bytes to modify</h4><p>We used a tool called <a href="https://rada.re/n/">Redare2</a> to help poke around in the screenrecording binary. Ramping up on this tool took a bit of time, but luckily there’s this cool new thing called ChatGPT that’s super helpful in these situations 😉.</p><p>So with our new friends Redare2 and ChatGPT, we were able to find a simple command that searches for the exact bytes we were after:</p><pre>r2 -q -c &quot;/x b4000000&quot; screenrecord</pre><p>The screenrecord argument is the path to the file we want to inspect. We pulled this particular binary off an Android device using:</p><pre>adb pull /system/bin/screenrecord</pre><p>But what’s all this other stuff? Here’s where ChatGPT is really helpful:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ebcD9DFuPboV0WFGqBE0rA.png" /></figure><p>So we’re searching the binary for this sequence of bytes: b4000000 . Why? This is the 4-byte little-endian hexidecimal representation of 180, which is the value of the kMaxTimeLimitSec constant we were interested in.</p><p><strong>If we can find where this constant value is defined, we can update those bytes to a different number!</strong></p><p>As it turns out, b4000000 appears multiple times in the binary. The left column lists the address of each occurrence:</p><pre># search for occurrences of 0xb4000000<br><br>$ r2 -qc &quot;/x b4000000&quot; screenrecord<br><br>0x00020854 hit0_0 b4000000<br>0x00015c79 hit0_1 b4000000<br>0x000169a2 hit0_2 b4000000<br>0x000183b6 hit0_3 b4000000<br>0x000199a5 hit0_4 b4000000<br>0x000199b6 hit0_5 b4000000<br>0x000199f7 hit0_6 b4000000<br>0x00019c8e hit0_7 b4000000<br>0x0001affa hit0_8 b4000000<br>0x0001b158 hit0_9 b4000000<br>0x0001b173 hit0_10 b4000000<br>0x0001c0f9 hit0_11 b4000000<br>0x0001d487 hit0_12 b4000000<br>0x00004d1c hit0_13 b4000000<br>0x000077ad hit0_14 b4000000<br>0x00007c9a hit0_15 b4000000<br>0x00007cff hit0_16 b4000000<br>0x0000814c hit0_17 b4000000<br>0x0000eaa7 hit0_18 b4000000<br>0x00010648 hit0_19 b4000000</pre><p>Luckily, the first entry (0x00020854) is the one we are looking for. We can verify this by searching for references to that address:</p><pre># analyze the binary, then list all references to 0x00020854<br><br>$ r2 -qc &quot;aaa; axt 0x00020854&quot; screenrecord<br><br>(nofunc) 0x15c6e [DATA:r--] mov dword [0x00020854], eax<br>(nofunc) 0x16344 [DATA:r--] mov r9d, dword [0x00020854]<br>(nofunc) 0x16cdc [DATA:r--] mov r15d, dword [0x00020854]</pre><p>The exact assembly here isn’t super important. What does matter is that yes, there are indeed instructions that reference the 4-byte value at 0x00020854. The same command does not yield any results for any of the other addresses listed.</p><p>Here’s what that tells us: 0x00020854 is the only address that both…</p><ol><li>…contains the 4-byte representation of the value 180, and</li><li>…is referenced by at least one instruction in the binary</li></ol><p>This alone gives us high confidence that we have the right address that corresponds to the kMaxTimeLimitSec constant. But as a final check, let’s take a look at the first instruction that references this address:</p><pre>(nofunc) 0x15c6e [DATA:r--] mov dword [0x00020854], eax</pre><p>We can use Radare2’s pd command to view the instruction right before that one:</p><pre># seek to 0x15c6e, then print 1 instruction before that address<br><br>$ r2 -qc &quot;s 0x15c6e; pd -1&quot; screenrecord<br><br>0x00015c69      e8126d0000     call sym.imp.atoi</pre><p>It’s a call to the sym.imp.atoi function. Looking back at the source, the only reference to atoi is in <a href="https://cs.android.com/android/platform/superproject/main/+/main:frameworks/av/cmds/screenrecord/screenrecord.cpp;l=1197-1205;drc=09977ff16168166a2b4b3eb727ee7a8a4953de0b">this part of the code</a>:</p><pre>case &#39;t&#39;:<br>    gTimeLimitSec = atoi(optarg);<br>    if (gTimeLimitSec == 0 || gTimeLimitSec &gt; kMaxTimeLimitSec) {<br>        fprintf(stderr,<br>                &quot;Time limit %ds outside acceptable range [1,%d]\n&quot;,<br>                gTimeLimitSec, kMaxTimeLimitSec);<br>        return 2;<br>    }<br>    break;</pre><p>And we see that kMaxTimeLimitSec is referenced there as expected.</p><h4>Rewriting the binary</h4><p>So we just did a lot of work to verify that 0x00020854 is the address we need to modify in the file. It currently holds the value 180 — Let’s update it to 3600 to see what happens!</p><pre># seek to 0x00020854, then write 3600(0x100E0000) to that address<br><br>r2 -q -c &quot;s 0x00020854; wx 0x100E0000&quot; -w screenrecord</pre><p>Now we have a local screenrecord binary that we hope has been updated to increase its time limit to 3600 seconds (1 hour). Let’s verify that:</p><pre># push the modified screenrecord binary to /data/local/tmp/<br>adb push ./screenrecord /data/local/tmp<br><br># make the file executable<br>adb shell chmod +x /data/local/tmp/screenrecord<br><br># print the help message<br>adb shell /data/local/tmp/screenrecord --help</pre><p>If you’ve done this sort of work before, you never expect this to behave as expected without a lot of debugging and trial and error. But to our surprise, this is what we saw on our first attempt:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lv4e85dsTCYmvsrNseqLiQ.png" /></figure><p>The usage message was updated with the modified value! We then validated that we could indeed record a video longer than the original 3-minute limit using the modified binary! 🥳🥳🥳</p><h4>Integrating into our infrastructure</h4><p>The last step for us was integrating the fix into our infrastructure. This was a matter of pushing the modified screenrecord binary to our Android devices before making them available to our device pool. In the end, a small change.</p><h3>Wrapping up</h3><p>This was an example of a very deep dive that resulted in a simple solution. We were especially relieved that, in the end, the fix required only a few lines of code changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*_uYWlnDBxwZgBtbFtg8RNA.png" /></figure><p>And of course — most importantly — we’re happy to share that we have completely removed the Android screen recordings limits on <a href="https://mobile.dev/">Maestro Cloud</a> 🙌</p><p>If you haven’t checked out <a href="https://mobile.dev/">Maestro</a> yet, we promise it will blow your mind. <a href="https://mobile.dev/">Get started here</a> and make sure to <a href="https://docsend.com/view/3r2sf8fvvcjxvbtk">Join us on Slack</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4839abc74aee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maestro Best Practices: Structuring your Test Suite]]></title>
            <link>https://medium.com/@leland_40592/maestro-best-practices-structuring-your-test-suite-54ec390c5c82?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/54ec390c5c82</guid>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Thu, 04 May 2023 15:41:15 GMT</pubDate>
            <atom:updated>2025-01-09T19:40:34.999Z</atom:updated>
            <content:encoded><![CDATA[<h4>Best practices on how to structure and organize your Maestro Test Suite</h4><p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*fmGqGCHvAKZNTRYzIu4sJQ.png" /></figure><p>Once you’ve familiarized yourself with the basics of Maestro, the next step is to start planning out what a full test suite looks like for your app. We’ll walk through this process and address some of the key questions you’ll likely run into:</p><ul><li>How do I decide what belongs in a single Flow vs multiple Flows?</li><li>How should I organize my Flows?</li><li>How can I run a different set of Flows in different circumstances?</li></ul><p>We’ll start with a general rule of thumb for breaking down your Flows:</p><h4><strong><em>A Flow should test a single user scenario</em></strong></h4><p>It might be tempting to test your entire app as a long sequence of commands under single Flow. Don’t do this! There are a number of ways this will make things harder for you:</p><ul><li>If any command fails, this will halt the entire test — you won’t get information about the rest of your app</li><li>You won’t be able to run your test cases in parallel, increasing execution time in CI</li><li>Your test results will show up as a single Flow result (even if you are testing many different parts of your app)</li></ul><p>Instead, break down your Flows into smaller scenarios that each represent a single scenario you’d like to verify. As is usually the case in these types of situations, this is more of an art than a science. You’ll need to decide on the granularity of your Flows based on the complexity of your app.</p><p>A good starting point is thinking about user intent. What is a user trying to accomplish in each scenario (eg. “Search for a item”, “Log in”, “Purchase a product”, “Add a comment”)? If your Flow is covering more than one user intent, it probably make sense to break it up into multiple Flows.</p><h4>Use subdirectories to organize your Flows</h4><p>To organize your Flow files, you can place related Flow files into subdirectories. You can choose the directory structure you like, but our recommendation is to group Flows by feature:</p><pre>.maestro<br>├── auth<br>│   ├── Login.yaml<br>│   └── Onboarding.yaml<br>├── checkout<br>│   ├── CheckoutWithCreditCard.yaml<br>│   ├── CheckoutWithGooglePay.yaml<br>│   └── CheckoutWithInvalidInfo.yaml<br>├── common<br>│   ├── OpenDeeplink.yaml<br>│   └── ScrollToSelected.yaml<br>└── search<br>    ├── FilterByCategory.yaml<br>    ├── Search.yaml<br>    ├── SearchHistory.yaml<br>    ├── SortByDate.yaml<br>    └── SortByPrice.yaml</pre><p>You’ll need to configure your <a href="https://maestro.mobile.dev/api-reference/configuration/workspace-configuration"><strong>config.yaml</strong></a> to specify the Flows you want to run. By default, Maestro will only run Flows at the root level of your Flow directory.</p><pre># config.yaml<br>flows:<br>  - auth/*<br>  - checkout/*<br>  - search/*</pre><p>Notice that we omitted the common/ directory above since it only holds utility Flows which shouldn’t be run as standalone Flows.</p><p>Alternatively, you can avoid updating your config.yaml every time you add a feature directory by using a more generic <a href="https://en.wikipedia.org/wiki/Glob_(programming)">file glob</a>. This does however require adding the util tag to every Flow in the common directory so we can <a href="https://maestro.mobile.dev/cli/tags#global-tags">exclude that tag from executing</a>:</p><pre># config.yaml<br>flows:<br>  - */*<br><br>excludeTags:<br>  - util</pre><p>Those were just a couple common patterns, but you are free to organize your Flow subdirectories as you please using a combination of flows, excludeTags, and includeTags.</p><h4>Use Flow tags to run different sets of Flows in different scenarios</h4><p>It’s often useful to maintain separate sets of Flows for different situations. For instance, you may want to run your entire test suite nightly, but only a subset of those Flows on every pull request or commit to your main branch. The easiest way to manage this behavior is using <a href="https://maestro.mobile.dev/cli/tags#global-tags"><strong>Flow Tags</strong></a>.</p><p>Let’s say you want to run your smoke tests on every pull request. First, tag each smoke test Flow with smokeTest (You can name the tag whatever you want):</p><pre>appId: com.example<br>tags:<br>  - smokeTest<br>---<br>- launchApp<br>...</pre><p>Then, you’ll be able to run just these flows by including the smokeTest tag when uploading to Maestro Cloud. The example below shows how you can configure this in a GitHub workflow. The last line is the relevant configuration:</p><pre>name:  Run Smoke Tests<br><br>on:<br>  pull_request:<br>    branches: [ main ]<br><br>jobs:<br>  build:<br>    runs-on: macOS-latest<br>    steps:<br>      - uses: actions/checkout@v2<br>      - name: Install Xcode<br>        uses: maxim-lobanov/setup-xcode@v1<br>        with:<br>          xcode-version: latest<br>      - run: xcodebuild -project MyApp.xcodeproj -scheme MyApp -destination &#39;platform=iOS Simulator,name=iPhone 11&#39;<br>      - uses: mobile-dev-inc/action-maestro-cloud@v1.2.3<br>        with:<br>          api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}<br>          app-file: &lt;app_name&gt;.app<br>          include-tags: smokeTest</pre><p>Or when running on the command line, use the --includeTags option:</p><pre>$ maestro test --includeTags smokeTest .maestro/<br>$ maestro cloud --includeTags smokeTest example.app/ .maestro/</pre><p>To run the full test suite, simply omit the include-tags/--includeTags configuration. Your nightly GitHub workflow might look something like the config below. Note that the include-tags key is not specified this time:</p><pre>name:  Run Nightly Test Suite<br>on:<br>  schedule:<br>    - cron: &#39;0 2 * * *&#39; # run at 2 AM UTC<br><br>jobs:<br>  build:<br>    runs-on: macOS-latest<br>    steps:<br>      - uses: actions/checkout@v2<br>      - name: Install Xcode<br>        uses: maxim-lobanov/setup-xcode@v1<br>        with:<br>          xcode-version: latest<br>      - run: xcodebuild -project MyApp.xcodeproj -scheme MyApp -destination &#39;platform=iOS Simulator,name=iPhone 11&#39;<br>      - uses: mobile-dev-inc/action-maestro-cloud@v1.2.3<br>        with:<br>          api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}<br>          app-file: &lt;app_name&gt;.app</pre><h4>Any other questions?</h4><p>This guide covered some of the most common questions we hear from team ramping up on Maestro, but we’d love to chat if you have any follow up questions! The quickest way to connect with the Mobile.dev team, is to <a href="https://docsend.com/view/3r2sf8fvvcjxvbtk"><strong>join our Slack community</strong></a> and post your question in the #maestro channel. You can also reach us via email at <strong>support@mobile.dev</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54ec390c5c82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing: Maintainable No-Code UI Automation for Mobile with Maestro Studio]]></title>
            <link>https://medium.com/@leland_40592/announcing-maintainable-no-code-ui-automation-for-mobile-with-maestro-studio-16bb0c42da3b?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/16bb0c42da3b</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[automation-testing]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 16:04:10 GMT</pubDate>
            <atom:updated>2025-01-09T19:41:20.391Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GMnk9vxVDSy2JkOCtesQ5Q.png" /></figure><p><strong>Today we are excited to announce the next evolution of Maestro Studio, which brings maintainable no-code UI automation to the Mobile ecosystem!</strong></p><p>The new ability to record Maestro Commands drastically reduces Flow authorship time, and more importantly enables <strong>anyone</strong> to write Maestro Flows!</p><p><a href="https://maestro.mobile.dev/getting-started/installing-maestro">Upgrade to the latest Maestro CLI</a> and run “maestro studio” to try it out!</p><h4><strong>Challenges with Existing Tooling</strong></h4><p>Before we dive into the announcement, let’s review the challenges with existing no-code tooling. There have been a number of attempts at no-code automation on mobile, but they each suffer from the same key issues:</p><ul><li><strong>Requires re-recording the whole test when something changes</strong></li><li><strong>Difficult to keep in sync with feature changes</strong></li><li><strong>Difficult to edit / tweak recorded tests</strong></li><li><strong>Difficult to run Flows as part of CI</strong></li></ul><p>Traditionally, no-code solutions focus on making writing tests <em>from the ground up</em> much easier — and to be fair, they usually do a good job of this. But the problem teams end up running into is this:</p><figure><img alt="Initial authorship of a test suite constitutes just 10% of the development cost. 90% of your team’s time will be spent on maintenance of those tests." src="https://cdn-images-1.medium.com/max/1024/1*AGikbMIEDwLb4k3kZA_dag.png" /></figure><p>We’ve embraced this reality by treating <strong>maintainability</strong> as a core design principle when building Maestro Studio. Today, we are excited to introduce you to the first solution for maintainable no-code Mobile UI automation.</p><h3>Maestro Studio</h3><p><strong>Meet the next evolution of Maestro Studio 🎉</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F792001232%3Fh%3D5a48d7c8f5%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F792001232%2F5a48d7c8f5&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1594062863-f646ffb078b5024094698b74b5c3b6854a6238d008161735c76c4a3552de0d87-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1379" frameborder="0" scrolling="no"><a href="https://medium.com/media/6ff33dcd4af9306b1a9b1d081ce1736f/href">https://medium.com/media/6ff33dcd4af9306b1a9b1d081ce1736f/href</a></iframe><h4>Runs Locally</h4><p>The first thing to note is that Maestro Studio runs against local mobile devices (iOS Simulator / Android Emulator / Device). This allows you to easily interact with your device to debug or set up a test case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*udvTN7hGjSid2dai9GKAOA.gif" /></figure><h4>Exporting Flow Files</h4><p>It’s straightforward to keep your recorded Flows in sync with any app features changes since Maestro Studio generates standard Maestro commands. Simply export or copy the commands, then commit the Flow file to version control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xX31TUpEf3zO2nQ17_VHeg.gif" /></figure><h4>Easy Test Editing</h4><p>No-code automation tooling often feels “high-stakes” in that any mistake forces you to re-record the entire test. Maestro Studio removes the stress of recording your Flow by allowing you to add, remove, and even reorder recorded commands as needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yw4zL9YiI0sKstmSCf03aw.gif" /></figure><h4>Option to Manually Type Commands</h4><p>Sometimes it’s useful (and/or necessary) to write out a command manually. Maestro Studio’s “<a href="https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop">REPL</a>” interface provides first-class support for inputting commands manually. This is also a huge help when trying out various Maestro commands on your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OlYknEczrPWTLv5Z4Wt43Q.gif" /></figure><h4>Inspecting UI Elements</h4><p>Maestro Studio can also surface a list of ways to interact with a given element. Right-click on the device screen to view a list of sample code snippets that you can copy over to your Flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-MfkIXJ9i5NyfF_xZMQuQ.gif" /></figure><h3>Running Recorded Flows on CI</h3><p>Whether you record your Flows using Maestro Studio or write them by hand, you’ll ultimately want to run them automatically. Since Maestro Studio generates standard Maestro Flows, you can easily run your Flows on CI using <a href="https://cloud.mobile.dev/"><strong>Maestro Cloud</strong></a>. Check out the documentation to learn how to <a href="https://cloud.mobile.dev/getting-started/integrate-into-ci">integrate your Flows into any CI workflow</a>.</p><figure><a href="https://cloud.mobile.dev/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytJMWM1ZwwCOm1pFOWbwGw.png" /></a></figure><h3>What’s Next?</h3><p>There are clear short-term improvements we’ll be looking into like autocomplete, GUI for editing commands, and more recordable gestures. But what we’re really excited about is the fundamental innovation that Maestro unlocks. Maestro’s structured, human-readable syntax makes it particularly well-suited to build on top of. Features like natural language-driven testing or 100% automatic testing are not as far off as you would think!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKaEoA8GEy42JCHjRuzi7w.png" /></figure><p>👋 Follow us on Twitter (<a href="https://twitter.com/mobile__dev">@mobile__dev</a>) for updates, and join 1000+ other Maestro users in our <a href="https://docsend.com/view/3r2sf8fvvcjxvbtk">community Slack channel</a>!</p><p>Learn more at <a href="https://mobile.dev/">mobile.dev</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16bb0c42da3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running your Maestro Flows on GitHub Actions]]></title>
            <link>https://medium.com/@leland_40592/running-your-maestro-flows-on-github-actions-fe2e016b7338?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe2e016b7338</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Thu, 15 Dec 2022 03:44:36 GMT</pubDate>
            <atom:updated>2025-01-09T19:41:40.959Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*hHI54k7ROgMjGdCNyMP6mg.png" /></figure><p>Maestro is compatible with all CI systems and provides native integrations with a number of common providers including GitHub Actions. You can start running your Flows in CI with just a few lines of configuration using the <a href="http://github.com/mobile-dev-inc/action-maestro-cloud">Maestro Cloud GitHub Action</a>.</p><h3>Create a Maestro Cloud account</h3><p>This doesn’t cost anything up front and you’ll have $10 of free credit each month to play around with the platform. If you haven’t already, start by creating a Maestro Cloud account: <a href="https://console.mobile.dev/signup">Create a Maestro Cloud Account</a></p><h3>Add your API key secret</h3><p>The GitHub Action will need to authenticate with Maestro Cloud. So the first step is to expose your API key as a GitHub “Repository Secret”.</p><p><strong>Grab your API key</strong></p><ol><li>Log in to <a href="https://console.mobile.dev/">Maestro Cloud Console</a>, click on your username in bottom left corner and click on View API Key</li><li>Copy your API Key and save it somewhere. You will need it in next steps!</li></ol><p><strong>Add your API key as a “Repository Secret”</strong></p><ol><li>Navigate to your GitHub repo and click on Settings in top nav bar.</li><li>In repository settings page click on Secrets -&gt; Actions. It will open Action Secrets page.</li><li>On Action Secrets page, click on New Repository Secret button. Use MAESTRO_CLOUD_API_KEY as the secret name and paste your API key from the previous step into the “Secret” value text box. Click “Add Secret” to add the secret.</li></ol><h3>Commit your Maestro Flows to your repository</h3><p>Create a .maestro/ directory at the root of your repository and commit your Flows there:</p><pre>&lt;root&gt;<br>├── .maestro/<br>│   ├── Login.yaml<br>│   ├── Add to Cart.yaml<br>│   └── Search.yaml</pre><p>It’s common to have some Flow files that are only meant to be executed as part of another Flow via the runFlow command. These &quot;subflows&quot; can be nested under a subdirectory to prevent them from running as a top-level Flow.</p><pre>&lt;root&gt;<br>├── .maestro/<br>│   ├── subflows/<br>│   │   └── MySubflow.yaml<br>│   ├── Login.yaml<br>│   ├── Add to Cart.yaml<br>│   └── Search.yaml</pre><h3>Update your GitHub Actions workflow</h3><p>Next, you’ll need to update your GitHub Actions workflow to add in the Maestro Cloud step. Here are a couple examples of working workflow files for Android and iOS:</p><p><strong>Android Workflow</strong></p><pre># .github/workflows/android.yaml<br><br>name: Build and upload to Maestro Cloud<br><br>on:<br>  push:<br>    branches: [ main ]<br>  pull_request:<br>    branches: [ main ]<br><br>jobs:<br>  maestro-cloud:<br>    runs-on: ubuntu-latest<br>    outputs:<br>      app: app/build/outputs/apk/debug<br>    steps:<br>      - uses: actions/checkout@v3<br>      - uses: actions/setup-java@v3<br>        with:<br>          java-version: 11<br>          distribution: &#39;temurin&#39;<br>      - run: ./gradlew assembleDebug<br>      - uses: mobile-dev-inc/action-maestro-cloud@v1.1.1<br>        with:<br>          api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}<br>          app-file: app/build/outputs/apk/debug/app-debug.apk</pre><p><strong>iOS Workflow</strong></p><pre>name:  Mobile Dev Action iOS<br><br>on:<br>  push:<br>    branches: [ main ]<br>  pull_request:<br>    branches: [ main ]<br><br>jobs:<br>  build:<br>    runs-on: macOS-latest<br>    steps:<br>      - uses: actions/checkout@v2<br>      - uses: actions/setup-xcode@v2<br>        with:<br>          xcode-version: 12<br>      - run: xcodebuild -project MyApp.xcodeproj -scheme MyApp -destination &#39;platform=iOS Simulator,name=iPhone 11&#39;<br>      - uses: mobile-dev-inc/action-maestro-cloud@v1.1.1<br>        with:<br>          api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}<br>          app-file: &lt;app_name&gt;.app</pre><p>The workflows above execute generally the same steps for each platform:</p><ul><li>For every push or pull_request to main branch trigger this job</li><li>Build the application</li><li>Upload the built application and Flow files to Maestro Cloud</li><li>Note the MAESTRO_CLOUD_API_KEY is the same secret you added to your Github repository earlier</li></ul><h3>That’s it!</h3><p>Check out the Maestro Cloud Action <a href="https://github.com/mobile-dev-inc/action-maestro-cloud">README</a> for more information on how to configure the step.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe2e016b7338" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing: Maestro Studio]]></title>
            <link>https://medium.com/@leland_40592/introducing-maestro-studio-96454c7ca98a?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/96454c7ca98a</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Tue, 13 Dec 2022 15:40:41 GMT</pubDate>
            <atom:updated>2025-01-09T19:41:45.255Z</atom:updated>
            <content:encoded><![CDATA[<h4>Your personal assistant to help write your Maestro Flows</h4><p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEuZ3AeXQSu5gNJKd1-bgQ.png" /></figure><h3>Community-Driven Innovation 🚀</h3><p>Last week, we proposed this feature in our community Slack channel: <strong>A visual interface that surfaces the exact Maestro commands needed to interact with your app’s UI.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ZLM64dyWwK_Gb4sMBJbHw.png" /></figure><p>This feature represents a major leap forward for Maestro users. But more importantly, it lays the foundation for a new generation of Mobile automation tooling. And all of this was directly driven by feedback from the community!</p><p>Today, we’re excited to announce a game-changing addition to the Maestro Ecosystem:</p><h3>Maestro Studio</h3><p>Meet your new favorite Maestro tool, <strong>Maestro Studio:</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F779795561%3Fh%3D353af3f2aa%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F779795561%3Fh%3D353af3f2aa&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1564997590-c98c0ddc2fdd31200293b0ca81580f392993d561c382474552397c2046158de9-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="780" frameborder="0" scrolling="no"><a href="https://medium.com/media/f5265a6b2972aa2ee3b433281e7925d8/href">https://medium.com/media/f5265a6b2972aa2ee3b433281e7925d8/href</a></iframe><p>Use Maestro Studio to instantly discover the exact commands needed to interact with your app.</p><p>Here’s how it works:</p><h4>Launch Maestro Studio</h4><p>Maestro Studio is built right into the Maestro CLI. Upgrade your CLI to the latest version, and run the command below to launch Maestro Studio in your browser:</p><pre>maestro studio</pre><p>Here’s what you’ll see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZdqRB2bHWrWREMa6GF76Tg.png" /></figure><h4>Visually Select a UI Element</h4><p>Click on the device screenshot to select a UI element. You can also search for an element by text or id.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPh8IE2Hbg7mxFnnNYLFqQ.png" /></figure><h4>Automatically Generated Examples</h4><p>Maestro Studio automatically generates examples of how you can interact the selected element. Click on an example to copy the command, then paste it right into your Flow file!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96GJyKeg3JRyY4xWkvAEPw.png" /></figure><h4>Can Maestro Studio just write my Flow for me?</h4><p>You read our minds! The north star is enabling the generation of a full Flow simply by clicking through your application 🤯.</p><p>Make sure to follow us on <a href="https://twitter.com/mobile__dev"><strong>Twitter</strong></a> and join us on <a href="https://docsend.com/view/3r2sf8fvvcjxvbtk"><strong>Slack</strong></a> to be the first to hear about any updates!</p><h3>What’s next for Maestro?</h3><p>We see Maestro, Maestro Cloud, and now Maestro Studio as the foundation for the next generation of mobile automation tooling. We’re going full speed ahead on our mission to fundamentally improve the tooling and experience of test authorship, maintenance, and execution. Thank you for being on this journey with us.</p><p>Learn more at <a href="https://www.mobile.dev/">mobile.dev</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96454c7ca98a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security Milestone — SOC 2 Type 2]]></title>
            <link>https://medium.com/@leland_40592/security-milestone-soc-2-type-2-2cca9d1e1967?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cca9d1e1967</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Thu, 08 Dec 2022 18:16:47 GMT</pubDate>
            <atom:updated>2025-01-09T19:41:49.442Z</atom:updated>
            <content:encoded><![CDATA[<h3>Security Milestone — SOC 2 Type 2</h3><p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5-8mQ-7h71i6Oat6zWeYzA.png" /></figure><p><strong>Today, we are excited to announce that we have issued our SOC 2 Type 2 Report.</strong></p><p>This report provides an external audit that demonstrates we are meeting the security commitments we have made to our users. Achieving this report is a major milestone for our company and shows our commitment to the security and confidentiality of our users’ data.</p><p>We are proud to have achieved this report with the help of Drata. With their assistance, we were able to streamline the process and ensure that our controls meet the highest standards.</p><p>At mobile.dev, we take the security and privacy of our users’ data very seriously. Issuing our SOC 2 Type 2 Report is just one way that we are working to protect the information that our users trust us with.</p><p>Visit our website to learn more about mobile.dev: <a href="https://www.mobile.dev/">www.mobile.dev</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cca9d1e1967" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing: “maestro record”]]></title>
            <link>https://medium.com/@leland_40592/introducing-maestro-record-a825cadaec21?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/a825cadaec21</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Fri, 02 Dec 2022 14:13:44 GMT</pubDate>
            <atom:updated>2025-01-09T19:42:33.505Z</atom:updated>
            <content:encoded><![CDATA[<h4>Record a beautiful video of your Maestro Flow with a single command</h4><p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*Xq0fIjix-zDmdpsNbQeUEA.png" /></figure><p>Since launching Maestro a few months ago, we’ve seen tons of Maestro screen recordings pop up on social media.</p><p>It’s usually the same setup: Flow output on one side and a Simulator or Emulator on the other. It’s a great way to showcase Maestro’s simplicity, and we’re stoked that users are excited as we are to showcase their Maestro Flows!</p><p>But we know from experience that setting up this sort of screen recording can be cumbersome. Here’s some of what you need to think about:</p><ul><li>Cleaning up your desktop for a clean recording</li><li>Sizing the terminal window correctly</li><li>Adjusting the terminal font size</li><li>Arranging the windows for the correct aspect ratio</li><li>Cropping the recording area to include the right padding</li><li>Trimming the start and end of the screen recording</li></ul><p>And the list goes on. At mobile.dev, we’re all about making mobile teams more efficient, so we’ve decided to make this process a whole lot easier.</p><h3>Introducing: “maestro record”</h3><p>Simply run the command below to render your Flow output and app screen recording into a beautifully formatted video:</p><pre>maestro record YourFlow.yaml</pre><p>Here’s an example of the final output:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F775621555%3Fh%3D736930f7f9%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F775621555%3Fh%3D736930f7f9&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1557227913-a321349c2ec90cc82653a91937205673befeeda8814402c06b5fde538127b62b-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/613c9735767f6d955c541d4b186d6844/href">https://medium.com/media/613c9735767f6d955c541d4b186d6844/href</a></iframe><p>You don’t need to worry about cleaning up your desktop or arranging your windows in any particular way. “maestro record” captures the raw Flow output and app screen recording, and then programmatically stitches them together into an mp4 file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*TTIR9EhHFZBrEHq4MMe2TA.png" /></figure><p>After your Flow runs, your video will begin rendering. This process usually takes a couple minutes. When your video is ready, a signed download url is printed to the terminal. Navigate to the link in your browser to download your video.</p><p><em>Note that the rendered video is sped up by 2x by default for a better viewing experience. We may make this configurable in the future.</em></p><p>We hope that “maestro record” encourages more folks to share their awesome Maestro Flows with the world. Give it a try today!</p><p>Learn more at <a href="https://www.mobile.dev/"><strong>mobile.dev</strong></a><strong><br></strong>Follow us on Twitter: <a href="https://twitter.com/mobile__dev"><strong>@mobile__dev</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a825cadaec21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maestro — Announcing JavaScript + HTTP Request Support]]></title>
            <link>https://medium.com/@leland_40592/maestro-announcing-javascript-http-request-support-b2db06e1db00?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2db06e1db00</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Thu, 01 Dec 2022 14:18:06 GMT</pubDate>
            <atom:updated>2025-01-09T19:42:25.095Z</atom:updated>
            <content:encoded><![CDATA[<h3>Maestro — Announcing JavaScript + HTTP Request Support</h3><h4>Run JavaScript and execute HTTP requests from your Maestro Flows</h4><p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*yDiZDygSVLXv8P-vpodLBg.png" /></figure><p>Maestro Flows have historically been written in pure YAML. This restriction enforces simple, declarative test definitions, which is a big part of why users are drawn to Maestro.</p><p>But there are some use cases that don’t fit well into the declarative world. Here are a few examples we’ve heard from real Maestro users:</p><ul><li>Execute an http request and input part of the response into a text field</li><li>Ensure that the sum of the prices of in a list match the total price</li><li>Ensure the label of a list item matches the title in its details screen</li></ul><p>These are valid use cases, but the logic would be difficult to encode into YAML syntax even if we considered the introduction of new Maestro APIs. To support these sorts of scenarios, we knew we needed a way to break out of the YAML world to express more complex ideas.</p><p>So today, we are excited to announce JavaScript support in Maestro Flows!</p><h3>JavaScript Support</h3><p><a href="https://maestro.mobile.dev/advanced/javascript"><strong>Full JavaScript Documentation</strong></a></p><p>Don’t worry — Maestro is not becoming a JavaScript framework. But we are opening up a small escape hatch to be used in specific scenarios where YAML is not a good fit.</p><p>Here’s how it works:</p><p>Everything within ${} blocks is evaluated as JavaScript, allowing you to insert dynamically computed values into any Maestro command:</p><pre>appId: com.example<br>env:<br>    MY_NAME: John<br>---<br>- launchApp<br>- inputText: ${1 + 1}               # Inputs &#39;2&#39;<br>- inputText: ${&#39;Hello &#39; + MY_NAME}  # Inputs &#39;Hello John&#39;<br>- tapOn: ${MY_NAME}                 # Taps on element with text &#39;John&#39;</pre><p>You can also run JavaScript files:</p><pre>- runScript: myScript.js</pre><p><em>Note: Your JavaScript code is evaluated in a sandbox for portability and security reasons. As a result, you only have access to a limited set of built in functions and you can’t access the filesystem.</em></p><p>An important use case we wanted to solve with JavaScript support is the ability to execute HTTP requests. So out-of-the-box, Maestro provides a set of simple HTTP JavaScript functions.</p><h3>HTTP Request Support</h3><p><a href="https://maestro.mobile.dev/advanced/javascript"><strong>Full HTTP Request Documentation</strong></a></p><p>Here’s an example that executes an HTTP GET request, parses the response, and types part of the output into a text field:</p><pre>// myScript.js<br>var response = http.get(&#39;https://api.example.com/getName&#39;);<br>output.firstName = json(response.body).first;</pre><pre># YourFlow.yaml<br>- runScript: myScript.js<br>- inputText: ${output.firstName}</pre><p>Here are the main concepts in the example above:</p><ul><li>http.post() is a built-in function that executes a POST request</li><li>json() is another built-in function that parses the response body into an Object</li><li>output is a built-in global Object variable where you can store computed values</li><li>inputText uses the stored output.firstName value as its text parameter</li></ul><p>With the introduction of JavaScript support and built-in HTTP functions, you can now easily interact with your backend APIs right from your Maestro Flows!</p><h3>Give it a try!</h3><p>Head to the documentation to get started with Maestro’s JavaScript support:</p><p><a href="https://maestro.mobile.dev/advanced/javascript"><strong>https://maestro.mobile.dev/advanced/javascript</strong></a></p><p>We’d love to hear your feedback on this feature. As always, the best place to reach us is on <a href="https://docsend.com/view/3r2sf8fvvcjxvbtk"><strong>Slack</strong></a> but you can also shoot us an email at <strong>hello@mobile.dev</strong>.</p><p>Follow us on Twitter for updates! <a href="https://twitter.com/mobile__dev"><strong>@mobile__dev</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2db06e1db00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tutorial: Getting Started With Maestro on Windows]]></title>
            <link>https://medium.com/@leland_40592/tutorial-getting-started-with-maestro-on-windows-9d17d6812c6d?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d17d6812c6d</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 18:32:04 GMT</pubDate>
            <atom:updated>2025-01-09T19:42:44.761Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QbAT2y3NIANI8beUYNvgyQ.png" /></figure><p>Maestro works great on Windows computers, but there are a few unique setup steps to be aware of. This article will walk you through the end-to-end steps for getting started with Maestro on a Windows machine.</p><h3>Steps</h3><ol><li>Install WSL2 (Window Subsystem for Linux)</li><li>Install Java 11</li><li>Install Maestro</li></ol><h3>1. Install WSL 2</h3><p>With recent Windows 11, Microsoft have made it pretty easy to install Windows Subsystem For Linux aka WSL</p><p>In order to install WSL, open Powershell As Administrator and run following command:</p><pre>wsl --install</pre><p>After running the above command, follow through instructions and restart the computer.</p><p>Install <a href="https://github.com/microsoft/terminal">Windows Terminal</a> application for refreshing terminal experience.</p><p>Set your linux username and password (Something that you will not forget).</p><p>Run following 2 commands to update your Ubuntu system. Enter password when prompted.</p><pre>sudo apt update<br>sudo apt upgrade</pre><h3>2. Install Java</h3><p>After restarting the system, open Terminal application and click on the dropdown to select Ubuntu. Type in following command:</p><pre>sudo apt install openjdk-11-jdk</pre><h3>3. Install Maestro</h3><p>Installing Maestro is now just a matter of running following command:</p><pre>curl -Ls &quot;https://get.maestro.mobile.dev&quot; | bash</pre><p><strong>TADA!</strong></p><p><strong>You have successfully installed Maestro in your Windows machine </strong>🙌</p><p>Check your maestro version using following command</p><pre>maestro --version</pre><h3>What Next?</h3><ul><li>Run an Android emulator (You can use <a href="https://developer.android.com/studio">Android Studio</a> to setup an Android emulator)</li><li><a href="https://maestro.mobile.dev/getting-started/writing-your-first-flow">Write your first flow</a></li><li>Check out the <a href="https://maestro.mobile.dev/">full documentation</a></li></ul><h3>Bonus Tips</h3><p>You can install adb into your WSL2 Ubuntu using following command</p><pre>sudo apt install adb</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d17d6812c6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get Started on Maestro Cloud in 5 minutes]]></title>
            <link>https://medium.com/@leland_40592/get-started-on-maestro-cloud-in-5-minutes-66f3c368192a?source=rss-b5f8fb397d60------2</link>
            <guid isPermaLink="false">https://medium.com/p/66f3c368192a</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Leland Takamine]]></dc:creator>
            <pubDate>Wed, 09 Nov 2022 16:58:04 GMT</pubDate>
            <atom:updated>2025-01-09T19:42:50.646Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Looking for the easiest way to test iOS, Android, and Web with a single platform? Check out </em><a href="https://www.robintest.com/"><strong><em>Robin — The new standard in Mobile and Web end-to-end testing</em></strong></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uNN8b74IClvOjyikBcScUQ.png" /></figure><p>If you aren’t already familiar with Maestro Cloud, check out the announcement blog post: <a href="https://blog.mobile.dev/introducing-maestro-cloud-4233d58852fb"><strong>Introducing: Maestro Cloud</strong></a>.</p><p>This article will walk you through running a Flow on Maestro Cloud from your local terminal. We recommend going through these steps to see the process working end-to-end before wiring into CI.</p><p>Alright — let’s get started!</p><h4><strong>1. Install the Maestro CLI</strong></h4><p>We’ll be using the maestro cloud command below, so start by <a href="https://maestro.mobile.dev/getting-started/installing-maestro"><strong>installing the Maestro CLI</strong></a> if you haven&#39;t already:</p><pre>curl -Ls &quot;https://get.maestro.mobile.dev&quot; | bash</pre><p>(On Windows? Head to <a href="https://maestro.mobile.dev/getting-started/installing-maestro/windows">the installation docs</a>)</p><h4><strong>2. Login to the CLI</strong></h4><p>Authenticate with mobile.dev on the command line using the following command:</p><pre>maestro login</pre><p>Follow the printed instructions to complete the login process.</p><h4><strong>3. Download the Samples</strong></h4><p>Use the download-samples command to download a sample app and Flow file to upload to Maestro Cloud:</p><pre>maestro download-samples</pre><p>You can of course choose to upload your own app and Flow file, but we recommend using the samples first to see how it works!</p><h4><strong>4. Run your Flow on Maestro Cloud</strong></h4><p>Use the maestro cloud command to run your flow Maestro Cloud. This command works the same whether you&#39;re running it locally or in CI.</p><pre># Android<br>cd ./samples<br>maestro cloud sample.apk android-flow.yaml</pre><pre># iOS<br>cd ./samples<br>maestro cloud sample.zip ios-flow.yaml</pre><h4><strong>5. View results in the console</strong></h4><p>A link to the Maestro Console console is printed out after your Flow is uploaded successfully. Click on the link to view the results of your upload. It may take a minute or so before your results are ready.</p><h3>Next Steps</h3><p>Check out the documentation below to wire Maestro Cloud into your CI workflow:</p><p><a href="https://cloud.mobile.dev/getting-started/integrate-into-ci"><strong>Maestro Cloud — Integrate into CI</strong></a></p><ul><li>Learn more at <a href="https://www.mobile.dev/"><strong>mobile.dev</strong></a></li><li>Follow us on Twitter for updates! <a href="https://twitter.com/mobile__dev"><strong>@mobile__dev</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66f3c368192a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>