Sha256: 3c25ac7f8303fbb79d49e7773a2bcbcad6d1534c0e1919557f20930a35079802

Contents?: true

Size: 686 Bytes

Versions: 5

Compression:

Stored size: 686 Bytes

Contents

Feature: Lockfile
  In order to avoid unexpected result and confusion,
  as a lazy Vim user,
  I want to stop vim-flavor process if obsolete file still exists.

  Scenario: User has old name of lockfile
    Given a repository "foo" with versions "1.0.0 1.0.1 1.0.2"
    And a flavorfile with:
      """ruby
      flavor '$foo_uri'
      """
    And an old name lockfile with:
      """
      $foo_uri (1.0.1)
      """
    When I run `vim-flavor install`
    Then it should fail with template:
      """
      Error: VimFlavor.lock is no longer used.  Rename it to Flavorfile.lock.
      """
    And a lockfile is not created
    And a flavor "$foo_uri" is not deployed to "$home/.vim"

Version data entries

5 entries across 5 versions & 1 rubygems

Version Path
vim-flavor-4.0.3 features/backward_compatibilities/lockfile.feature
vim-flavor-4.0.2 features/backward_compatibilities/lockfile.feature
vim-flavor-4.0.1 features/backward_compatibilities/lockfile.feature
vim-flavor-4.0.0 features/backward_compatibilities/lockfile.feature
vim-flavor-3.0.0 features/backward_compatibilities/lockfile.feature