Describe the bug
When running a test command with Maestro, the test runs around 6 seconds faster if Maestro Studio is open with the test device connected.
To Reproduce
Command:
flashlight test --bundleId com.pizzaapp --testCommand "MAESTRO_APP_ID=com.pizzaapp npx @perf-profiler/maestro@latest test .maestro/flows/Login.yaml"
Test file:
https://github.com/infinitered/ignite/blob/master/boilerplate/.maestro/flows/Login.yaml
Steps to reproduce the behavior:
npx ignite-cli@latest new PizzaApp --yes
yarn android
- Open Maestro Studio and select the device that you'll be running the test in
flashlight test --bundleId com.pizzaapp --testCommand "MAESTRO_APP_ID=com.pizzaapp npx @perf-profiler/maestro@latest test .maestro/flows/Login.yaml"
- Observe Average Test Runtime
- Close Maestro Studio
flashlight test --bundleId com.pizzaapp --testCommand "MAESTRO_APP_ID=com.pizzaapp npx @perf-profiler/maestro@latest test .maestro/flows/Login.yaml"
- Observe that Average Test Runtime is ~6s longer
Screenshots

Environment (please complete the following information):
- OS: macOS 26.0.1
- Flashlight Version: 0.18.0
- Android SDK platform tools version: Android Debug Bridge version 1.0.41 Version 36.0.0-13206524 Running on Darwin 25.0.0 (arm64)
- Test Framework: Maestro v2.0.3
- Share the bundle identifier of your app: com.pizzaapp
Additional context
This might be more of a Maestro issue. I just wanted to share it here just in case others were having similar issues with test runtime inconsistencies.
Describe the bug
When running a test command with Maestro, the test runs around 6 seconds faster if Maestro Studio is open with the test device connected.
To Reproduce
Command:
flashlight test --bundleId com.pizzaapp --testCommand "MAESTRO_APP_ID=com.pizzaapp npx @perf-profiler/maestro@latest test .maestro/flows/Login.yaml"Test file:
https://github.com/infinitered/ignite/blob/master/boilerplate/.maestro/flows/Login.yaml
Steps to reproduce the behavior:
npx ignite-cli@latest new PizzaApp --yesyarn androidflashlight test --bundleId com.pizzaapp --testCommand "MAESTRO_APP_ID=com.pizzaapp npx @perf-profiler/maestro@latest test .maestro/flows/Login.yaml"flashlight test --bundleId com.pizzaapp --testCommand "MAESTRO_APP_ID=com.pizzaapp npx @perf-profiler/maestro@latest test .maestro/flows/Login.yaml"Screenshots

Environment (please complete the following information):
Additional context
This might be more of a Maestro issue. I just wanted to share it here just in case others were having similar issues with test runtime inconsistencies.