Secondly, add a simulator device entry (no UDID needed) and make sure you provide the actual value for screen based on your iOS Simulator settings: devices: Build/Products/Debug-iphonesimulator/CoreDataBooks.app However you can also run them on the iOS Simulator.įirst off, modify your features/support/config.yml to include the path to your compiled app (relative or absolute), e.g. We encourage you to run your Zucchini features on real hardware. You can set one of the devices to be used by default in config.yml so that you can avoid setting ZUCCHINI_DEVICE each time: devices: ZUCCHINI_DEVICE="My Device" zucchini run /path/to/my_feature The udidetect utility comes in handy if you plan to add devices from time to time: udidetect -z. Running on the deviceĪdd your device to features/support/config.yml.
Make sure you check out the zucchini-demo project featuring an easy to explore Zucchini setup around Apple's CoreDataBooks sample. Start developing by editing features/my_feature/feature.zucchini and features/support/screens/ffee. Then to create a feature scaffold for your first feature: zucchini generate -feature /path/to/my_project/features/my_feature To create a project scaffold: zucchini generate -project /path/to/my_project You might as well keep your Zucchini tests in a separate project.
Using Zucchini doesn't involve making any modifications to your application code. Start using Zucchini gem install zucchini - ios A few command line tools which can be installed with homebrew:īrew update & brew install imagemagick node.