search

watir / tap_watir

Watir for Mobile Devices (currently pre-beta status but in active development)
MIT License
17 stars 5 forks source link

Some new ideas for how to initialize the App #3

Closed titusfortner closed 6 years ago

titusfortner commented 6 years ago

So I'm thinking we want to open a browser on a mobile device differently from how we open an application:

TapWatir::MobileBrowser.new(opts) vs. TapWatir::App.new(opts)

Also thinking we should move away from the idea of caps and just put everything into a single Hash input for now.

In the future we might want to create some kind of Capabilities object to make things more strict.

titusfortner commented 6 years ago

@Githraine let me know what you think about this syntax. We probably need to find someone using both Watir & Ruby Appium right now to give feedback on these things as well.

titusfortner commented 6 years ago

Also of note, implementing the Appium code needs to be with ruby_lib_core not ruby_lib

Githraine commented 6 years ago

@titusfortner That makes sense to me for launching the App or Browser. One question that comes to mind is how will this handle a browser launched by a native app? We would want those transitions to be as seamless as possible.

titusfortner commented 6 years ago

Do you mean hybrid apps that have a Webview context, or do you mean driving both a native app and a mobile browser at the same time?

prakharrr commented 6 years ago

@Githraine how will this handle a browser launched by a native app?

I know in iOS there are 2 ways that this can be done. Do you mean opening a web browser inside the app(using a webView within a storyboard) or opening chrome/safari from within the app.

titusfortner commented 6 years ago

outdated