-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Hold and swipe/drag to reorder items #1203
Comments
+1, I find this feature really useful. This behavior appears just after login flow, hence it is a blocker for the app that I test. Lack of this feature forces me to go with Appium instead of Maestro. Hopefully it will be released asap |
Hey Simon, thanks for this great feature idea! What would be the API you'd like to see? An idea: appId: com.example.example
---
- launchApp
- longPressOnAndSwipeTo:
longPressOn: # accepts all params for longPressOn
swipe: # accepts all params for swipe
- assertVisible: ... This new hypothetical command would essentially be a mix of |
@bartekpacia Yes that sounds ideal! |
Just throwing an idea out there - wouldn't it be interesting to make the API more generic by representing "drag and drop" with start, middle and end points? We have a use case where we need to draw a complete circle, and this could be a flexible way to accommodate that and potentially other complex gestures. - gesture:
start: {x: 200, y: 400}
steps:
- {x: 250, y: 350}
- {x: 300, y: 400}
- {x: 250, y: 450}
- {x: 200, y: 400} Then it could be nice to define the initial tab event to be of type |
Yeah, totally. I think we'd also need a way to specify timeout between gestures, and how long a move between each two points should take. |
Of course, contributions are welcome! |
This is badly needed |
Is your feature request related to a problem? Please describe.
Some apps require holding and swiping/dragging to reorder items
Describe the solution you'd like
Some kind of ability to perform the above, e.g.
- longPressAndSwipeTo
The text was updated successfully, but these errors were encountered: