Add start session command to increase speed of tests

[Almouro]

Proposed changes

feat:Add start session command to increase speed of tests

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 (can take ~20s on low end devices)

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

This PR introduces a start-session command:

• you start it in one tab and it should do the setup necessary, including uninstalling/installing APKs
• then if you do maestro test in another tab, setup won't be done again, and the tests will be fast ⚡

How it works

I was surprised by how easy it was to do and kudos for that 👏 You guys did a fantastic job there ♥️
The start-session command allows us to keep an active session open. Subsequent test command will find the session active in SessionStore and use it.
Then openDriver will be set to false, and the AndroidDriver won't run the open() function which does all the heavy setup.
Sadly this isn't the case for iOS, so we don't have it working out of the box.

Potentially breaking shards?

⚠️ I had to remove 2 lines of code: I have to be honest, I have to be honest, I didn't manage to understand their purpose 😓. So I'd love some help from @sdfgsdfgd or @igorsmotto to know why they're needed. 🙏

For reference, I've run a "shard" test with ./maestro test -s 2 tests including some launchApp and it worked for me. Likely I've missed a use-case.

Testing

• Tested locally + in our AWS Device farm CI
• Also added an e2e test script

Normal behavior	With active session ⚡
Screen.Recording.2024-08-09.at.5.24.32.PM.mov	Screen.Recording.2024-08-09.at.5.29.50.PM.mov

Issues fixed

Fixes #1096

[Almouro]

As mentioned, I had to remove 2 lines of code: I have to be honest, I didn't manage to understand their purpose. 😓
So I'd love some help from @sdfgsdfgd or @igorsmotto to know why they're needed. 🙏

I've tested maestro test -s 2 tests locally (including some launchApp) and didn't run into any issues, but likely I've missed something.

Here the issue is that since maestro test has found an active session, it didn't "open" the Android driver since it doesn't need to.
But this condition would force it to reopen when using launchApp which defeats the purpose of maestro start-session

[bartekpacia]

What a great pull request @Almouro! 🎉

Thanks a ton! I'll take a look at it the next week.

PS Don't bother with test-cloud failing, it's expected for external contributions.

[bartekpacia]

Do I understand correctly that this is Android-only atm?

[Almouro]

@bartekpacia indeed,
probably a bit more work would be needed on iOS, since the iOS driver isn't the one responsible for starting the XCTestInstaller it seems

[bartekpacia]

Thanks for confirming! Feature parity across platforms is very important for us, so we cannot merge it as is.