sunomono 0.2.0.pre

data/lib/helpers/zip_helpers.rb

@@ -0,0 +1,49 @@
+require 'zip'
+
+# This is a simple example which uses rubyzip to
+# recursively generate a zip file from the contents of
+# a specified directory. The directory itself is not
+# included in the archive, rather just its contents.
+#
+# Usage:
+#   directoryToZip = "/tmp/input"
+#   outputFile = "/tmp/out.zip"
+#   zf = ZipFileGenerator.new(directoryToZip, outputFile)
+#   zf.write()
+class ZipFileGenerator
+  # Initialize with the directory to zip and the location of the output archive.
+  def initialize(input_dir, output_file)
+    @input_dir = input_dir
+    @output_file = output_file
+  end
+
+  # Zip the input directory.
+  def write
+    entries = Dir.entries(@input_dir)
+    entries.delete('.')
+    entries.delete('..')
+    io = Zip::File.open(@output_file, Zip::File::CREATE)
+
+    write_entries(entries, '', io)
+    io.close
+  end
+
+  # A helper method to make the recursion work.
+  private
+
+  def write_entries(entries, path, io)
+    entries.each do |e|
+      zip_file_path = path == '' ? e : File.join(path, e)
+      disk_file_path = File.join(@input_dir, zip_file_path)
+      if File.directory?(disk_file_path)
+        io.mkdir(zip_file_path)
+        subdir = Dir.entries(disk_file_path)
+        subdir.delete('.')
+        subdir.delete('..')
+        write_entries(subdir, zip_file_path, io)
+      else
+        io.get_output_stream(zip_file_path) { |f| f.puts(File.open(disk_file_path, 'rb').read) }
+      end
+    end
+  end
+end

data/lib/skeleton/.gitignore

