features/commands/outdated.feature in berkshelf-6.2.0 vs features/commands/outdated.feature in berkshelf-6.2.1

@@ -1,11 +1,10 @@
 Feature: berks outdated
   Scenario: the dependency is up to date
     Given the Chef Server has cookbooks:
       | bacon | 1.0.0 |
       | bacon | 1.1.0 |
-    And the Berkshelf API server's cache is up to date
     And the cookbook store has the cookbooks:
       | bacon | 1.1.0 |
     And I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'bacon', '~> 1.1.0'
@@ -27,11 +26,10 @@
 
   Scenario: the dependency has no version constraint and there are new items
     Given the Chef Server has cookbooks:
       | bacon | 1.0.0 |
       | bacon | 1.1.0 |
-    And the Berkshelf API server's cache is up to date
     And the cookbook store has the cookbooks:
       | bacon | 1.0.0 |
     And I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'bacon'
@@ -54,10 +52,9 @@
   Scenario: the dependency has a version constraint and there are new items that satisfy it
     Given the Chef Server has cookbooks:
       | bacon | 1.1.0 |
       | bacon | 1.2.1 |
       | bacon | 1.5.8 |
-    And the Berkshelf API server's cache is up to date
     And the cookbook store has the cookbooks:
       | bacon | 1.0.0 |
     And I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'bacon', '~> 1.0'