kraken-mobile 1.0.2 → 1.0.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: bc931cd463cf275dd15848f6f5751461275b72c8
-  data.tar.gz: 83c25030dcf11cd2bd403b2f31b76948c73fea07
+SHA256:
+  metadata.gz: e37d1eb17311d98492fa285efa6be0ad6b99d674b2510497983d91a2ac468068
+  data.tar.gz: af154d6ce69ee8cc48a51155152e4d5e47304d6c97e996a78c68d5c8c62f270f
 SHA512:
-  metadata.gz: 99bf9ad2a91215798445e26e16fe0377bd8ba6dc0cea908166592c23819362444e082120562743663e299004df7918667cec8454ff375778b79f5e354b7fc5b5
-  data.tar.gz: e4d9af2856eef33da3d740a1cbf642492383490947a00bae2c765f13553efa863c8739fdd95bb571e38b279c456bf67cfd59238c0c69da27e7c7a872c848fb39
+  metadata.gz: 67d048888f05bf62f93b1a59078a45df13ab1beb239eef464130085fbe5e90ad5066d96019f485e9c3ce29e1f86b2eaf549b9ecb6ea80fdd9c432da0e31674b7
+  data.tar.gz: a50c7e482c919e3654c73053d459fbb10b173c4b0886995bd09851492d008ae25fff2ce195d22d3b95a4b656bc01ab8d43ab942f90a2b01c48ccb96f4b4d8f98

data/README.md

@@ -1,86 +1,100 @@
 <p align="center">
-    <img src="https://raw.githubusercontent.com/ravelinx22/KrakenMobile/master/reporter/assets/images/kraken.png" alt="kraken logo" width="140" height="193">
-</p>
+    <img src="./reporter/assets/images/kraken.png" alt="kraken logo" width="140" height="193">
+<h1 align="center">Kraken</h1>
 
-<h3 align="center">Kraken Mobile</h3>
+Kraken is an open source automated android and web E2E testing tool that supports and validates scenarios that involve the inter-communication between two or more users. It works in a Black Box manner meaning that it is not required to have access to the source code of the application but instead it can be run with the APK (Android package file format) and web page URL. Kraken uses signaling for coordinating the communication between the devices using a file based protocol.
 
-<p align="center">Kraken is an open source automated android E2E testing tool that supports and validates scenarios that involve the inter-communication between two or more users. It works in a Black Box manner meaning that it’s not required to have access to the source code of the application but instead it can be run with the APK (Android package file format). Kraken uses signaling for coordinating the communication between the devices using a file based protocol.</p>
+**Kraken is partially supported by a Google Latin America Research Award (LARA) 2018**
 
