Mobile testing with Cucumber Appium and Ruby
https://appsierra.com/how-to-do-cross-platform-mobile-testing-with-cucumber-appium-and-ruby/
Folder structure
app: Where we put android and iOS apps inside their respective folders, getting app/android/app.apk and app/ios/app.ipa
config: Where we put the settings passed to the appium_lib, also in their respective folders config/android/appium.txt and config/ios/appium.txt
features: Inside the folder, we find the core of the application, which contains the elements of the views, the test scenarios, the page objects and steps of the tests. Inside also has the folder called support where we have some auxiliary classes for use.
rake_tasks: this is where much of the magic happens, where you can run a test for a particular platform with a simple command.
Config
The configuration is a very simple part and it is possible that you all are already familiar to everyone. The thing that was modified was the use of text files for the storage of these settings.
Inside the config/android folder was the appium.txt file:
Inside the config/ios folder was the file also with the name appium.txt:
Features
Inside the features folder, we find a folder structure and also the test scenarios, I’ll start by talking about the elements folder.
Elements
Within the elements folder, we find several YAML files. YAML is a human-readable data serialization format inspired by languages such as XML has the following structure.
These YAML files are divided by app screens. Thus facilitating the search for elements and being possible to implement the logic of the test, before the screen is ready.
Page Objects
Pages are an abstraction for creating page objects, where appium methods are paralleled with elements captured by us.
