sunomono 0.2.0.pre

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: f748b83e9bf8d3ac0915d62eea3116a31d22f553
+  data.tar.gz: d50894040a6bd70af0d64bc35b997b49ca0e8c11
+SHA512:
+  metadata.gz: 8577fe27235665dd2ce17b5b6279fd75e2df01db093e4f00e3a349c4420ef630fa90eed3ec4ff7ee5fa5d3c7f626992653138c351e88c8b4bb6a4d0afac8bd52
+  data.tar.gz: 695e55f0e463ed575748ac496bc5f98a328c33a24db5a89d114efbb53b3eda53362dd5b3977d4ee0720f138bca7c786839e449440eacbf4af34ed7e888c981a4

data/.gitignore

@@ -0,0 +1,17 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log
+.irb-history
+.DS_Store
+.idea/

data/Gemfile

@@ -0,0 +1,9 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in sunomono.gemspec
+gemspec
+
+gem 'thor'
+gem 'i18n'
+gem 'json'
+gem 'gherkin'

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2014 oscartanner
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,157 @@
+
+##[DEPRECATION] 
+
+This gem has been renamed to sunomono and will no longer be supported. Please switch to sunomono as soon as possible.
+
+ > See: https://rubygems.org/gems/sunomono
+   
+ > And: https://github.com/concretesolutions/sunomono
+
+# Sunomono
+
+
+A simple gem to generate all files needed in a project that will support calabash for both Android and iOS.
+
+iOS Build script works only with iOS SDK 9.2 or newer
+
+[Calabash](http://calaba.sh/) uses cucumber to support functional tests in Android and iOS and has one gem for each Platform:
+
+  > calabash-android (for Android) [(link)](https://github.com/calabash/calabash-android)
+  
+  > calabash-cucumber (for iOS) [(link)](https://github.com/calabash/calabash-ios)
+
+The project structure is based on [this site](http://rubygemtsl.com/2014/01/06/designing-maintainable-calabash-tests-using-screen-objects-2). The structure is based on three layers: features, steps and screens.
+
+  1. Features: Contains all the features of the project, this features are Platform independent and will run for Android and iOS tests;
+  2. Steps: Contains all the steps implementations. This steps are Platform independent and will run for Android and iOS tests;
+  3. Screens: Contains all the Android and iOS screens. A screen must contain an identification, the declaration of all the elements of the screen and the declaration of its actions. This layer is Platform dependent. This occurs because, in almost every project, the identification of the elements varies between the Platforms. One example is that in Android almost all elements have an id, but in iOS the most common is to identify the elements by accessibility label. The Platform dependent screens must have the same name and same methods signatures. This will allow your steps to be unique between platforms
+
+  > One example of this structure can be found in the generated files (see Usage) on the file base_steps.rb. This file implements some common steps to help you start your tests and show you how to uses the Platform dependent screens
+  
+  > In my experience with tests I saw some cases that we will need to test features that are Platform dependent, like screens that send SMS which will only apper in Android apps. When this happen, the generated structure has Features and Steps that are Platform dependent and can be found inside the folder `features/android` and `features/ios` of the generated project.
+
+## Installation
+
+Install it as:
+
+    $ gem install sunomono
+
+## Usage
+
+In the terminal, type for help:
+
+```
+  suno
+```
+
+Or
+
+```
+  sunomono
+```
+
+To see the gem version type:
+
+```
+  suno version
+```
+
+To generate a project that support both Android and iOS features type:
+
+```
+  suno new ProjectName
+```
+
+This command will create a folder named ProjectName in the current directory and will create all the needed files. This gem support localizations. To create a localized project, in Portuguese, type:
+
+```
+  suno new ProjectName --lang=pt
+```
+
+If you use Windows, to avoid encoding problems, run the following command in cmd:
+
+```
+[HKEY_CURRENT_USER\Software\Microsoft\Command Processor] "AutoRun"="chcp 65001"
+```
+
+
+  > The default language is English ('en'). The elements of Gherkin such as Given, When, Then, And, Scenario will be translated to all Gherkin supported languages, but this gem has just a few translation files (see that in folder: `lib/sunomono/locales`). 
+  
+  > **Sunomono doesn't support your mother language?** No problem. Fork it, create your yml translation file, uses the en.yml file as a template. Translate it and make a pull request. There are only 15 lines to be translated, this will take no time.
+  
+  > **Want to know how to name your translation yml file?** See the Gherkin supported languages [here](https://github.com/cucumber/gherkin/blob/master/lib/gherkin/i18n.json) for reference.
+
+Once the project is created, open its folder (`cd ProjectName`) and run `bundle install`
+
+  > Remember to fix the calabash-cucumber version on the Gemfile. When updating the calabash-cucumber gem version you need to update the Calabash framework that was embedded on your iOS code. So, my suggestion is to update it manually. [In this page](https://github.com/calabash/calabash-ios/wiki/B1-Updating-your-Calabash-iOS-version) you can find more information on how to update the Calabash framework.
+
+
+There are nine generators that are responsible to create the templates for Features, Step definitions and Screens.
+
+**The generators commands ONLY WORK in the ROOT FOLDER of the project**.
+
+####Features
+
+```
+  suno generate feature FeatureName
+```
+The feature generator will create a Platform independent feature and its files. So this command will create the FeatureName.feature file inside the folder `feature`, the file FeatureName_steps.rb inside the folder `features/step_definitions`, the files FeatureName_screen.rb inside the folders `features/android/screens` and `features/ios/screens`.
+  
+  
+```
+  suno generate android-feature AndroidFeatureName
+  suno generate ios-feature iOSFeatureName
+```
+The aFeature and iFeature generator will create an Platform dependent feature. For example, the aFeature generator will create the AndroidFeatureName.feature file inside the folder `features/android/features`, the file AndroidFeatureName_steps.rb inside the folder `features/androd/step_definitions` and the screen file AndroidFeatureName_screen.rb inside the folder `features/android/screens`.
+
+
+Don't forget about internationalization. All the generators accept the option `--lang=pt` or with some other language.
+
+####Steps
+
+```
+  suno generate step StepName
+```
+The step generator will create a Platform independent step file named StepName_steps.rb in the folder `features/step_definitions`
+
+  
+```
+  suno generate android-step AndroidStepName
+```
+The android-step generator will create an Android step file named AndroidStepName_steps.rb in the folder `features/android/step_definitions`
+
+
+```
+  suno generate ios-step iOSStepName
+```
+The iStep generator will create an iOS step file name iOSStepName_steps.rb in the folder `features/ios/step_definitions`
+
+
+
+####Screens
+
+```
+  suno generate screen ScreenName
+```
+The screen generator will create both Platform dependent screens in the folders `features/android/screens` and `features/ios/screens`.
+
+
+```
+  suno generate android-screen AndroidScreenName
+  suno generate ios-screen iOSScreenName
+```
+The android-screen and ios-screen will create only the Android and iOS dependent screens respectively.
+
+## Continuous Integration (CI)
+
+The project contains a lot of scripts that will help you to configure you CI server.
+
+> Documentation under development.
+
+## Contributing
+
+1. Fork it ( https://github.com/concretesolutions/cs-bdd/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create a new Pull Request

data/Rakefile

@@ -0,0 +1 @@
+require 'bundler/gem_tasks'

data/bin/suno

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require 'sunomono'
+Sunomono::SunomonoRunner.start

data/bin/sunomono

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require 'sunomono'
+Sunomono::SunomonoRunner.start

data/lib/aws/android/app_installation_hooks.rb

@@ -0,0 +1,30 @@
+require 'calabash-android/management/app_installation'
+
+AfterConfiguration do |config|
+  FeatureMemory.feature = nil
+end
+
+Before do |scenario|
+  @scenario_is_outline = (scenario.class ==
+    Cucumber::Ast::OutlineTable::ExampleRow)
+  scenario = scenario.scenario_outline if @scenario_is_outlinel
+
+  feature = scenario.feature
+  if FeatureMemory.feature != feature || ENV['RESET_BETWEEN_SCENARIOS'] == '1'
+    if ENV['RESET_BETWEEN_SCENARIOS'] == '1'
+      log 'New scenario - reinstalling apps'
+    else
+      log 'First scenario in feature - reinstalling apps'
+    end
+
+    uninstall_apps
+    install_app(ENV['TEST_APP_PATH'])
+    install_app(ENV['APP_PATH'])
+    FeatureMemory.feature = feature
+    FeatureMemory.invocation = 1
+  else
+    FeatureMemory.invocation += 1
+  end
+end
+
+FeatureMemory = Struct.new(:feature, :invocation).new

data/lib/aws/android/app_life_cycle_hooks.rb

@@ -0,0 +1,13 @@
+require 'calabash-android/management/adb'
+require 'calabash-android/operations'
+
+Before do |scenario|
+  start_test_server_in_background
+end
+
+After do |scenario|
+  if scenario.failed?
+    screenshot_embed
+  end
+  shutdown_test_server
+end

data/lib/aws/ios/01_launch.rb

@@ -0,0 +1,43 @@
+require 'calabash-cucumber/launcher'
+
+# You can find examples of more complicated launch hooks in these
+# two repositories:
+#
+# https://github.com/calabash/ios-smoke-test-app/blob/master/CalSmokeApp/features/support/01_launch.rb
+# https://github.com/calabash/ios-webview-test-app/blob/master/CalWebViewApp/features/support/01_launch.rb
+
+module Calabash::Launcher
+  @@launcher = nil
+
+  def self.launcher
+    @@launcher ||= Calabash::Cucumber::Launcher.new
+  end
+
+  def self.launcher=(launcher)
+    @@launcher = launcher
+  end
+end
+
+Before do
+  launcher = Calabash::Launcher.launcher
+  options = {
+    timeout: 3000
+  }
+
+  launcher.relaunch(options)
+end
+
+After do |scenario|
+  # Calabash can shutdown the app cleanly by calling the app life cycle methods
+  # in the UIApplicationDelegate.  This is really nice for CI environments, but
+  # not so good for local development.
+  #
+  # See the documentation for QUIT_APP_AFTER_SCENARIO for a nice debugging workflow
+  #
+  # http://calabashapi.xamarin.com/ios/file.ENVIRONMENT_VARIABLES.html#label-QUIT_APP_AFTER_SCENARIO
+  # http://calabashapi.xamarin.com/ios/Calabash/Cucumber/Core.html#console_attach-instance_method
+  if launcher.quit_app_after_scenario?
+    calabash_exit
+  end
+end
+

data/lib/helpers/sunomono_helpers.rb

@@ -0,0 +1,136 @@
+# -*- coding: utf-8 -*-
+require_relative 'zip_helpers'
+
+def create_feature_file(name, platform = nil)
+  # options used to generate the file in the template function
+  opts = { name: camelize(name) }
+
+  # If platform is not nil than the feature is OS dependent
+  file_path = ''
+  if platform.nil?
+    file_path = File.join(FileUtils.pwd, 'features', "#{name.downcase}.feature")
+    opts[:platform] = ''
+  else
+    file_path = File.join(
+      FileUtils.pwd, 'features', platform.downcase, 'features',
+      "#{name.downcase}.feature"
+    )
+    opts[:platform] = platform
+  end
+
+  # Thor creates a file based on the templates/feature.tt template
+  template('feature', file_path, opts)
+end
+
+def create_steps_file(name, platform = nil)
+  # options used to generate the file in the template function
+  opts = { name: camelize(name) }
+
+  # If platform is not nil than the step is OS dependent
+  file_path = nil
+  if platform.nil?
+    file_path = File.join(
+      FileUtils.pwd, 'features', 'step_definitions',
+      "#{name.downcase}_steps.rb"
+    )
+    opts[:platform] = ''
+  else
+    file_path = File.join(
+      FileUtils.pwd, 'features', platform.downcase, 'step_definitions',
+      "#{name.downcase}_steps.rb"
+    )
+    opts[:platform] = platform
+  end
+
+  # Thor creates a file based on the templates/steps.tt template
+  template('steps', file_path, opts)
+end
+
+def create_screen_file(name, platform)
+  # options used to generate the file in the template function
+  opts = { name: camelize(name), platform: platform }
+
+  # Thor creates a file based on the templates/screen.tt template
+  template('screen',
+           File.join(
+             FileUtils.pwd, 'features', platform.downcase, 'screens',
+             "#{name.downcase}_screen.rb"
+           ), opts)
+end
+
+def camelize(string)
+  camelized = ''
+
+  string.split('_').each do |s|
+    camelized += s.capitalize
+  end
+
+  camelized
+end
+
+def in_root_project_folder?
+  # Looks if the user is in the root folder of the project
+  if !Dir.exist?(File.join(FileUtils.pwd, 'features', 'android', 'features')) ||
+     !Dir.exist?(File.join(FileUtils.pwd, 'features', 'ios', 'features'))
+    puts 'Please run this command on the root folder of the project'
+    exit 1
+  end
+
+  true
+end
+
+def create_zip_folder(dir)
+  file_name = "#{Time.now.strftime('%Y%m%d%H%M%S')}_specs.zip"
+  zf = ZipFileGenerator.new(dir, file_name)
+  zf.write
+  say_status(:create, file_name)
+end
+
+# Looks for special chars in the specs folder
+def special_chars_in_exported_path?
+  entries = `grep -inrE 'á|â|ã|é|ê|í|ó|õ|ô|ú|ç' . --exclude-dir={.git,screenshots,config,support,test_servers} --exclude='*.zip'`
+  if entries.count("\n") > 0
+    puts_special_chars_error_message(entries)
+    exit 1
+  end
+end
+
+def puts_special_chars_error_message(entries)
+  puts <<-EOF
+There are special chars in your specs.
+This can block AWS Device Farm execution.'
+Entries found:
+#{entries}
+
+To skip this validation use: '--skip-char-validation'
+Exiting..."
+EOF
+end
+
+# Copies all folders and files from specs that are valid in AWS context
+def copy_all_project_files(dir)
+  directory FileUtils.pwd, dir,
+            exclude_pattern: /(.git|.DS_Store|.irb-history|.gitignore|.gitkeep|screenshot|.apk|.zip)/
+  # Replacing launcher files to avoid problems with AWS Device Farm
+  copy_file File.join(File.dirname(__FILE__), '..', 'aws',
+                      'android', 'app_installation_hooks.rb'),
+            File.join(dir, 'features', 'android',
+                      'support', 'app_installation_hooks.rb'),
+            force: true
+  copy_file File.join(File.dirname(__FILE__), '..', 'aws',
+                      'android', 'app_life_cycle_hooks.rb'),
+            File.join(dir, 'features', 'android',
+                      'support', 'app_life_cycle_hooks.rb'),
+            force: true
+  copy_file File.join(File.dirname(__FILE__), '..', 'aws',
+                      'ios', '01_launch.rb'),
+            File.join(dir, 'features', 'ios',
+                      'support', '01_launch.rb'),
+            force: true
+end
+
+def create_screen_shot_dirs(dir)
+  Dir.mkdir File.join(dir, 'screenshots')
+  Dir.mkdir File.join(dir, 'screenshots', 'ios')
+  Dir.mkdir File.join(dir, 'screenshots', 'android')
+end