features/commands/outdated.feature in berkshelf-3.1.0 vs features/commands/outdated.feature in berkshelf-3.1.1

@@ -46,11 +46,11 @@
       """
     When I successfully run `berks outdated`
     Then the output should contain:
       """
       The following cookbooks have newer versions:
-        * bacon (1.1.0)
+        * bacon (1.0.0 => 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 |
@@ -73,10 +73,10 @@
       """
     When I successfully run `berks outdated`
     Then the output should contain:
       """
       The following cookbooks have newer versions:
-        * bacon (1.5.8)
+        * bacon (1.0.0 => 1.5.8)
       """
 
   Scenario: When the lockfile is not present
     Given I have a Berksfile pointing at the local Berkshelf API with:
       """