sunomono 1.0.0 → 1.0.3

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: c2004c5b090a5d6ad75bba706b0b8ec7f56efc36
4
- data.tar.gz: 4ffb96f15db0a129f681d89aa4d348f0e2eab48d
3
+ metadata.gz: 8a61a48e2204b21f7a247e0d7bfbde0d8ac6da11
4
+ data.tar.gz: 437cf14ed19959b7a614e8c45cbc7e75fb43ace3
5
5
  SHA512:
6
- metadata.gz: 3c1a32996b059a4ac2eac72bab7823f4856c955b62abd4e53901eaf9063d09cbdd19aca0ea287b9b288a6caf0de88da2ea52d13eb92fcbee24e8cd15e29d8d06
7
- data.tar.gz: e4818940ec114d4f016f80080ec1ed4302cf07dd05aabedf2f6b1bce958e6486e319305795c94134e1e10b387fe37909edc21311071c8080310e5a4d3570ad34
6
+ metadata.gz: 34dc1c888445f5a61d8c5ed526f9b4049ba97eba11916281f5fc923f782f7f7e656b941535a1138bafc2ca8fe3fe500475fd8743c2c7674e3d31c5e3bac2c1fd
7
+ data.tar.gz: 512553fadeeb9ad139f1b27a653cef21128d4a1c6d9b477dc13a72e2edbce625784aad12fd4584c0d058fd756f3c1722f62d2204a4a8083b6bf41865bd02293c
@@ -1,165 +0,0 @@
1
- #Getting Started
2
-
3
- ## Ruby
4
-
5
- There is a lot of ways of installing ruby, one is using RVM (http://rvm.io/rvm/install):
6
-
7
- Install RVM stable with ruby:
8
-
9
- ```
10
- $ \curl -sSL https://get.rvm.io | bash -s stable --ruby
11
- ```
12
-
13
- After this, include the following lines in you `~/.bashrc` file.
14
-
15
- ```
16
- export PATH="$PATH:$HOME/.rvm/bin" # Add RVM to PATH for scripting
17
- [[ -s $HOME/.rvm/scripts/rvm ]] && source $HOME/.rvm/scripts/rvm
18
- ```
19
-
20
- # Android
21
-
22
- ## Installing the Gems
23
-
24
- Install the following gems
25
-
26
- ```
27
- gem install calabash-common calabash-android
28
- ```
29
-
30
- **Warning!**
31
-
32
- The gem **`calabash-android`** can install the beta version of the cucumber gem.
33
- 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.
34
-
35
- ## Running the tests
36
- To run the android tests, you need to:
37
-
38
- 1. Open the Android AVD
39
- 2. Open the terminal on the tests folder
40
- 3. Execute the command:
41
-
42
- ```
43
- calabash-android run features/app-QA.apk -p android
44
- ```
45
-
46
-
47
- > To run in a computer with more than one emulator or device, use the command:
48
- >
49
- >```
50
- > ADB_DEVICE_ARG=emulator-5554 calabash-android run features/app-QA.apk -p android
51
- >```
52
- >
53
- >Given that 'emulator-5554' is one of the returns of the command `$ adb devices` on the terminal
54
-
55
-
56
- > To run on all connected devices, run the script `run_tests_all_devices.sh`, located on the `config/scripts/android` folder of the project
57
-
58
- > **!! IMPORTANT !!**
59
-
60
- > Remember to export the WORKSPACE variable with the path of the cloned test repository
61
-
62
- > Remember to pass the APK path as the parameter of the script
63
- >
64
- > ```
65
- > ./config/scripts/android/run_tests_all_devices.sh PATH_OF_APK_FILE
66
- >```
67
-
68
-
69
- ## Calabash Terminal
70
-
71
- The calabash terminal allows you to run the calabash commands without being on a test context
72
- To open the calabash terminal, you need to:
73
-
74
- 1. Open the Android AVD
75
- 2. Open the terminal on the tests folder
76
- 3. Execute the command:
77
-
78
- ```
79
- calabash-android console features/app-QA.apk -p android
80
- ```
81
-
82
- 4. Run the commands
83
-
84
- ```
85
- reinstall_apps
86
- start_test_server_in_background
87
- ```
88
-
89
- 5. Run the commands you want to.
90
-
91
- # iOS
92
-
93
- ## Installing the Gems
94
-
95
- Install the following gems
96
-
97
- ```
98
- gem install calabash-common calabash-cucumber
99
- ```
100
-
101
- ## Configuring the iOS project
102
-
103
- 1. Run the command `pod install`
104
- 2. Run the command `calabash-ios setup` and follow the instructions
105
- 3. Make sure that the signing is a wildcard
106
-
107
-
108
- ## Running the tests
109
- To run the iOS tests in a device, you need to:
110
-
111
- 1. Open the terminal on the tests folder
112
- 2. Compile the project to create the .app file with the command
113
-
114
- ```
115
- ./config/scripts/ios/build_app.sh xcworkspace_path TargetName-cal iphoneos8.1 ConfigurationName
116
- ```
117
-
118
- PS.1: TargetName-cal is the name of the target created with the command `calabash-ios setup`
119
- PS.2: iphoneos8.1 is the sdk for devices, for emulatores use iphonesimulator8.1
120
- PS.3: Configuration name can be Dev, Debug, Release, Prod or any other configuration build
121
- PS.4: The path to the .app file is the last output line of the above command
122
-
123
- 3. To execute one feature, run the command
124
-
125
- ```
126
- APP_BUNDLE_PATH=AppFilePath DEVICE_TARGET=DeviceUUID DEVICE_ENDPOINT=CalabashServerEndpointDevice cucumber -p ios
127
- ```
128
-
129
- 4. To execute all the features in the configured devices run the script
130
-
131
- ```
132
- ./config/scripts/ios/run_tests_all_devices.sh AppFilePath
133
- ```
134
-
135
- PS.: Remember to configure all the connected devices on the file `./config/scripts/ios/devices`.
136
- 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.
137
-
138
- ## Calabash Terminal (Device)
139
-
140
- The calabash terminal allows you to run the calabash commands without being on a test context
141
- To open the calabash terminal, you need to:
142
-
143
- 1. Connect the device
144
- 2. Open the terminal on the tests folder
145
- 3. Execute the command:
146
-
147
- ```
148
- APP_BUNDLE_PATH=AppFilePath DEVICE_TARGET=DeviceUUID DEVICE_ENDPOINT=CalabashServerEndpointDevice calabash-ios console
149
- ```
150
-
151
- 4. Run the command
152
-
153
- ```
154
- start_test_server_in_background
155
- ```
156
-
157
- 5. Run the commands you want to.
158
-
159
- ## Pitfalls
160
-
161
- 1. Always build the project with the device connected
162
- 2. Ensure that the device is enabled to Development and the UI Automations is enabled on the Developer menu (Settings)
163
- 3. If the device in pin locked, ensure that it is unlocked. If there is no pin, the calabash will automatically unlock the device
164
- 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.
165
- 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.
@@ -7,7 +7,7 @@ require_relative File.expand_path('../../base_screen/base_screen.rb', __FILE__)
7
7
  class AppiumWorld
8
8
  end
9
9
 
10
- if ENV['PLATAFORM'] == 'android'
10
+ if ENV['PLATFORM'] == 'android'
11
11
  caps = Appium.load_appium_txt file: File.expand_path('../android/appium.txt', __FILE__), verbose: true
12
12
  else
13
13
  caps = Appium.load_appium_txt file: File.expand_path('../ios/appium.txt', __FILE__), verbose: true
@@ -0,0 +1,3 @@
1
+ Before do
2
+ $driver.start_driver
3
+ end
@@ -1,3 +1,3 @@
1
1
  module Sunomono
2
- VERSION = '1.0.0'.freeze
2
+ VERSION = '1.0.3'.freeze
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: sunomono
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.0
4
+ version: 1.0.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Oscar Tanner
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2017-10-25 00:00:00.000000000 Z
12
+ date: 2017-10-30 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: bundler