gistfile1.txt

$ cucumber-chef test --tags @minitest
cucumber-chef v2.0.0.rc1

Using features directory: /home/sns/chef-repo/features
Cucumber-Chef Test Runner Initalized!
Cleaning up any previous test runs...done.
Uploading files required for this test run...done.
Executing Cucumber-Chef Test Runner
@minitest
Feature: Run minitests
  
  In order to unit-test cookbooks
  As an infrastructure developer
  I want to be able to run the MiniTest suites from the same interface as my Cucumber tests

  Background:                                                       # ./wonderstuff/minitest.feature:8
    * all servers are being destroyed
    * I have a server called "minitest"                             # cucumber-chef-2.0.0.rc1/lib/cucumber/chef/steps/provision_steps.rb:22
    * "minitest" is running "ubuntu" "lucid"                        # cucumber-chef-2.0.0.rc1/lib/cucumber/chef/steps/provision_steps.rb:26
    * minitest is being provisioned
    * "minitest" has been provisioned                               # cucumber-chef-2.0.0.rc1/lib/cucumber/chef/steps/provision_steps.rb:46
    * the "apache" recipe has been added to the "minitest" run list # cucumber-chef-2.0.0.rc1/lib/cucumber/chef/steps/provision_steps.rb:54

  Scenario: MiniTest suites should pass                             # ./wonderstuff/minitest.feature:14
    When I enable the running of MiniTest suites for "minitest"     # wonderstuff/step_definitions/minitest_steps.rb:1
    Then the tests should run and pass on "minitest"                # wonderstuff/step_definitions/minitest_steps.rb:5
      # Running tests:
      
      apache2::default#test_0004_drops_off_an_index_page = 0.00 s = .
      apache2::default#test_0002_starts_the_apache_servce = 0.16 s = .
      apache2::default#test_0005_should_replace_the_default_index_page_with_a_wonderstuff_design_page = 0.00 s = .
      apache2::default#test_0003_ensures_the_apache_service_will_be_running_after_reboot = 0.18 s = .
      apache2::default#test_0001_installs_the_apache_webserver = 0.49 s = .
      
      
      Finished tests in 0.850603s, 5.8782 tests/s, 7.0538 assertions/s.
      
      5 tests, 6 assertions, 0 failures, 0 errors, 0 skips

1 scenario (1 passed)
6 steps (6 passed)
2m33.001s