zucchini-ios 0.5.3 → 0.5.4

data/README.md

@@ -28,20 +28,44 @@ Create a feature scaffold for your first feature:
 zucchini generate --feature /path/to/my_project/features/my_feature
 ```
 
-Add your device to features/support/config.yml.
-
-The [udidetect](https://github.com/vaskas/udidetect) utility comes in handy if you plan to add devices from time to time: `udidetect -z`.
-
 Start hacking by modifying features/my_feature/feature.zucchini and features/support/screens/welcome.coffee.
 
 Alternatively, check out the [zucchini-demo](https://github.com/rajbeniwal/zucchini-demo) project featuring an easy to explore Zucchini setup around Apple's CoreDataBooks sample.
 
-Running a feature on the device
+Running on the device
 --------------------------------
+Add your device to features/support/config.yml.
+
+The [udidetect](https://github.com/vaskas/udidetect) utility comes in handy if you plan to add devices from time to time: `udidetect -z`.
+
 ```
 ZUCCHINI_DEVICE="My Device" zucchini run /path/to/my_feature 
 ```
 
+Running on the iOS Simulator
+-------------------------------
+We strongly encourage you to run your Zucchini features on real hardware. However, you can run them on the iOS Simulator if you must.
+
+First off, modify your features/support/config.yml to include a full path to your compiled app, e.g.
+
+```
+app: /Users/vaskas/Library/Developer/Xcode/DerivedData/CoreDataBooks-ebeqiuqksrwwoscupvxuzjzrdfjz/Build/Products/Debug-iphonesimulator/CoreDataBooks.app
+```
+
+Secondly, add an 'iOS Simulator' entry to the devices section (no UDID needed) and make sure you provide the actual value for 'screen' based on your iOS Simulator settings:
+
+```
+devices:
+  iOS Simulator:
+    screen: low_ios5
+```
+
+Run it as usual:
+
+```
+ZUCCHINI_DEVICE="iOS Simulator" zucchini run /path/to/my_feature 
+```
+
 See also
 ---------
 ```

data/lib/feature.rb

@@ -55,8 +55,10 @@ class Zucchini::Feature
       `rm -rf #{run_data_path}/*`
       compile_js
     
+      device_params = (@device[:name] == "iOS Simulator") ? "" : "-w #{@device[:udid]}"
+      
       begin
-        out = `instruments -w #{@device[:udid]} -t #{Zucchini::Config.template} #{Zucchini::Config.app} -e UIASCRIPT #{run_data_path}/feature.js -e UIARESULTSPATH #{run_data_path} 2>&1`
+        out = `instruments #{device_params} -t #{Zucchini::Config.template} #{Zucchini::Config.app} -e UIASCRIPT #{run_data_path}/feature.js -e UIARESULTSPATH #{run_data_path} 2>&1`
         puts out
         # Hack. Instruments don't issue error return codes when JS exceptions occur
         raise "Instruments run error" if (out.match /JavaScript error/) || (out.match /Instruments\ .{0,5}\ Error\ :/ )

data/lib/version.rb

@@ -1,3 +1,3 @@
 module Zucchini
-  VERSION = "0.5.3"
+  VERSION = "0.5.4"
 end

metadata

@@ -2,7 +2,7 @@
 name: zucchini-ios
 version: !ruby/object:Gem::Version 
   prerelease: 
-  version: 0.5.3
+  version: 0.5.4
 platform: ruby
 authors: 
 - Vasily Mikhaylichenko
@@ -12,7 +12,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-12-22 00:00:00 Z
+date: 2011-12-28 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: clamp