Sha256: 5dcaf2eb9614a652e5f9525aeb30c0be3a97843443c0e0c93f42bd3e156cbb5c
Contents?: true
Size: 1.5 KB
Versions: 18
Compression:
Stored size: 1.5 KB
Contents
Feature: Displaying outdated cookbooks
As a user
I want to know what cookbooks are outdated before I run update
So that I can decide whether to update everything at once
Scenario: Running berks outdated with no version constraints
Given I write to "Berksfile" with:
"""
site :opscode
cookbook 'berkshelf-cookbook-fixture'
"""
When I successfully run `berks outdated`
Then the output should contain:
"""
Listing outdated cookbooks with newer versions available...
"""
And the output should contain:
"""
All cookbooks up to date
"""
Scenario: Running berks outdated with satisfied version constraints
Given I write to "Berksfile" with:
"""
site :opscode
cookbook 'berkshelf-cookbook-fixture', '>= 0.1'
"""
When I run `berks outdated`
Then the output should contain:
"""
Listing outdated cookbooks with newer versions available...
"""
And the output should contain:
"""
All cookbooks up to date
"""
Scenario: Running berks outdated with unsatisfied version constraints
Given I write to "Berksfile" with:
"""
site :opscode
cookbook 'berkshelf-cookbook-fixture', '~> 0.1'
"""
When I run `berks outdated`
Then the output should contain:
"""
Listing outdated cookbooks with newer versions available...
"""
And the output should contain:
"""
Cookbook 'berkshelf-cookbook-fixture (~> 0.1)' is outdated
"""
Version data entries
18 entries across 18 versions & 1 rubygems