features/install.feature in berkshelf-0.4.0 vs features/install.feature in berkshelf-0.5.0.rc1

@@ -63,25 +63,10 @@
       """
       Using example_cookbook (0.5.0) at path:
       """
     And the exit status should be 0
 
-  @no_run
-  Scenario: installing a Berksfile that contains a path location which contains a broken symlink
-    Given a Berksfile with path location sources to fixtures:
-      | example_cookbook_broken_link | example_cookbook_broken_link |
-    When I run the install command with flags:
-      | --shims |
-    Then the following directories should exist:
-      | cookbooks                  |
-      | cookbooks/example_cookbook |
-    And the output should contain:
-      """
-      Shims written to: 
-      """
-    And the exit status should be 0
-
   Scenario: installing a Berksfile that contains a Git location
     Given I write to "Berksfile" with:
       """
       cookbook "artifact", git: "git://github.com/RiotGames/artifact-cookbook.git", ref: "0.9.8"
       """
@@ -144,65 +129,10 @@
       """
       Cookbook 'doesntexist' not found in any of the default locations
       """
     And the CLI should exit with the status code for error "CookbookNotFound"
 
-  Scenario: running install command with the --shims flag to create a directory of shims
-    Given I write to "Berksfile" with:
-      """
-      cookbook "mysql", "1.2.4"
-      """
-    When I run the install command with flags:
-      | --shims |
-    Then the following directories should exist:
-      | cookbooks       |
-      | cookbooks/mysql |
-    And the output should contain:
-      """
-      Shims written to: 
-      """
-    And the exit status should be 0
-
-  Scenario: running install command with the --shims flag and a relative path
-    Given I write to "Berksfile" with:
-      """
-      cookbook "mysql", "1.2.4"
-      """
-    When I run the install command with flags:
-      | --shims relativepath |
-    Then the following directories should exist:
-      | relativepath       |
-      | relativepath/mysql |
-    And the output should contain:
-      """
-      Shims written to: 
-      """
-    And the exit status should be 0
-
-  Scenario: running install with --shims when current project is a cookbook and the 'metadata' is specified
-    Given a cookbook named "sparkle_motion"
-    And the cookbook "sparkle_motion" has the file "Berksfile" with:
-      """
-      metadata
-      """
-    When I cd to "sparkle_motion"
-    And I run the install command with flags:
-      | --shims |
-    Then the following directories should exist:
-      | cookbooks                |
-      | cookbooks/sparkle_motion |
-    And the output should contain:
-      """
-      Shims written to: 
-      """
-    And the output should contain:
-      """
-      Using sparkle_motion (0.0.0) at path:
-      """
-    And the exit status should be 0
-
-
   Scenario: installing a Berksfile that has a Git location source with an invalid Git URI
     Given I write to "Berksfile" with:
       """
       cookbook "nginx", git: "/something/on/disk"
       """
@@ -265,10 +195,10 @@
     And the CLI should exit with the status code for error "InternalError"
 
   Scenario: with a cookbook definition containing a chef_api source location
     Given I write to "Berksfile" with:
       """
-      cookbook "artifact", chef_api: :knife
+      cookbook "artifact", "= 0.10.2", chef_api: :knife
       """
     And the Chef server has cookbooks:
       | artifact | 0.10.2 |
     When I run the install command
     Then the output should contain: