Adding code and specs for creating empty structure with --init switch

[vestel]

--init switch creates following structure

• features\
  • step_definitions\
  • support\
    • env.rb
• cucumber.yml

If 'features' folder or 'cucumber.yml' exist, it exits with error-code 1

[aslakhellesoy]

Did you forget some assertions here?

[tooky]

@vestel would you be able to pull behaviour out into a SkeletonCreator? Would be nice to get this in as a new feature for 2.0.

[vestel]

@tooky I'll try to find out how the best way to do it during this weekend

[vestel]

@tooky Can you take a look and correct me if something wrong. I'm really not sure how to do that

[vestel]

Travis CI build error has nothing common with my code. I don't understand why it appeared, since local build was clean and green at my box. What should I do next?

[brasmusson]

The first time the Ruby 2.0.0 job failed with the error below, but when I restarted the job it passed:

(::) failed steps (::)
Exit status was 1 but expected it to be 0. Output:
Unable to contact the wire server at localhost:54321. Is it up? (Cucumber::WireSupport::Connection::ConnectionError)
/home/travis/build/cucumber/cucumber/lib/cucumber/wire_support/connection.rb:57:in `rescue in socket'
<snip>
Failing Scenarios:
cucumber -p ruby_2_0 features/docs/wire_protocol.feature:85 # Scenario: Dry run finds a step match

[mattwynne]

Don't worry about the build failure then - thanks @brasmusson.

@vestel it's hard to review this PR because it contains 4b4cd78 which has a lot of changes in it, and aren't related to this change. Can you rebase your branch to just have the commits that you've made for this change?

[mattwynne]

Superseded by #699. Thanks anyway @vestel!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.