robotframework-anywherelibrary to do cross platform testing(desktop browser,android,ios)

[Luis Lu]

Hi All,

I just wrote a lightweight library named robotframework-anywherelibrary, it's an option for robotframework users to do cross platform testing. 

Currently it's not mature enough, but promising. Hope you can do some advertisements and it can be listed in our robotframework.org !

Introduction

AnywhereLibrary is a cross platform(desktop browser,android,ios) testing library for Robot Framework that leverages the Selenium 2(WebDriver) libraries internally to control a web browser and appium as mobile test automation framework for use with native and hybrid app.

This library is specially suitable for handling SPA(single-page apps) with responsive design pattern. WIth this you only need generate a set of scripts to cover all platform(desktop browser ,android,ios).

On the other hand, no any UI test automation framework is made for your real busines. If this library can't be suitable for your business, it's highly recommed that you can fork this repository as your prototype for UI test automation. According to your real business requirements to customize your own anywherelibrary.

B.R.

Luis

[Luis Lu]

https://github.com/luisxiaomai/robotframework-anywherelibrary

https://pypi.python.org/pypi/robotframework-anywherelibrary/1.0.1

http://luisxiaomai.github.io/robotframework-anywherelibrary/doc/AnywhereLibraryDocument.html

[Andréa Perez]

Hello, 

I think your library is very interesting and is a tool that migh be very useful for Robot Framework. 

However, I find it no so practical that we have to configure the app path, app-package and app-application in the /AnywhereLibrary/cfg file. 

Would it be possible to set the parameters of the cfg file with a Keyword ? 

Thank you very much, 

And congratulations for this work, 

ANdréa Perez

[Tatu Aalto]

Ugh

I was looking your code and I am not sure why you did make some of the implementations. Currently I cannot use the AnywhereLibrary for my application testing. 

I did write small proof of concept and from that I am certain that I can use the underlying Appium and Selenium libraries in the way it is needed. But the PoC indicates that to get the AnywhereLibrary suitable for my needs, it would need go through re-factoring/rewrite.

Changes that I have in my mind:

1. I would not keep the xml file as base for the desired capabilities. Instead I would give it as an argument in the Initial Driver keyword. Most likely some sort of dictionary
2. For the interaction (Click, Type and so on) keywords, I would remove the waiting element to present logic. Making sure that element is present before interacting with it, should not be present in this level. I feel that in longer test runs, waiting element to be present before interacting with it, makes the test run last longer. 
3. My coding skills are not that great and sometimes I not get, why the logic is done in that way. Perhaps there is a good reason, but I did plan to simplify the logic. 
4. Write unit and acceptance test. 

Now how you feel about? I know that changes might be too big, because you may have other needs, which are different from my needs.  If you feel that changes that I propose are too big, then no hard feelings, I can understand it. 

In any case I would like to get the project started. So please let me know what you think. 

Br  Tatu