features/commands/package.feature in berkshelf-3.0.0.beta4 vs features/commands/package.feature in berkshelf-3.0.0.beta5

@@ -7,48 +7,11 @@
   Scenario: When no options are passed
     Given I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'fake', '~> 1.0.0'
       """
-    When I successfully run `berks package fake`
-    Then a file named "fake.tar.gz" should exist
+    When I successfully run `berks package my-cookbooks.tar.gz`
+    Then a file named "my-cookbooks.tar.gz" should exist
     And the output should contain:
       """
       Cookbook(s) packaged to
       """
-
-
-  Scenario: With the --output option
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '~> 1.0.0'
-      """
-    When I successfully run `berks package fake --output foo/bar`
-    Then a file named "foo/bar/fake.tar.gz" should exist
-
-
-  Scenario: With an installed cookbook name
-    Given I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'fake', '~> 1.0.0'
-      """
-    When I run `berks package non-existent`
-    Then a file named "non-existent.tar.gz" should not exist
-    And the output should contain:
-      """
-      Cookbook 'non-existent' is not in your Berksfile
-      """
-    And the exit status should be "CookbookNotFound"
-
-
-  Scenario: With an invalid cookbook
-    Given a cookbook named "cookbook with spaces"
-    And I have a Berksfile pointing at the local Berkshelf API with:
-      """
-      cookbook 'cookbook with spaces', path: './cookbook with spaces'
-      """
-    When I run `berks package`
-    Then the output should contain:
-      """
-      The cookbook 'cookbook with spaces' has invalid filenames:
-      """
-    And the exit status should be "InvalidCookbookFiles"