@@ -0,0 +1,9 @@
+.irb-history
+reports/*
+test_servers/*
+.DS_Store
+screenshot*.png
+screenshots/android/*
+!screenshots/android/.*
+screenshots/ios/*
+!screenshots/ios/.*

data/lib/skeleton/Gemfile

@@ -0,0 +1,7 @@
+# Gemfile to help setting up the initial development environment
+source 'https://rubygems.org'
+
+gem 'calabash-common'
+gem 'calabash-android', '~> 0.7'
+gem 'calabash-cucumber', '~> 0.19'
+gem 'sunomono', '~> 0.2'

data/lib/skeleton/README.md

@@ -0,0 +1,165 @@
+#Getting Started 
+
+## Ruby
+  
+  There is a lot of ways of installing ruby, one is using RVM (http://rvm.io/rvm/install):
+  
+  Install RVM stable with ruby: 
+
+  ```
+  $ \curl -sSL https://get.rvm.io | bash -s stable --ruby
+  ```
+  
+  After this, include the following lines in you `~/.bashrc` file.
+  
+  ```
+  export PATH="$PATH:$HOME/.rvm/bin" # Add RVM to PATH for scripting
+  [[ -s $HOME/.rvm/scripts/rvm ]] && source $HOME/.rvm/scripts/rvm
+  ```
+
+# Android
+
+## Installing the Gems
+
+  Install the following gems
+
+  ```
+  gem install calabash-common calabash-android
+  ```
+
+  **Warning!**
+  
+  The gem **`calabash-android`** can install the beta version of the cucumber gem.
+  This gem brokes the execution of the calabash. After the installation of calabash-android, check your installed gems with the command `gem list | grep cucumber` and install the stable version of the cucumber gem (command: `gem install cucumber`) and remove the beta version (command: `gem uninstall cucumber`), if that is the case.
+
+## Running the tests
+  To run the android tests, you need to:
+  
+  1. Open the Android AVD
+  2. Open the terminal on the tests folder
+  3. Execute the command:
+  
+  ```
+    calabash-android run features/app-QA.apk -p android
+  ```
+  
+
+  > To run in a computer with more than one emulator or device, use the command:
+  >
+  >```
+  >  ADB_DEVICE_ARG=emulator-5554 calabash-android run features/app-QA.apk -p android
+  >```
+  >
+  >Given that 'emulator-5554' is one of the returns of the command `$ adb devices` on the terminal
+
+
+  > To run on all connected devices, run the script `run_tests_all_devices.sh`, located on the `config/scripts/android` folder of the project
+
+  > **!! IMPORTANT !!** 
+
+  > Remember to export the WORKSPACE variable with the path of the cloned test repository
+  
+  > Remember to pass the APK path as the parameter of the script
+  > 
+  > ```
+  > ./config/scripts/android/run_tests_all_devices.sh PATH_OF_APK_FILE
+  >```
+
+
+## Calabash Terminal
+
+The calabash terminal allows you to run the calabash commands without being on a test context
+To open the calabash terminal, you need to:
+
+  1. Open the Android AVD
+  2. Open the terminal on the tests folder
+  3. Execute the command:
+  
+  ```
+    calabash-android console features/app-QA.apk -p android
+  ```
+  
+  4. Run the commands
+  
+  ```
+    reinstall_apps
+    start_test_server_in_background
+  ```
+  
+  5. Run the commands you want to.
+
+# iOS
+
+## Installing the Gems
+
+  Install the following gems
+
+  ```
+  gem install calabash-common calabash-cucumber
+  ```
+  
+## Configuring the iOS project
+
+  1. Run the command `pod install`
+  2. Run the command `calabash-ios setup` and follow the instructions
+  3. Make sure that the signing is a wildcard
+
+
+## Running the tests
+  To run the iOS tests in a device, you need to:
+  
+  1. Open the terminal on the tests folder
+  2. Compile the project to create the .app file with the command 
+  
+  ```
+  ./config/scripts/ios/build_app.sh xcworkspace_path TargetName-cal iphoneos8.1 ConfigurationName
+  ```
+  
+        PS.1: TargetName-cal is the name of the target created with the command `calabash-ios setup`
+        PS.2: iphoneos8.1 is the sdk for devices, for emulatores use iphonesimulator8.1
+        PS.3: Configuration name can be Dev, Debug, Release, Prod or any other configuration build
+        PS.4: The path to the .app file is the last output line of the above command
+
+  3. To execute one feature, run the command
+  
+  ```
+    APP_BUNDLE_PATH=AppFilePath DEVICE_TARGET=DeviceUUID DEVICE_ENDPOINT=CalabashServerEndpointDevice cucumber -p ios
+  ```
+  
+  4. To execute all the features in the configured devices run the script
+  
+  ```
+    ./config/scripts/ios/run_tests_all_devices.sh AppFilePath
+  ```
+  
+      PS.: Remember to configure all the connected devices on the file `./config/scripts/ios/devices`.
+           In this file you need to inform the device UUID, the device IP with the calabash server port and a name to identify this device on the reports. Remember to leave an empty line at the end of the file and to split the informations using pipes.
+
+## Calabash Terminal (Device)
+
+The calabash terminal allows you to run the calabash commands without being on a test context
+To open the calabash terminal, you need to:
+
+  1. Connect the device
+  2. Open the terminal on the tests folder
+  3. Execute the command:
+  
+  ```
+    APP_BUNDLE_PATH=AppFilePath DEVICE_TARGET=DeviceUUID DEVICE_ENDPOINT=CalabashServerEndpointDevice calabash-ios console
+  ```
+  
+  4. Run the command
+  
+  ```
+    start_test_server_in_background
+  ```
+  
+  5. Run the commands you want to.
+
+## Pitfalls
+
+  1. Always build the project with the device connected
+  2. Ensure that the device is enabled to Development and the UI Automations is enabled on the Developer menu (Settings)
+  3. If the device in pin locked, ensure that it is unlocked. If there is no pin, the calabash will automatically unlock the device
+  4. Ensure that the device WIFI is enabled and it is accessible from the computer that is starting the tests. The calabash server works sending commands to the device by the network.
+  5. Always run the target -cal on the Xcode one first time to see if the target is ok and running. The calabash-ios gem cannot print errors of execution, but Xcode can.

data/lib/skeleton/config/cucumber.yml

@@ -0,0 +1,7 @@
+# config/cucumber.yml
+##YAML Template
+---
+android: PLATFORM=android SCREENSHOT_PATH=screenshots/android/ -r features/support -r features/android -r features/step_definitions --exclude features/ios
+
+
+ios: PLATFORM=ios SCREENSHOT_PATH=screenshots/ios/ -r features/support -r features/ios -r features/step_definitions --exclude features/android

data/lib/skeleton/config/email/template.html

@@ -0,0 +1,14 @@
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <title>Project Name - Sunomono _OS_ - _STATUS_TITLE_</title>
+  </head>
+  <body>
+    <center>
+      <h1>Continuous Integration</h1>
+        <h2>Job Status: _JOB_NAME_, build number: #_BUILD_NUMBER_</h2>
+        Hello. I'm here to let you know that the tests <strong>_STATUS_</strong>.<br>
+        To view the reports, click <a href="http://jenkins_url/reports/_JOB_NAME_/_BUILD_NUMBER_">here.</a><br>
+    </center>
+  </body>                                                                                                                                  
+</html>

data/lib/skeleton/config/load_classes.rb

@@ -0,0 +1,31 @@
+# Choosing the platform using two environment vars that are mandatory for
+# calabash-ios console execution.
+# If they are not set, then we are executing a calabash android console
+# otherwise, if they are set, then we are execution calabash ios console 
+if ENV['APP_BUNDLE_PATH'].nil? && ENV['DEVICE_TARGET'].nil?
+  platform = 'android'
+else
+  platform = 'ios'
+end
+
+puts "Loading #{platform} classes..."
+
+features_path = File.join(File.expand_path('.', Dir.pwd), 'features')
+
+# Loading the support ruby files
+Dir[File.join(features_path, 'support', '*.rb')].each do |file|
+  # We can't load hook files in calabash console context
+  load file unless file.include? 'hooks.rb'
+end
+
+platform_path = File.join(features_path, platform)
+
+# Loading all ruby files in the base screen path
+Dir[File.join(platform_path, '*.rb')].each do |file|
+  load file
+end
+
+# Loading all screens files
+Dir[File.join(platform_path, 'screens', '*.rb')].each do |screen|
+  load screen
+end

data/lib/skeleton/config/scripts/android/run_tests_all_devices.sh

@@ -0,0 +1,41 @@
+#!/bin/bash
+# ----------------------------------------------------------------------------
+# Uncomment the next line to enable debug
+# set -x
+#
+# $1 -> parameter with the name of the apk
+# $2 -> parameter to indicates the tapume to run. Can be null and can have other 2 values: must or should
+
+## CODE BEGIN  #############################################################
+[ $# -lt 1 ] && echo "Wrong number of parameters." && exit 1
+
+# Counting the number of lines returned from the command adb devices
+# This command will return at least 2 as result, because of one header line and one empty line at end
+# So if the result is less than or equal 2, it means that there are no devices or emulators connected
+number_of_devices=$(adb devices | wc -l)
+[ $number_of_devices -le 2 ] && echo "There are no devices or emulators connected!" && exit 1
+
+echo Inicio da execução: $(date)
+
+# Creating the reports folder for the html format
+reports_path="$WORKSPACE/reports-cal"
+mkdir $reports_path
+
+for device in $(adb devices | grep "device$" | cut -f 1)
+do
+  cd $WORKSPACE
+  # Creates the reports folder
+  mkdir "$reports_path"/"$device"
+
+  {
+      ADB_DEVICE_ARG=$device calabash-android run $1 -p android SCREENSHOT_PATH="$reports_path"/"$device"/ -f 'Calabash::Formatters::Html' -o "$reports_path"/"$device"/reports.html -f junit -o "$reports_path"/"$device"
+      # Calabash has a problem with images relative path, the command above will replace all the images path on the
+      # html report file to be a relative path
+      sed -i.bak 's|'"$reports_path"/"$device"/'||g' "$reports_path"/"$device"/reports.html
+  }&
+
+done
+wait
+
+echo Fim da execução: $(date)
+## CODE END  #############################################################

data/lib/skeleton/config/scripts/android/start_emulators.sh

@@ -0,0 +1,52 @@
+#!/bin/bash
+# Author: Victor Nascimento
+
+bash stop_emulators.sh 
+
+# Suffix name of the AVD
+SUFFIX="CALABASH_AVD_4."
+
+# All $SUFFIX emulators are started
+for AVD in ${HOME}/.android/avd/${SUFFIX}*.avd
+do
+    # remove any locks that were left
+    rm "$AVD/*.lock" 2> /dev/null
+    # takes only the name of the AVD
+    echo $AVD
+    AVD="$(basename ${AVD/.avd/})" 
+    echo starting "$AVD"... 
+    emulator -wipe-data -gpu on -noaudio -scale 0.5 -no-boot-anim -accel on -avd "$AVD" -qemu -m 1024 -enable-kvm &
+done
+
+sleep 15
+# lists all emulators with adb and check for its online state
+
+# finds the port through adb emulator name
+for porta in $(adb devices -l | grep ^emulator | cut -d " " -f 1 | cut -d - -f 2)
+do
+    echo Searching for emulator PID for port: ${porta}
+    pid=$(netstat -tlnp 2> /dev/null | grep "$porta" | tr -s " " | cut -d " " -f 7 | cut -d "/" -f 1)
+    echo gets the AVD name from the exec command
+    avd=$(ps -ef | grep -v grep | grep "$pid" | egrep -o '\-avd .*' | cut -d " " -f 2)
+    echo AVD: ${avd}
+    # if name contains suffix
+    if echo "$avd" | grep -q "$SUFFIX"
+    then
+	echo Waiting for "emulator-${porta}:${avd}" to be ready
+
+	# Wait for online state with maximum 60 tries
+	COUNT=0
+	
+	while adb -s "emulator-${porta}" shell getprop dev.bootcomplete | grep -q error 
+	do
+	    if [ "$COUNT" -eq 60 ]
+	    then
+		echo "Emulator took too long to start up"
+		exit 1
+	    fi
+
+	    let COUNT++
+	    sleep 1
+	done
+    fi
+done

data/lib/skeleton/config/scripts/android/stop_emulators.sh

@@ -0,0 +1,13 @@
+#!/bin/bash
+# Author: Victor Nascimento
+
+SUFFIX=CALABASH_AVD_4.
+
+for AVD in $HOME/.android/avd/${SUFFIX}*.avd
+do 
+    AVD="$(basename ${AVD/.avd/})" 
+    echo chuck killing "$AVD"... 
+    pkill -9 -f "$AVD"
+done
+
+

data/lib/skeleton/config/scripts/break_build_if_failed.sh

@@ -0,0 +1,6 @@
+# Looking for errors on the report files and returns an error
+if [ $TESTS_RESULT == "Failed" ] 
+then
+    echo "Setting build as failed"
+    exit 1
+fi

data/lib/skeleton/config/scripts/check_if_tests_failed.sh

@@ -0,0 +1,11 @@
+# Looking for errors on the report files and returns an error
+cd "$WORKSPACE/reports-cal"
+
+export TESTS_RESULT="Ok"
+for folder in *
+do
+    if egrep '[0-9]+ failed' "$folder/reports.html"
+    then
+	export TESTS_RESULT="Failed"
+    fi
+done

data/lib/skeleton/config/scripts/ios/build_app.rb

@@ -0,0 +1,71 @@
+#!/usr/bin/env ruby
+# coding: utf-8
+# ----------------------------------------------------------------------------
+#
+# $1 -> configuration environment (dev or jenkins)
+#
+#
+# REMEMBER to fill the configuration file build_app.yml
+
+require 'fileutils'
+require 'yaml'
+require 'pathname'
+
+# When running on CI
+# It is a good pratice to run pod install when executing this script
+# on the CI to avoid building problems
+# %x(pod install)
+
+# Parsing the yaml configuration file
+config = YAML.load_file(File.join(File.dirname(__FILE__), 'build_app.yml'))
+
+if ARGV.length != 1
+  puts 'Error: Wrong number of arguments!'
+  puts 'Usage: build_app.rb environment'
+  puts "Available Environments: #{config.keys.join(', ')}"
+  exit 1
+end
+
+if config[ARGV[0]].nil?
+  puts 'Error: Wrong configuration environment!'
+  puts "Available Environments: #{config.keys.join(', ')}"
+  exit 1
+else
+  config = config[ARGV[0]]
+end
+
+puts "Starting at #{Time.now.strftime('%H:%M:%S')}"
+
+# Creating a folder name from the destination configuration parameter
+folder_name = config['destination'].gsub('platform=', '').gsub('name=', '')
+              .tr(' ', '_').tr(',', '_')
+export_path = File.join(config['export_path'], folder_name)
+
+# Removing the folder where the .app will be stored if it already exists
+FileUtils.rm_r export_path if Dir.exist?(export_path)
+
+# Creating the folder where the .app will be stored
+FileUtils.mkdir_p export_path
+
+puts 'Building project'
+
+system <<eos
+  xcodebuild -workspace "#{config['xcworkspace']}" \
+  -scheme "#{config['scheme']}" -destination "#{config['destination']}" \
+  -configuration "#{config['configuration']}" clean build \
+  CONFIGURATION_BUILD_DIR="#{export_path}"
+eos
+
+# Getting the app folder that was created
+# Listing all folders on the export path folder
+folders = Pathname.new(export_path).children.select { |c| c.directory? }
+# Getting the folder which ends with .app
+app_pathname = folders.select { |f| f.to_s.match('.app$') }
+# Getting the app folder path
+app_path = app_pathname.first.to_s
+
+# Printing the APP_BUNDLE_PATH in the terminal
+puts "APP_BUNDLE_PATH=#{app_path}"
+
+puts "End: #{Time.now.strftime('%H:%M:%S')}"
+puts 'Bye!'