mobile-dev-inc/maestro

Make Maestro faster by giving the option to skip helper APKs install/uninstall

Open

#1,096 opened on May 19, 2023

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Kotlin (6,111 stars) (306 forks)batch import
P3enhancementgood first issuemaestro cli

Description

Is your feature request related to a problem? Please describe. When running on lower end Android devices, Maestro can take a long time to start and to finish the test, since it's installing the APKs + uninstalling at the end

For instance, we use Flashlight to generate e2e performance reports based on several e2e test iterations and we recommend heavily the use of Maestro (https://docs.flashlight.dev/test/maestro) However the time bottleneck of running multiple test iterations is those install/uninstall

Describe the solution you'd like It'd be nice to have the option to skip APK install/uninstall to speed things up For instance

maestro test test.yaml --skipApkInstall

I'd be happy to raise a PR for that!

We could also add a maestro setup task that does the necessary setup before running a test

Contributor guide

Tech stack
kotlinandroid
Domain
mobiletestingcli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
KotlinAndroidMaestro codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the Maestro CLI argument parsing in `App.kt` or command classes. Identify where APK install/uninstall is triggered (likely in a setup or test command). Propose a ` skipApkInstall` flag to bypass those steps. Consider implementing a separate `setup` command as suggested. Review existing tests for CLI flags to maintain consistency.