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

@@ -16,11 +16,10 @@
     Then the output should contain:
       """
       All cookbooks up to date!
       """
 
-
   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
@@ -37,11 +36,10 @@
       """
       The following cookbooks have newer versions:
         * bacon (1.1.0)
       """
 
-
   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 |
@@ -59,11 +57,10 @@
       """
       The following cookbooks have newer versions:
         * bacon (1.5.8)
       """
 
-
   Scenario: When there is no lockfile present
     And I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'bacon', '1.0.0'
       """
@@ -71,10 +68,9 @@
     Then the output should contain:
       """
       Could not find cookbook 'bacon (= 1.0.0)'. Try running `berks install` to download and install the missing dependencies.
       """
     And the exit status should be "CookbookNotFound"
-
 
   Scenario: When the cookbook is not installed
     And I have a Berksfile pointing at the local Berkshelf API with:
       """
       cookbook 'bacon', '1.0.0'