gistfile1.txt

$ bundle exec cucumber
Feature: User posts to their blog
  In order post to my blog while I'm travelling
  As an author
  I want to publish posts from my iPhone

  Background:                                                 # features/example.feature:6
    Given "Specs.xcodeproj" is loaded in the iphone simulator # iCuke-0.6.3/lib/icuke/cucumber.rb:197
      execution expired (Timeout::Error)
      /Volumes/HD/Users/justin/.rvm/rubies/ruby-1.8.7-p302/lib/ruby/1.8/timeout.rb:64:in `launch'
      features/example.feature:7:in `Given "Specs.xcodeproj" is loaded in the iphone simulator'

  Scenario:                                                   # features/example.feature:9
    When I tap "New post"                                     # iCuke-0.6.3/lib/icuke/cucumber.rb:227
    And I type "My post" in "Title"                           # iCuke-0.6.3/lib/icuke/cucumber.rb:231
    And I type "Interesting things" in "Body"                 # iCuke-0.6.3/lib/icuke/cucumber.rb:231
    And I tap "Post"                                          # iCuke-0.6.3/lib/icuke/cucumber.rb:227
    Then I should see "Published"                             # iCuke-0.6.3/lib/icuke/cucumber.rb:219

Failing Scenarios:
cucumber features/example.feature:9 # Scenario: 

1 scenario (1 failed)
6 steps (1 failed, 5 skipped)
0m30.322s

Hi Justin,

I'm stuck on this step as well. https://gist.github.com/853726
How did you solve this? What do you mean by shutdown?
Any suggestions would be much appreciated.

Thanks.

So my mistake was that I was building the app and running it from XCode, then running Cucumber. Because iCuke uses a tool to launch the simulator itself, it was failing (because the simulator was already running). The solution was to quit the simulator and run cucumber, which in turn let it launch the simulator.

Thanks, but that doesn't seem to be the problem for me. The problem for me was that I hadn't created build/Debug-iphonesimulator in advance. Got it fixed. : )

@achainan - I just so happened to run into the exact same problem again. This time, the surface-layer cause was that I created the Xcode application with Xcode 4. I trashed the app and created it in Xcode 3.2.x and it worked fine (even after I went in and edited the app using Xcode 4)