-## Table of contents
+# Video
+[![krakenThumbnail](./reporter/assets/images/krakenThumbnail.jpg)](https://www.youtube.com/watch?v=hv5gFIpW3gM&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=1)
 
-- [Technologies](#technologies)
-- [Installation](#installation)
-- [Signaling](#signaling)
-- [Writing your first test](#writing-your-first-test)
-- [Kraken steps](#kraken-steps)
-- [Running your tests](#running-your-tests)
-- [Kraken Settings](#kraken-settings)
-- [Properties file](#properties-file)
+# Publications
 
-## Technologies
+- *“Kraken-Mobile: Cross-Device Interaction-based Testing of Android Apps”*, [William Ravelo-Méndez](https://ravelinx22.github.io/), [Camilo Escobar-Velásquez](https://caev03.github.io/), and [Mario Linares-Vásquez](https://profesores.virtual.uniandes.edu.co/mlinaresv/en/inicio-en/), *Proceedings of the 35th IEEE International Conference on Software Maintenance and Evolution ([ICSME’19](https://icsme2019.github.io/))*, Tool Demo Track, Cleveland, OH, USA, September 30th - October 4th, 2019, to appear 4 pages (52% Acceptance Rate) [[pdf](https://thesoftwaredesignlab.github.io/KrakenMobile/assets/pdfs/icsme19.pdf)][[bibtex](https://thesoftwaredesignlab.github.io/KrakenMobile/assets/pdfs/icsme19.bib)]
 
-Kraken uses [calabash-android](https://github.com/calabash/calabash-android) for running automated E2E tests in each device or emulator and [cucumber](https://github.com/cucumber/cucumber-ruby) for running your feature files written with Gherkin sintax. 
+# Technologies
 
-## Installation
+Kraken uses [calabash-android](https://github.com/calabash/calabash-android) and [selenium-webdriver](https://github.com/SeleniumHQ/selenium) for running automated E2E tests in each device or emulator and [cucumber](https://github.com/cucumber/cucumber-ruby) for running your feature files written with Gherkin sintax.
+
+# 🔨 Installation
 
 ### Prerequisites
 
-Kraken requires Ruby 2.20 or higher but we recommend using ~2.3 version. We use calabash-android as runner, you can check their prerequisites at this [link](https://github.com/calabash/calabash-android/blob/master/documentation/installation.md)
+Kraken requires Ruby 2.20 or higher but we recommend using ~2.3 version. We use calabash-android for mobile testing, you can check their prerequisites at this [link](https://github.com/calabash/calabash-android/blob/master/documentation/installation.md). For web testing we use selenium-webdriver, you can check their prerequisites as well at this [link](https://www.selenium.dev/selenium/docs/api/rb/).
+
+- Ruby at least version 2.3.1
+- Java JDK
+- Android SDK
+- Chromedriver (Version ~83 recommended) or Geckodriver (Only if you use Kraken web)
 
+You need to have configured ANDROID_HOME, ANDROID_HOME/platform_tools and JAVA_HOME in your environment variables.
 
-Installing and managing a Gem is done through the gem command. To install Kraken's gem run the following command
+Installing and managing Kraken Gem is done through the gem command. To install Kraken’s gem run the following command.
 
-    $ gem install kraken-mobile
+```
+$ gem install kraken-mobile
+```
 
+NOTE: If you are having trouble running Kraken in your Windows operating system refer to the this [guide](https://github.com/TheSoftwareDesignLab/KrakenMobile/blob/master/docs/WINDOWS_GUIDE.md) specifying steps to solve this issues.
 
-## Signaling
+# Signaling
 
-Signaling is a protocol used for the communication of two or more devices running in parallel. It’s based in the idea that each emulator or real device has a communication channel where he can receive signals sent from other devices which contain information or actions that are supposed to be executed. This type of protocol is commonly used in automated mobile E2E testing tools that validate scenarios involving the inter-communication and collaboration of two or more applications.
+Signaling is a protocol used for the communication of two or more devices running in parallel. It is based in the idea that each browser, emulator or real device has a communication channel where he can receive signals sent from other devices which contain information or actions that are supposed to be executed. This type of protocol is commonly used in automated mobile E2E testing tools that validate scenarios involving the inter-communication and collaboration of two or more applications.
 
-## Writing your first test
+# Writing your first test
 
 ### Generate cucumber feature skeleton
 
 First you need to generate the cucumber feature skeleton where your tests are going to be saved. To achieve this you should run `kraken-mobile gen`. It will create the skeleton in your current folder like this:
 
-    features
-    |_support
-    | |_app_installation_hooks.rb
-    | |_app_life_cycle_hooks.rb
-    | |_env.rb
-    |_step_definitions
-    | |_kraken_steps.rb
-    |_my_first.feature
+```
+features
+|_support
+| |_app_installation_hooks.rb
+| |_app_life_cycle_hooks.rb
+| |_env.rb
+|_step_definitions
+| |_mobile_steps.rb
+|_web
+| |_step_definitions
+| | |_web_steps.rb
+| |_support
+| | |_app_life_cycle_hooks.rb
+|_my_first.feature
+```
 
 ### Write a test
 
-The features goes in the features foler and should have the ".feature" extension.
-
-You can start out by looking at features/my_first.feature. You should also check calabash [predefined steps](https://github.com/calabash/calabash-android/blob/master/ruby-gem/lib/calabash-android/canned_steps.md).
+The features goes in the features foler and should have the “.feature” extension. You can start out by looking at `features/my_first.feature`. You should also check calabash [predefined steps](https://github.com/calabash/calabash-android/blob/master/ruby-gem/lib/calabash-android/canned_steps.md).
 
 ### Syntax
 
-In Kraken each feature is a test and each scenario within a feature is a test case that is run in a device. Each device is identified as an user and numbered from 1 to N. Ex: @user1, @user2, @user3. To check what is the number of a given device you should run `kraken-mobile devices`
+In Kraken each feature is a test and each scenario within a feature is a test case that is run in a device. Each device is identified as an user and numbered from 1 to N. Ex: @user1, @user2, @user3. To check what is the number of a given device you should run `kraken-mobile devices`.
 
-    List of devices attached
-    user1 - emulator-5554 - Android_SDK_built_for_x86
-    user2 - emulator-5556 - Android_SDK_built_for_x86
+```
+List of devices attached
+user1 - emulator-5554 - Android_SDK_built_for_x86
+user2 - emulator-5556 - Android_SDK_built_for_x86
+```
 
 After identifying what number each device has, you can write your test case giving each scenario the tag of a given device like so:
 
-    Feature: Example feature
+```
+Feature: Example feature
 
-      @user1
-      Scenario: As a first user I say hi to a second user
-        Given I wait
-        Then I send a signal to user 2 containing "hi"
+  @user1
+  Scenario: As a first user I say hi to a second  user
+  Given I wait
+  Then I send a signal to user 2 containing "hi"
 
-      @user2
-      Scenario: As a second user I wait for user 1 to say hi
-        Given I wait for a signal containing "hi"
-        Then I wait
+  @user2
+  Scenario: As a second user I wait for user 1  to say hi
+  Given I wait for a signal containing "hi"
+  Then I wait
+```
 
-## Kraken steps
+# Kraken steps
 
 Kraken offers two main steps to help synchronizing your devices.
 
@@ -88,41 +102,139 @@ Kraken offers two main steps to help synchronizing your devices.
 
 To wait for a signal coming from another device for 10 seconds that is Kraken default timeout use the following step.
 
-    Then /^I wait for a signal containing "([^\"]*)"$/
+```
+Then /^I wait for a signal containing "([^\"]*)"$/
+```
 
 To wait for a signal coming from another device for an specified number of seconds use the following step
 
-    Then /^I wait for a signal containing "([^\"]*)" for (\d+) seconds$/
+```
+Then /^I wait for a signal containing "(  [^\"]*)" for (\d+) seconds$/
+```
 
 To send a signal to another specified device use the following step
 
-    Then /^I send a signal to user (\d+) containing "([^\"]*)"$/
+```
+Then /^I send a signal to user (\d+) containing "([^\"]*)"$/
+```
 
 ### Signaling functions
 
-Kraken internal implementation of the signaling steps use the following functions.
-
-#### readSignal(channel, content, timeout)
+Each device has an internal Kraken implementation of the signaling steps using the following functions.
 
-Waits for a signal with the specified content in the channel passed by parameter. This functions waits for the specified number of seconds in the timeout parameter before throwing an exception.
+```
+read_signal(content, time_out)
+```
 
-**Note: The channel parameter has to be the number of a device such as @user1, @user2, @userN**
+Waits for a signal with the specified content. This functions waits for the specified number of seconds in the timeout parameter before throwing an exception if specified.
 
-#### writeSignal(channel, content)
+```
+write_signal(signal)
+```
 
-Writes content to a channel passed by parameter.
+Writes signal content to a device inbox.
 
-**Note: The channel parameter has to be the number of a device such as @user1, @user2, @userN**
+# 📱Kraken Mobile
 
 ## Running your tests
 
 To run your test:
 
-    kraken-mobile run <apk>
+```
+$ kraken-mobile run <apk>
+```
 
 Kraken with the help of Calabash-Android will install an instrumentation along with your app and will start your tests in all devices connected (Check Kraken Settings section in order to learn how to specify in what devices your tests should be run).
 
-## Kraken Settings
+## 🦍 Mobile Monkey execution
+
+Kraken offers the possibility of generating random GUI events by using Android ADB monkey as well as its own implementation based in the idea of sending and reading random signals.
+
+### Android’s ADB Monkey
+
+To execute ADB monkey Kraken offers the following command specifying the number of events to be executed:
+
+```
+Then I start a monkey with (\d+) events
+```
+
+### Kraken’s own monkey
+
+Kraken extended the ADB monkey behavior by executing GUI events only in buttons and clickable views or inputs by offering the following command:
+
+```
+Then I start kraken monkey with (\d+) events
+```
+
+## XML snapshot
+
+Kraken makes it possible to save the XML presented by the current view in a specific device, this is convenient to identify view ids, asserting the correct XML is presented after an action has being completed or running static analyzing tools.
+
+### Saving the snapshot
+
+To save the snapshot of the current view, Kraken offers the following step specifying where the file is going to be saved:
+
+```
+Then I save device snapshot in file with path "([^\"]*)"
+```
+
+# 🌎 Kraken Web
+
+Kraken is extended to run also in web browsers and orchestrate the communication with other browsers running different websites or mobile applications that are being executed on physical devices or emulators. With the help of ChromeDriver/Geckodriver, selenium-webdriver and Cucumber we run test scenarios using Gherkin syntax as well as Kraken predefined signaling steps described before.
+
+## Specifying a web user in a test
+
+To specify that user is going to be run in a web browser instead of a mobile device you need to tag the scenario with @web. If a scenario is not tagged with @web Kraken will assume that is a mobile user and will attempt to run all steps in a mobile manner.
+
+```bash
+Feature: Example feature
+
+  @user1 @web
+  Scenario: As a first user I say hi to a second  user
+	Given I navigate to page "https://www.gmail.com/"
+    Then I send a signal to user 2 containing "hi"
+
+  @user2 @web
+  Scenario: As a second user I wait for user 1  to say hi
+    Given I wait for a signal containing "hi"
+	Then I navigate to page "https://www.gmail.com/"
+```
+
+This scenario will open two web browsers and execute the signaling between them.
+
+## Web steps
+
+To see a list of all web steps available in Kraken, visit the following [link.](https://github.com/TheSoftwareDesignLab/KrakenMobile/blob/master/docs/WEB_STEPS.md)
+
+## Executing web only scenarios
+
+To run a test that only contains web users and as a result does not require an APK file, run the following command:
+
+```
+$ kraken-mobile run
+```
+
+Kraken with the help of selenium-webdriver will start all required browsers and run your test scenario.
+
+## Specifying in what browser Kraken will run
+
+Kraken uses ChromeDriver and Chrome as default web browser but provides support for Firefox and Geckodriver. To specify that your test is going to be run in Firefox, specify the environment variable BROWSER when running your tests as follows:
+
+```bash
+$ BROWSER=firefox kraken-mobile run
+```
+
+**Note: Make sure that you have Geckodriver and Firefox installed previously.**
+
+## 🦍 Web Monkey execution
+
+Kraken has implemented it's own monkey behavior by executing random GUI events in buttons, clickable views and inputs by offering the following command:
+
+```
+Then I start kraken monkey with (\d+) events
+```
+
+# Kraken Settings
 
 Kraken uses kraken_mobile_settings.json to specify in what devices the tests should be run.
 
@@ -130,38 +242,102 @@ Kraken uses kraken_mobile_settings.json to specify in what devices the tests sho
 
 The following command will show you the available connected devices or emulators and let you choose which ones you want to use.
 
-    kraken-mobile setup
+```
+$ kraken-mobile setup
+```
 
 ### Run tests with settings file
 
-    kraken-mobile run <apk> --configuration=<kraken_mobile_settings_path>
+```
+$ kraken-mobile run <apk> --configuration=<kraken_mobile_settings_path>
+```
+
+# 🗯 Extended Kraken functionalities
+
+In the following sections we provide specification for shared functionality between Kraken mobile and web as well as some examples of Kraken in action.
 
-## Properties file
+# Properties file
 
 Kraken uses properties files to store sensitive data such as passwords or api keys that should be used in your test cases.
 
 ### Generate properties file
 
-The properties files should be a manually created json file with the following structure.
+The properties files should be a manually created JSON file with the following structure.
 
-    {
-      "@user1": {
+```
+{
+    "@user1": {
         "PASSWORD": "test"
-      },
-      "@user2": {
+    },
+    "@user2": {
         "PASSWORD": "test2"
-      }
     }
-    
+}
+```
+
 ### Use properties file in your test
 
 You can use the specified properties using the following sintax.
 
-    @user1
-    Scenario: As a kjkhdkjds
-        Given I wait
-        Then I see the text "<PASSWORD>"
+```
+@user1
+Scenario: As a user
+    Given I wait
+    Then I see the text "<PASSWORD>"
+```
 
 ### Run tests with settings file
 
-    kraken-mobile run <apk> --properties=<kraken_mobile_properties_path>
+```
+kraken-mobile run <apk> --properties=<kraken_mobile_properties_path>
+```
+
+# Use fake strings in tests
+
+Kraken offers a Fake string generator thanks to the Ruby gem [Faker](https://github.com/faker-ruby/faker), the list of supported faker types are listed as follows:
+
+- Name
+- Number
+- Email
+- String
+- String Date
+
+### Use a faker in a test
+
+Kraken keeps a record of every Fake string generated, thats why each string will have an id associated. To generate a Faker string you need to follow the structure “$FAKERNAME_ID”.
+
+```
+@user1
+Scenario: As a user
+    Given I wait
+    Then I enter text "$name_1" into field with id "view"
+```
+
+### Reusing a fake string
+
+As mentioned before, Kraken keeps record of every string generated with an id given to each string, this gives you the possibility of reusing this string later in your scenario. To reuse a string you can you need to append a $ character to the fake string as follows:
+
+```
+@user1
+Scenario: As a user
+    Given I wait
+    Then I enter text "$name_1" into field with id "view"
+    Then I press "add_button"
+    Then I should see "$$name_1"
+```
+
+# Examples
+
+
+| Application  | Video | Feature File | Steps Definition | Properties file | Settings File | Report Link |
+|:-------------|:-------------|:-------------|:------------------|:-------|:-------|:-------|
+| Infinite Words | [video](https://www.youtube.com/watch?v=4lX7mO80w-4&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=3&t=0s)|[.feature](/examples/infinite-words/infinite_words.feature)|--- | ---  | ---  | [report](/examples/infinite-words/report/index.html) |
+| QuizUp | [video](https://www.youtube.com/watch?v=2mhZVTK0r6k&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=4&t=1s) | [.feature](/examples/quizup/quizup.feature)|[stepsDef](../gh-pages/examples/quizup/step_definitions/kraken_steps.rb) | --- |  --- | [report](/examples/quizup/report/index.html)  |
+| Spotify/Shazam | [video](https://www.youtube.com/watch?v=7AKsfY1KFX0&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=5&t=0s) | [.feature](/examples/shazam/shazam.feature)|[stepsDef](../gh-pages/examples/shazam/step_definitions/kraken_steps.rb) | [.json](/examples/shazam/kraken_properties.json) |  [.json](/examples/shazam/kraken_mobile_settings.json) | [report](/examples/shazam/report/index.html)  |
+| Spunky | [video](https://www.youtube.com/watch?v=WOhRWkdFaVk&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=6&t=25s) | [.feature](/examples/spunky/spunky.feature)|[stepsDef](../gh-pages/examples/spunky/step_definitions/kraken_steps.rb) | --- |  --- | [report](/examples/spunky/report/index.html)  |
+| Picap | [video](https://www.youtube.com/watch?v=RozQrmH_Z5k&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=7&t=3s) | [.feature](/examples/picap/picap.feature)|[stepsDef](../gh-pages/examples/picap/step_definitions/kraken_steps.rb) | [.json](/examples/picap/kraken_properties.json) |  --- | [report](/examples/picap/report/index.html)  |
+| AskFM | [video](https://www.youtube.com/watch?v=d9Gbdx8kFX8&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=8&t=0s) | [.feature](/examples/askfm/askfm.feature)|[stepsDef](../gh-pages/examples/askfm/step_definitions/kraken_steps.rb) | --- |  --- | [report](/examples/askfm/report/index.html)  |
+| Stick Men Fight | [video](https://www.youtube.com/watch?v=36OJKNj0nSo&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=9&t=4s) | [.feature](/examples/stick/stick.feature)|--- | --- |  --- | [report](/examples/stick/report/index.html)  |
+| Tic Tac Toe | [video](https://www.youtube.com/watch?v=F9pDJDYsL_w&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=10&t=2s) | [.feature](/examples/tictactoe/tictactoe.feature)|[stepsDef](../gh-pages/examples/tictactoe/step_definitions/kraken_steps.rb) | --- |  --- | [report](/examples/tictactoe/report/index.html)  |
+| Tumblr | [video](https://www.youtube.com/watch?v=eqFej2uJz4k&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=11&t=3s) | [.feature](/examples/tumblr/tumblr.feature)|[stepsDef](../gh-pages/examples/tumblr/step_definitions/kraken_steps.rb) | [.json](/examples/tumblr/kraken_properties.json) |  --- | [report](/examples/tumblr/report/index.html)  |
+| F3 | [video](https://www.youtube.com/watch?v=vESh6Jyp-so&list=PLF5U8kfVgRcJ3RCHt7cWmwlqN93brbVW-&index=12&t=0s) | [.feature](/examples/f3/f3.feature)|[stepsDef](../gh-pages/examples/f3/step_definitions/kraken_steps.rb) | [.json](/examples/f3/kraken_properties.json) |  --- | [report](/examples/f3/report/index.html)  |

data/bin/kraken-mobile

@@ -1,91 +1,88 @@
 #!/usr/bin/env ruby
 
-require File.join(File.dirname(__FILE__), "kraken-mobile-helpers")
-require File.join(File.dirname(__FILE__), "kraken-mobile-setup")
-require File.join(File.dirname(__FILE__), "kraken-mobile-calabash-android")
-$LOAD_PATH << File.expand_path("../../lib", __FILE__)
-require 'kraken-mobile'
+require File.join(File.dirname(__FILE__), 'kraken_mobile_helpers')
+require File.join(File.dirname(__FILE__), 'kraken_mobile_setup')
+require File.join(File.dirname(__FILE__), 'kraken_mobile_calabash_android')
+$LOAD_PATH << File.expand_path('../lib', __dir__)
+require 'kraken_mobile'
 require 'kraken-mobile/constants'
 
 #-------------------------------
 # AGV reader helper
 #-------------------------------
 
-def read_specified_runner
-  runner_command = ARGV.select { |arg| arg.include?("--runner=") }.first
-  if runner_command
-    formatted_runner_command = runner_command.strip.downcase
-    formatted_runner_command.slice!("--runner=")
-    formatted_runner_command
-  end
-end
+def read_configuration
+  configuration_command = ARGV.select do |arg|
+    arg.include?('--configuration=')
+  end.first
+  return if configuration_command.nil?
 
-def read_specified_protocol
-  protocol_command = ARGV.select { |arg| arg.include?("--protocol=") }.first
-  if protocol_command
-    formatted_protocol_command = protocol_command.strip.downcase
-    formatted_protocol_command.slice!("--protocol=")
-    if KrakenMobile::Constants::SUPPORTED_PROTOCOLS.include?(formatted_protocol_command)
-      formatted_protocol_command
-    else # Protocol not supported.
-      raise "Specified protocol not supported."
-    end
-  else # If protocol not specified use file based as default.
-    KrakenMobile::Constants::FILE_PROTOCOL
-  end
+  configuration_command = configuration_command.strip.downcase
+  configuration_command.slice!('--configuration=')
+  configuration_command
 end
 
-def read_configuration
-  configuration_command = ARGV.select { |arg| arg.include?("--configuration=") }.first
-  if configuration_command
-    configuration_command = configuration_command.strip.downcase
-    configuration_command.slice!("--configuration=")
-    configuration_command
-  end
+def read_user_entered_properties_path
+  properties_command = ARGV.select { |arg| arg.include?('--properties=') }.first
+  return if properties_command.nil?
+
+  properties_command = properties_command.strip.downcase
+  properties_command.slice!('--properties=')
+  properties_command
 end
 
-def read_properties
-  properties_command = ARGV.select { |arg| arg.include?("--properties=") }.first
-  if properties_command
-    properties_command = properties_command.strip.downcase
-    properties_command.slice!("--properties=")
-    properties_command
-  end
+#-------------------------------
+# Helpers
+#-------------------------------
+
+def user_entered_apk_path
+  return nil if ARGV.first.nil?
+
+  first_argument = ARGV.first
+  return nil if first_argument.start_with?('--') # Is argument parameter not apk
+
+  File.expand_path(first_argument)
 end
 
 #-------------------------------
 # Command reader
 #-------------------------------
 
-if ARGV.length == 0
-    print_usage
+if ARGV.length.zero?
+  print_usage
 else
   cmd = ARGV.shift
   case cmd
-    when 'version'
-      require 'kraken-mobile/version'
-      puts KrakenMobile::VERSION
-    when 'devices'
-      require 'kraken-mobile/helpers/devices_helper/manager'
-      print_devices
-    when 'setup'
-      kraken_setup
-    else
-      runner_command = read_specified_runner()
-      protocol = read_specified_protocol()
-      configuration = read_configuration()
-      properties = read_properties()
-      if runner_command
-          case runner_command
-            when KrakenMobile::Constants::CALABASH_ANDROID
-              require File.join(File.dirname(__FILE__), "kraken-mobile-calabash-android")
-              handle_calabash_android(cmd, protocol, configuration, properties)
-            else
-              raise "Specified runner not supported."
-          end
-      else # If runner not specified use calabash android as default.
-        require File.join(File.dirname(__FILE__), "kraken-mobile-calabash-android")
-        handle_calabash_android(cmd, protocol, configuration, properties)
-      end
+  when 'version'
+    require 'kraken-mobile/version'
+    puts KrakenMobile::VERSION
+  when 'devices'
+    require 'kraken-mobile/helpers/devices_helper/manager'
+    print_devices
+  when 'setup'
+    KrakenSetup.new.run
+  when 'gen'
+    ensure_java_installed
+    ensure_android_sdk_installed
+
+    scaffold_folder_structure
+  when 'resign'
+    ensure_java_installed
+    ensure_android_sdk_installed
+
+    require 'calabash-android/helpers'
+    puts 'Resigning APK with Calabash-Android'
+    ensure_apk_is_specified
+    resign_apk(user_entered_apk_path)
+  when 'run'
+    ensure_java_installed
+    ensure_android_sdk_installed
+
+    require File.join(File.dirname(__FILE__), 'kraken_mobile_calabash_android')
+    configuration = read_configuration
+    user_entered_properties_path = read_user_entered_properties_path
+    handle_calabash_android(configuration, user_entered_properties_path)
+  else
+    print_usage
   end
 end