Sha256: 741469ffd06e2fb203109bffe720be13ac2a8b1ebb742c10d6de2056761cb1b0

Contents?: true

Size: 627 Bytes

Versions: 5

Compression:

Stored size: 627 Bytes

Contents

@typical_usage
Feature: Install Vim plugins
  In order to automate boring steps,
  as a lazy Vim user,
  I want to use a declarative way to start using new Vim plugins.

  Background:
    Given a repository "foo" with versions "1.0.0 1.0.1 1.0.2"

  Scenario: Install from scratch
    Given a flavorfile with:
      """ruby
      """
    When I edit the flavorfile as:
      """ruby
      flavor '$foo_uri'
      """
    And I run `vim-flavor install`
    Then it should pass
    And a lockfile is created with:
      """
      $foo_uri (1.0.2)
      """
    And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"

Version data entries

5 entries across 5 versions & 1 rubygems

Version Path
vim-flavor-4.0.3 features/typical_usage/install_vim_plugins.feature
vim-flavor-4.0.2 features/typical_usage/install_vim_plugins.feature
vim-flavor-4.0.1 features/typical_usage/install_vim_plugins.feature
vim-flavor-4.0.0 features/typical_usage/install_vim_plugins.feature
vim-flavor-3.0.0 features/typical_usage/install_vim_plugins.feature