Sha256: 9197da3207b0135f72db396af04314ae85f011eb310e2955432da989e51271ae
Contents?: true
Size: 1.6 KB
Versions: 7
Compression:
Stored size: 1.6 KB
Contents
Feature: Module status
The `status` subcommand displays all known modules and their status.
Background:
Given a repository with following Vendorfile:
"""ruby
vendor 'generated', :version => '0.23' do |v|
File.open('README', 'w') { |f| f.puts "Hello, World!" }
File.open('VERSION', 'w') { |f| f.puts v.version }
end
"""
Scenario: status new module
When I run vendor command "status"
Then the last vendor output should match /new\s+generated\/0.23/
Scenario: status up-to-date module
When I run vendor command "install"
And I run vendor command "status"
Then the last vendor output should match /up to date\s+generated\/0.23/
Scenario: status outdated modules
When I run vendor command "install"
And I change Vendorfile to:
"""ruby
vendor 'generated', :version => '0.42' do |v|
File.open('README', 'w') { |f| f.puts "Hello, Updated, World!" }
File.open('VERSION', 'w') { |f| f.puts v.version }
end
"""
And I run vendor command "status"
Then the last vendor output should match /outdated\s+generated\/0.42/
Scenario: Module's dependencies are statused if they are known
When I change Vendorfile to:
"""ruby
require 'vendorificator/vendor/chef_cookbook'
chef_cookbook 'memcached'
"""
And I run vendor command "status"
Then the last vendor output should match /new\s+memcached/
And the last vendor output should not match "runit"
When I run vendor command "install"
And I run vendor command "status"
Then the last vendor output should match /up to date\s+memcached/
And the last vendor output should match /up to date\s+runit/
Version data entries
7 entries across 7 versions & 1 rubygems