Replies: 2 comments
-
Potentially related to #911 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @yschimke! Similar motivation here as in #911 - we want maestro to be a blackbox testing framework. Thanks for the suggestion though! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there a good mechanism for running small plugins during the test, or is there value in supporting it?
Mobly has a bunch of predefined Snippets, that are callable from (python) scripts
https://github.com/google/mobly-bundled-snippets/tree/master/src/main/java/com/google/android/mobly/snippet/bundled
Building on top of https://github.com/google/mobly-snippet-lib
Then end up getting run in an instrumentation test with slightly elevated priviledges.
The equivelant feature in Maestro seem implemented by specific commands like setLocation
https://maestro.mobile.dev/reference/geo-location
maestro/maestro-proto/src/main/proto/maestro_android.proto
Line 64 in cf4ebf7
Is there any possibility to open these up? Say passing through Proto objects (which don't need to be known by the framework) and adding a plugin mechanism in the instrumentation test runner, to run these?
Beta Was this translation helpful? Give feedback.
All reactions