Sha256: 53dbe1f88c10d64a4fe590907fcb6792f32fae37c9d293be2c3ccc776b8acf4d
Contents?: true
Size: 628 Bytes
Versions: 12
Compression:
Stored size: 628 Bytes
Contents
Feature: Berksfile.lock
As a user
I want my versions to be locked even when I don't specify versions in my Berksfile
So when I share my repository, all other developers get the same versions that I did when I installed.
@slow_process
Scenario: Writing the Berksfile.lock
Given I write to "Berksfile" with:
"""
cookbook 'ntp', '1.1.8'
"""
When I run the install command
Then a file named "Berksfile.lock" should exist in the current directory
And the file "Berksfile.lock" should contain in the current directory:
"""
cookbook 'ntp', :locked_version => '1.1.8'
"""
Version data entries
12 entries across 12 versions & 1 rubygems