vim-flavor 2.2.1 → 4.0.1

data/features/branches/changing_tracking_branches.feature

@@ -24,7 +24,6 @@ Feature: Changing tracking branches
         $foo_uri $foo_rev_102 at master ... done
       Completed.
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
 
   Scenario: Use a branch instead of a version
@@ -49,7 +48,6 @@ Feature: Changing tracking branches
       """
       $foo_uri ($foo_rev_102 at master)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
 
   Scenario: Use a version instead of a branch
@@ -74,5 +72,4 @@ Feature: Changing tracking branches
       """
       $foo_uri (1.0.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"

data/features/branches/detect_incompatible_declarations.feature

@@ -32,7 +32,6 @@ Feature: Detect incompatible declarations
         $L_uri branch: experimental is required by $B_uri
       Please resolve the conflict.
       """
-    And a bootstrap script is not created in "$home/.vim"
     And a flavor "$A_uri" is not deployed to "$home/.vim"
     And a flavor "$B_uri" is not deployed to "$home/.vim"
     And a flavor "$L_uri" is not deployed to "$home/.vim"
@@ -66,7 +65,6 @@ Feature: Detect incompatible declarations
         $L_uri ~> 0.2 is required by $B_uri
       Please resolve the conflict.
       """
-    And a bootstrap script is not created in "$home/.vim"
     And a flavor "$A_uri" is not deployed to "$home/.vim"
     And a flavor "$B_uri" is not deployed to "$home/.vim"
     And a flavor "$L_uri" is not deployed to "$home/.vim"

data/features/branches/install.feature

@@ -24,7 +24,6 @@ Feature: Install Vim plugins with specific branches
       """
       $foo_uri ($foo_rev_102 at master)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
 
   Scenario: Install a plugin according to a lockfile
@@ -47,5 +46,4 @@ Feature: Install Vim plugins with specific branches
         $foo_uri $foo_rev_102 at master ... skipped (already deployed)
       Completed.
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"

data/features/branches/update.feature

@@ -26,5 +26,4 @@ Feature: Update Vim plugins with specific branches
         $foo_uri $foo_rev_103 at master ... done
       Completed.
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.3" is deployed to "$home/.vim"

data/features/caching/deployment.feature

@@ -9,6 +9,7 @@ Feature: Deployment
       """ruby
       flavor '$foo_uri', '~> 1.0'
       """
+
   Scenario: Deploy plugins which are not deployed yet
     Given a flavor "$foo_uri" is not deployed to "$home/.vim"
     When I run `vim-flavor install`

data/features/flavorfile/README.md

@@ -1,6 +1,6 @@
 Flavorfile is a DSL to declare which versions of Vim plugins to use.
 Whenever `vim-flavor` is invoked to manage Vim plugins,
-`vim-flavor` reads a file `VimFlavor` in the current working directory,
+`vim-flavor` reads a file `Flavorfile` in the current working directory,
 and evaluates it as a flavorfile.
 
 

data/features/flavorfile/comments.feature

@@ -19,5 +19,4 @@ Feature: Comments
     And a lockfile is created with:
       """
       """
-    And a bootstrap script is created in "$home/.vim"
     But a flavor "$foo_uri" is not deployed to "$home/.vim"

data/features/flavorfile/groups.feature

@@ -19,7 +19,6 @@ Feature: Groups
       """
       $foo_uri (1.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.2" is deployed to "$home/.vim"
     But a flavor "$bar_uri" is not deployed to "$home/.vim"
 
@@ -35,7 +34,6 @@ Feature: Groups
       """
       $foo_uri (1.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.2" is deployed to "$home/.vim"
     But a flavor "$bar_uri" is not deployed to "$home/.vim"
 
@@ -52,6 +50,5 @@ Feature: Groups
     And a lockfile is created with:
       """
       """
-    And a bootstrap script is created in "$home/.vim"
     But a flavor "$foo_uri" is not deployed to "$home/.vim"
     But a flavor "$bar_uri" is not deployed to "$home/.vim"

data/features/flavorfile/repository_name.feature

@@ -7,7 +7,7 @@ Feature: Repository name
     Given a GitHub repository "vim-scripts/vspec" with versions "0.0.4 1.2.0"
     And a flavorfile with:
       """ruby
-      # Fetch the plugin from git://github.com/vim-scripts/vspec.git
+      # Fetch the plugin from https://github.com/vim-scripts/vspec.git
       flavor 'vspec', '~> 0.0'
       """
     When I run `vim-flavor install`
@@ -16,14 +16,13 @@ Feature: Repository name
       """
       vspec (0.0.4)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "vspec" version "0.0.4" is deployed to "$home/.vim"
 
   Scenario: Declare using a Vim plugin from GitHub
     Given a GitHub repository "kana/vim-vspec" with versions "0.0.4 1.2.0"
     And a flavorfile with:
       """ruby
-      # Fetch the plugin from git://github.com/kana/vim-vspec.git
+      # Fetch the plugin from https://github.com/kana/vim-vspec.git
       flavor 'kana/vim-vspec', '~> 0.0'
       """
     When I run `vim-flavor install`
@@ -32,7 +31,6 @@ Feature: Repository name
       """
       kana/vim-vspec (0.0.4)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "kana/vim-vspec" version "0.0.4" is deployed to "$home/.vim"
 
   Scenario: Declare using a Vim plugin from an arbitrary URI
@@ -48,5 +46,4 @@ Feature: Repository name
       """
       $vspec_uri (0.0.4)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$vspec_uri" version "0.0.4" is deployed to "$home/.vim"

data/features/flavorfile/version_constraint.feature

@@ -3,10 +3,9 @@ Feature: Version constraint
   as a lazy Vim user,
   I want to declare desirable versions of Vim plugins.
 
-  Note that vim-flavor assumes that plugins follow [the versioning policies of
-  RubyGems](http://docs.rubygems.org/read/chapter/7#page26), to determine
-  compatibility of plugins.  See also [Philosophy](../philosophy) for the
-  details.
+  Note that vim-flavor assumes that plugins follow [Semantic Versioning
+  2.0.0](https://semver.org/spec/v2.0.0.html), to determine compatibility of
+  plugins.  See also [Philosophy](../philosophy) for the details.
 
   Background:
     Given a repository "foo" with versions "1.0 1.1 1.2 2.0"
@@ -22,7 +21,6 @@ Feature: Version constraint
       """
       $foo_uri (2.0)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "2.0" is deployed to "$home/.vim"
 
   Scenario: Declare using a Vim plugin not older than a specific version
@@ -36,7 +34,6 @@ Feature: Version constraint
       """
       $foo_uri (2.0)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "2.0" is deployed to "$home/.vim"
 
   Scenario: Declare using the latest and compatible version of a Vim plugin
@@ -50,5 +47,4 @@ Feature: Version constraint
       """
       $foo_uri (1.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.2" is deployed to "$home/.vim"

data/features/install_vim_flavor.md

@@ -1,10 +1,10 @@
 ## Required softwares
 
-* [Git](http://git-scm.com/) 1.7.9 or later
-* [Ruby](http://www.ruby-lang.org/) 2.0.0 or later
-  * Recommendation: Use [RVM](http://beginrescueend.com/) or other tools
+* [Git](https://git-scm.com/) 2.10.1 or later
+* [Ruby](https://www.ruby-lang.org/) 3.0.0 or later
+  * Recommendation: Use [rbenv](https://github.com/rbenv/rbenv) or other tools
     for ease of installation across different envinronments.
-* [Vim](http://www.vim.org/) 7.3 or later
+* [Vim](https://www.vim.org/) 8.0 or later
   * Note that Vim should be compiled as normal, big or huge version
     to use most of plugins.
 
@@ -26,14 +26,8 @@
 
     cd $YOUR_REPOSITORY_FOR_DOTFILES
 
-    # Add the following line into the first line of your vimrc:
-    #
-    #   runtime flavors/bootstrap.vim
-    vim vimrc
-
-    touch VimFlavor VimFlavor.lock
-
-    git add VimFlavor VimFlavor.lock vimrc
+    touch Flavorfile Flavorfile.lock
+    git add Flavorfile Flavorfile.lock
     git commit -m 'Use vim-flavor to manage my favorite Vim plugins'
 
 

data/features/news.md

@@ -0,0 +1 @@
+../CHANGELOG.md

data/features/philosophy.md

@@ -8,11 +8,11 @@ vim-flavor can install plugins which meet the following conditions:
   This is an intentional design.  Because:
   * [vim-scripts.org](http://vim-scripts.org/) provides
     [comprehensive Git mirrors](https://github.com/vim-scripts) for
-    [plugins uploaded to www.vim.org](http://www.vim.org/scripts/index.php).
+    [plugins uploaded to www.vim.org](https://www.vim.org/scripts/index.php).
   * Experimental plugins which are not uploaded to www.vim.org
     are usually found in [GitHub](https://github.com/).
-* Plugins must follow [the versioning policies of
-  RubyGems](http://docs.rubygems.org/read/chapter/7#page26) and have "version"
+* Plugins must follow [Semantic Versioning
+  2.0.0](https://semver.org/spec/v2.0.0.html) and have "version"
   tags in their repositories.  For example, if there is the version 1.2.3 of
   a plugin, its repository must have the tag `1.2.3`, and the files of the
   version 1.2.3 can be checked out via the tag `1.2.3`.  In other words,
@@ -35,7 +35,7 @@ vim-flavor can install plugins which meet the following conditions:
   * Git mirrors by vim-scripts.org have proper directory structures even if
     the original plugins are uploaded to www.vim.org without proper directory
     structures.  (A good example is
-    [a.vim](http://www.vim.org/scripts/script.php?script_id=31) and
+    [a.vim](https://www.vim.org/scripts/script.php?script_id=31) and
     [its mirror](https://github.com/vim-scripts/a.vim).)
   * Other Git repositories might not have proper directory structures.
     Such plugins are not ready to use for everyone.

data/features/resolve_dependencies/README.md

@@ -14,12 +14,13 @@ overlooked.
 
 So that `vim-flavor` automatically resolves dependencies of Vim plugins.  If
 a plugin declares its dependencies as a [flavorfile](flavorfile) and saves it
-as `VimFlavor`, `vim-flavor` reads the file and automatically installs
+as `Flavorfile`, `vim-flavor` reads the file and automatically installs
 dependencies according to the file.
 
 `vim-flavor` also takes care about versions of Vim plugins.  If two plugins
-require the same plugin but required versions are not compatible to others,
-installation will be stopped to avoid using Vim with a broken configuration.
+require the same plugin but required versions are not compatible to each
+other, installation will be stopped to avoid using Vim with a broken
+configuration.
 
 
 

data/features/resolve_dependencies/basics.feature

@@ -34,7 +34,6 @@ Feature: Resolve dependencies of Vim plugins
       $foo_uri (1.1)
       $qux_uri (2.1)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.1" is deployed to "$home/.vim"
     And a flavor "$bar_uri" version "2.1" is deployed to "$home/.vim"
     And a flavor "$qux_uri" version "2.1" is deployed to "$home/.vim"
@@ -72,7 +71,6 @@ Feature: Resolve dependencies of Vim plugins
       $foo_uri (1.1)
       $qux_uri (1.1)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.1" is deployed to "$home/.vim"
     And a flavor "$bar_uri" version "2.1" is deployed to "$home/.vim"
     And a flavor "$qux_uri" version "1.1" is deployed to "$home/.vim"
@@ -112,7 +110,6 @@ Feature: Resolve dependencies of Vim plugins
       $foo_uri (2.1)
       $qux_uri (2.1)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "2.1" is deployed to "$home/.vim"
     And a flavor "$bar_uri" version "2.1" is deployed to "$home/.vim"
     And a flavor "$qux_uri" version "2.1" is deployed to "$home/.vim"
@@ -145,6 +142,5 @@ Feature: Resolve dependencies of Vim plugins
       $bar_uri (2.1)
       $foo_uri (2.1)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "2.1" is deployed to "$home/.vim"
     And a flavor "$bar_uri" version "2.1" is deployed to "$home/.vim"

data/features/resolve_dependencies/upgrade_outdated_dependencies.feature

@@ -40,7 +40,6 @@ Feature: Update outdated dependencies of Vim plugins
       $B_uri (0.0)
       $L_uri (0.4)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$A_uri" version "0.0" is deployed to "$home/.vim"
     And a flavor "$B_uri" version "0.0" is deployed to "$home/.vim"
     And a flavor "$L_uri" version "0.4" is deployed to "$home/.vim"
@@ -81,7 +80,6 @@ Feature: Update outdated dependencies of Vim plugins
       $L_uri (0.5)
       $X_uri (0.0)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$A_uri" version "0.0" is deployed to "$home/.vim"
     And a flavor "$B_uri" version "0.0" is deployed to "$home/.vim"
     And a flavor "$L_uri" version "0.5" is deployed to "$home/.vim"

data/features/resolve_dependencies/version_conflict.feature

@@ -31,7 +31,6 @@ Feature: Version conflict
         $foo_uri ~> 2.0 is required by $qux_uri
       Please resolve the conflict.
       """
-    And a bootstrap script is not created in "$home/.vim"
     And a flavor "$foo_uri" is not deployed to "$home/.vim"
     And a flavor "$bar_uri" is not deployed to "$home/.vim"
     And a flavor "$qux_uri" is not deployed to "$home/.vim"
@@ -59,6 +58,5 @@ Feature: Version conflict
         $foo_uri >= 2.0 is required by you
       Please resolve the conflict.
       """
-    And a bootstrap script is not created in "$home/.vim"
     And a flavor "$foo_uri" is not deployed to "$home/.vim"
     And a flavor "$bar_uri" is not deployed to "$home/.vim"

data/features/step_definitions/cli_steps.rb

@@ -7,7 +7,12 @@ Then 'it should pass' do
 end
 
 Then /^it should (pass|fail) with template:$/ do |pass_fail, template|
-  self.__send__("assert_#{pass_fail}ing_with", expand(template))
+  expect(last_command_started).to have_output(an_output_string_including(expand(template)))
+  if pass_fail == 'pass'
+    expect(last_command_started).to be_successfully_executed
+  else
+    expect(last_command_started).not_to be_successfully_executed
+  end
 end
 
 When /^I run `(.*)` \(variables expanded\)$/ do |command|

data/features/step_definitions/dependency_steps.rb

@@ -1,5 +1,6 @@
 Then /^a dependency "(.*)" is stored in "(.*)"$/ do |repo_name, deps_path|
+  cache_path = "#{deps_path}/#{repo_name.zap}"
   steps %Q{
-    Then a directory named "#{deps_path}/#{repo_name.zap}" should exist
+    Then a directory named "#{path_for_step(cache_path)}" should exist
   }
 end

data/features/step_definitions/directory_steps.rb

@@ -1,5 +1,5 @@
 When /^I delete the directory "([^"]*)"$/ do |dir_name|
-  in_current_dir do
+  cd('.') do
     # FileUtils#rmdir cannot delete non-empty directories.
     # TODO: Use aruba's "I remove the directory" step.
     #       Currently its implementation cannot delete git repositories.

data/features/step_definitions/file_steps.rb

@@ -1,9 +1,9 @@
 Given /^an executable file named "(.*)" with:$/ do |file_path, content|
   steps %Q{
-    Given a file named "#{file_path}" with:
+    Given a file named "#{path_for_step(file_path)}" with:
       """
       #{content}
       """
   }
-  File.chmod(0755, File.join([current_dir, file_path]))
+  File.chmod(0755, File.join([expand_path('.'), file_path]))
 end

data/features/step_definitions/flavor_steps.rb

@@ -18,7 +18,11 @@ Given /^the repository "([^"]*)" has versions "([^"]*)"$/ do |basename, versions
 end
 
 Given /^the repository "([^"]*)" has versions "([^"]*)" and a flavorfile:$/ do |basename, versions, flavorfile_content|
-  add_new_versions_to_repo(basename, versions, flavorfile_content)
+  add_new_versions_to_repo(basename, versions, flavorfile_content, :new)
+end
+
+Given /^the repository "([^"]*)" has versions "([^"]*)" and an old name flavorfile:$/ do |basename, versions, flavorfile_content|
+  add_new_versions_to_repo(basename, versions, flavorfile_content, :old)
 end
 
 Given /^a (?:(?:GitHub|local) )?repository "([^"]*)" with versions "([^"]*)"$/ do |basename, versions|
@@ -38,6 +42,16 @@ Given /^a (?:(?:GitHub|local) )?repository "([^"]*)" with versions "([^"]*)" and
   }
 end
 
+Given /^a (?:(?:GitHub|local) )?repository "([^"]*)" with versions "([^"]*)" and an old name flavorfile:$/ do |basename, versions, flavorfile_content|
+  steps %Q{
+    Given a repository "#{basename}"
+    And the repository "#{basename}" has versions "#{versions}" and an old name flavorfile:
+      """
+      #{flavorfile_content}
+      """
+  }
+end
+
 Given /^"([^"]*)" version "([^"]*)" is released$/ do |basename, version|
   steps %Q{
     Given the repository "#{basename}" has versions "#{version}"
@@ -58,21 +72,22 @@ Given /^a repository "([^"]*)" from offline cache$/ do |repo_name|
   repository_path = make_repo_path(repo_name).sub(expand('$tmp/'), '')
   sh <<-"END"
     {
-      git clone --quiet --no-checkout 'vendor/#{repo_name}' '#{current_dir}/#{repository_path}'
+      git clone --quiet --no-checkout 'vendor/#{repo_name}' '#{expand_path('.')}/#{repository_path}'
     } >/dev/null
   END
 end
 
 Given /^I disable network to the original repository of "([^"]*)"$/ do |basename|
   steps %Q{
-    Given I delete the directory "#{make_repo_path(basename)}"
+    Given I delete the directory "#{path_for_step(make_repo_path(basename))}"
   }
 end
 
 When /^I create a file named "([^"]*)" in "([^"]*)" deployed to "([^"]*)"$/ do |file_name, v_repo_name, v_vimfiles_path|
   flavor_path = make_flavor_path(expand(v_vimfiles_path), expand(v_repo_name))
+  file_path = "#{flavor_path}/#{file_name}"
   steps %Q{
-    When I write to "#{flavor_path}/#{file_name}" with:
+    When I write to "#{path_for_step(file_path)}" with:
       """
       """
   }
@@ -82,24 +97,24 @@ Then /^a flavor "([^"]*)" version "([^"]*)" is deployed to "([^"]*)"$/ do |v_rep
   flavor_path = make_flavor_path(expand(v_vimfiles_path), expand(v_repo_name))
   basename = expand(v_repo_name).split('/').last.sub(/^vim-/, '')
   steps %Q{
-    Then the file "#{flavor_path}/doc/#{basename}.txt" should contain:
+    Then the file "#{path_for_step(flavor_path)}/doc/#{basename}.txt" should contain:
       """
       *#{basename}* #{version}
       """
-    Then a file named "#{flavor_path}/doc/tags" should exist
+    Then a file named "#{path_for_step(flavor_path)}/doc/tags" should exist
   }
 end
 
 Then /^a flavor "([^"]*)" is not deployed to "([^"]*)"$/ do |v_repo_name, v_vimfiles_path|
   flavor_path = make_flavor_path(expand(v_vimfiles_path), expand(v_repo_name))
   steps %Q{
-    Then a directory named "#{flavor_path}" should not exist
+    Then a directory named "#{path_for_step(flavor_path)}" should not exist
   }
 end
 
 Then /^"([^"]*)" version "([^"]*)" is (?:(not) )?cached$/ do |v_repo_name, version, p|
   d = make_cached_repo_path(expand(v_repo_name), expand('$home').to_stash_path)
-  (system <<-"END").should == (p != 'not')
+  expect(system <<-"END").to equal(p != 'not')
     {
       cd '#{d}' &&
       git rev-list --quiet '#{version}'
@@ -109,7 +124,8 @@ end
 
 Then /^a file named "([^"]*)" (should(?: not)?) exist in "([^"]*)" deployed to "([^"]*)"$/ do |file_name, should, v_repo_name, v_vimfiles_path|
   flavor_path = make_flavor_path(expand(v_vimfiles_path), expand(v_repo_name))
+  file_path = "#{flavor_path}/#{file_name}"
   steps %Q{
-    Then a file named "#{flavor_path}/#{file_name}" #{should} exist
+    Then a file named "#{path_for_step(file_path)}" #{should} exist
   }
 end

data/features/step_definitions/flavorfile_steps.rb

@@ -1,6 +1,15 @@
 Given 'a flavorfile with:' do |content|
   steps %Q{
-    Given a file named "#{'.'.to_flavorfile_path}" with:
+    Given a file named "#{path_for_step(expand_path('.').to_flavorfile_path)}" with:
+      """
+      #{expand(content)}
+      """
+  }
+end
+
+Given 'an old name flavorfile with:' do |content|
+  steps %Q{
+    Given a file named "#{path_for_step("#{expand_path('.')}/VimFlavor")}" with:
       """
       #{expand(content)}
       """

data/features/step_definitions/lockfile_steps.rb

@@ -1,6 +1,15 @@
 Given 'a lockfile with:' do |content|
   steps %Q{
-    Given a file named "#{'.'.to_lockfile_path}" with:
+    Given a file named "#{path_for_step(expand_path('.').to_lockfile_path)}" with:
+      """
+      #{expand(content)}
+      """
+  }
+end
+
+Given 'an old name lockfile with:' do |content|
+  steps %Q{
+    Given a file named "#{path_for_step("#{expand_path('.')}/VimFlavor.lock")}" with:
       """
       #{expand(content)}
       """
@@ -18,7 +27,7 @@ end
 
 Given 'I delete the lockfile' do
   steps %Q{
-    Given I remove the file "#{'.'.to_lockfile_path}"
+    Given I remove the file "#{path_for_step(expand_path('.').to_lockfile_path)}"
   }
 end
 
@@ -34,7 +43,7 @@ end
 Then /^(?:a|the) lockfile is (?:created|updated) with:$/ do |content|
   # For some reason, Cucumber drops the last newline from every docstring...
   steps %Q{
-    Then the file "#{'.'.to_lockfile_path}" should contain exactly:
+    Then the file "#{path_for_step(expand_path('.').to_lockfile_path)}" should contain exactly:
       """
       #{content == '' ? '' : expand(content) + "\n"}
       """
@@ -42,11 +51,11 @@ Then /^(?:a|the) lockfile is (?:created|updated) with:$/ do |content|
 end
 
 Then /^(?:a|the) lockfile is (?:created|updated) and matches with:$/ do |content|
-  check_file_content('.'.to_lockfile_path, /#{content}/, true)
+  expect(path_for_step(expand_path('.').to_lockfile_path)).to have_file_content(/#{content}/)
 end
 
 Then /^(?:a|the) lockfile is not created$/ do
   steps %Q{
-    Then a file named "#{'.'.to_lockfile_path}" should not exist
+    Then a file named "#{path_for_step(expand_path('.').to_lockfile_path)}" should not exist
   }
 end

data/features/support/env.rb

@@ -1,13 +1,17 @@
 require 'aruba/api'
 require 'aruba/cucumber'
 require 'fileutils'
+require 'pathname'
 require 'vim-flavor'
 
 class FakeUserEnvironment
   include Vim::Flavor::ShellUtility
 
-  def add_new_versions_to_repo(basename, versions, flavorfile_content = nil)
+  def add_new_versions_to_repo(basename, versions, flavorfile_content = nil, naming_style = :new)
     repository_path = make_repo_path(basename)
+    flavorfile_path = naming_style == :new ?
+      repository_path.to_flavorfile_path :
+      "#{repository_path}/VimFlavor"
     doc_name = basename.split('/').last.sub(/^vim-/, '')
     sh <<-"END"
       {
@@ -19,10 +23,10 @@ class FakeUserEnvironment
           git add doc
           #{
             %Q{
-              cat <<'FF' >#{'.'.to_flavorfile_path}
+              cat <<'FF' >#{flavorfile_path}
 #{expand(flavorfile_content)}
 FF
-              git add #{'.'.to_flavorfile_path}
+              git add #{flavorfile_path}
             } if flavorfile_content
           }
           git commit -m "Version $v"
@@ -44,6 +48,16 @@ FF
     }
   end
 
+  def path_for_step(path)
+    cwd = Pathname.new(expand_path('.'))
+    pathd = Pathname.new(path)
+    if not pathd.absolute?
+      pathd = cwd + pathd
+    end
+
+    pathd.relative_path_from(cwd).to_s
+  end
+
   def make_cached_repo_path(repo_name, stash_path)
     "#{stash_path}/repos/#{repo_name.zap}"
   end
@@ -68,22 +82,18 @@ end
 Before do
   variable_table['version'] = Vim::Flavor::VERSION
 
-  variable_table['tmp'] = File.absolute_path(current_dir)
+  variable_table['tmp'] = File.absolute_path(expand_path('.'))
 
   steps %Q{
     Given a directory named "home"
   }
-  variable_table['home'] = File.absolute_path(File.join([current_dir, 'home']))
+  variable_table['home'] = File.absolute_path(File.join([expand_path('.'), 'home']))
 
   @aruba_timeout_seconds = 5
-end
 
-Aruba.configure do |config|
-  config.before_cmd do |cmd|
-    set_env 'VIM_FLAVOR_HOME', variable_table['home']
-    set_env 'VIM_FLAVOR_GITHUB_URI_PREFIX', expand('file://$tmp/repos/')
-    set_env 'VIM_FLAVOR_GITHUB_URI_SUFFIX', ''
-  end
+  set_environment_variable 'VIM_FLAVOR_HOME', variable_table['home']
+  set_environment_variable 'VIM_FLAVOR_GITHUB_URI_PREFIX', expand('file://$tmp/repos/')
+  set_environment_variable 'VIM_FLAVOR_GITHUB_URI_SUFFIX', ''
 end
 
 World do

data/features/testing_vim_plugins/README.md

@@ -3,7 +3,7 @@
 1. Write tests for your Vim plugin with
    [vim-vspec](https://github.com/kana/vim-vspec).
 2. Declare dependencies of your Vim plugin as a [flavorfile](flavorfile), and
-   save it as `VimFlavor` in the root of your Vim plugin.
+   save it as `Flavorfile` in the root of your Vim plugin.
 3. Run `vim-flavor test`.
 
 
@@ -14,15 +14,16 @@
 It is hard to test Vim plugins, because there are a few problems:
 
 * It is hard to write readable and maintainable test code in Vim script, even
-  for skilled users.  Because Vim script is not expressive as script languages
-  like Ruby and others.
+  for skilled users.  Because Vim script is not expressive as other script
+  languages like Ruby.
 * Each test must be run in an isolated environment to guarantee the same
   results for every time and everywhere.  So that all settings including vimrc
-  and plugins must be ignored.  User's viminfo must not be read and written
-  too.
+  and plugins of yours must be ignored.  Your viminfo also must not be read
+  and written to avoid unexpected test failures and unexpectedly overwritten
+  of registers and marks you used.
 * Some plugins require other plugins at runtime.  Such dependencies must be
   resolved, but they must be installed into a temporary place to avoid
-  corrupting user's settings.  And `'runtimepath'` must be configured
+  corrupting your environment.  And `'runtimepath'` must be configured
   carefully for both dependencies and plugins under development.
 
 Therefore it is hard to do right testing for Vim plugins from scratch.  As