- XCode 4.2
- A few command line tools:
brew update && brew install imagemagick && brew install coffee-script
gem install zucchini-ios
Using Zucchini doesn't involve making any modifications to your application code. You might as well keep your Zucchini tests in a separate project.
Start by creating a project scaffold:
zucchini generate --project /path/to/my_project
Create a feature scaffold for your first feature:
zucchini generate --feature /path/to/my_project/features/my_feature
Start hacking by modifying features/my_feature/feature.zucchini and features/support/screens/welcome.coffee.
Alternatively, check out the zucchini-demo project featuring an easy to explore Zucchini setup around Apple's CoreDataBooks sample.
Add your device to features/support/config.yml.
The udidetect utility comes in handy if you plan to add devices from time to time:
ZUCCHINI_DEVICE="My Device" zucchini run /path/to/my_feature
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.
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
zucchini --help zucchini run --help zucchini generate --help