dkdeploy-core 8.0.0

data/features/bower.feature

@@ -0,0 +1,52 @@
+Feature: Test tasks for namespace 'bower'
+
+  Background:
+    Given a test app with the default configuration
+
+  Scenario: Given a bower.js file, running cap bower:run['install', 'htdocs'] results in Bower (v1.5.2) installing components
+    When I successfully run `cap dev "bower:run[install,htdocs]"`
+    Then the output should contain "bower jquery#2.1.4             install jquery#2.1.4"
+    And a file named "htdocs/bower_components/jquery/dist/jquery.js" should exist
+
+  Scenario: Running arbitrarily Bower commands
+    Given I run `cap dev "bower:run[install,htdocs]"`
+    When I run `cap dev "bower:run[list,htdocs]"`
+    Then the output should contain "dkdeploy-core-bower-fixture-file#0.0.1"
+    And the output should contain "└── jquery#2.1.4"
+    When I successfully run `cap dev "bower:run[lookup bootstrap,htdocs]"`
+    Then the output should contain "bootstrap https://github.com/twbs/bootstrap.git"
+
+  Scenario: Running arbitrarily Bower commands with multiple bower.json files
+    Given the default aruba exit timeout is 120 seconds
+    And a file named "another_directory/bower.json" with:
+    """
+    {
+      "name": "dkdeploy-core-another-bower-fixture-file",
+      "version": "0.0.1",
+      "authors": [
+        "Random Coder <mail@example.com>"
+      ],
+      "description": "This is another fixture bower.js file for dkdeploy-core",
+      "moduleType": [
+        "globals"
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "bootstrap": "3.3.5"
+      }
+    }
+    """
+    When I extend the development capistrano configuration variable bower_paths with value ['htdocs', 'another_directory']
+    And I successfully run `cap dev "bower:run_all[install]"`
+    Then a file named "htdocs/bower_components/jquery/dist/jquery.js" should exist
+    And a file named "another_directory/bower_components/bootstrap/dist/css/bootstrap.css" should exist
+
+  Scenario: Running a Bower command with missing bower.json file
+    Given I successfully run `rm htdocs/bower.json`
+    When I successfully run `cap dev "bower:run[install,htdocs]"`
+    Then the output should contain "Skipping directory htdocs because it does not contain a bower.json file."
+
+  Scenario: Running a Bower command with missing directory configured
+    Given I successfully run `rm htdocs/bower.json`
+    When I successfully run `cap dev "bower:run[install,i_do_not_exist]"`
+    Then the output should contain "Skipping directory i_do_not_exist because it does not exist."

data/features/current_folder.feature

@@ -0,0 +1,17 @@
+Feature: Test tasks for namespace 'current_folder'
+
+  Background:
+    Given a test app with the default configuration
+    And the remote server is cleared
+
+  Scenario: Do not remove current folder if it is symlinked
+    Given the project is deployed
+    And I store the symlink source of current
+    When I successfully run `cap dev current_folder:remove_unlesss_symlinked`
+    Then the symlink source of current should not have changed
+
+  Scenario: Remove current folder if it's not symlinked
+    Given a remote directory named "current_path"
+    When I successfully run `cap dev current_folder:remove_unlesss_symlinked`
+    Then a remote directory named "current_path" should not exist
+

data/features/db.feature

@@ -0,0 +1,93 @@
+Feature: Test tasks for namespace 'db'
+
+	Background:
+		Given a test app with the default configuration
+		And the remote server is cleared
+		And I want to use the database `dkdeploy_core`
+
+	Scenario: Check if settings upload is possible with settings given as arguments
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		Then a remote file named "shared_path/config/db_settings.dev.yaml" should exist
+
+	Scenario: Check if settings upload is possible with settings given interactively
+		When I run `cap dev db:upload_settings` interactively
+		And I type "127.0.0.1"
+		And I type "3306"
+		And I type "dkdeploy_core"
+		And I type "root"
+		And I type "ilikerandompasswords"
+		And I type "utf8"
+		And I close the stdin stream
+		Then the exit status should be 0
+		And a remote file named "shared_path/config/db_settings.dev.yaml" should exist
+
+	Scenario: Check if settings upload is possible with settings given as enviroment variables
+		When I successfully run `cap dev db:upload_settings DB_HOST=127.0.0.1 DB_PORT=3306 DB_NAME=dkdeploy_core DB_USERNAME=root DB_PASSWORD=ilikerandompasswords DB_CHARSET=utf8`
+		Then a remote file named "shared_path/config/db_settings.dev.yaml" should exist
+
+	Scenario: Reading missing database config file
+		When I run `cap dev db:read_db_settings`
+		Then the output should contain "Unable to locate database config file on remote server."
+
+	Scenario: Reading existing database config file
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		Then a file named "temp/db_settings.dev.yaml" should not exist
+		When I run `cap dev db:read_db_settings`
+		Then a file named "temp/db_settings.dev.yaml" should exist
+
+	Scenario: Check if password will not appear in log
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		Then the output should not contain "ilikerandompasswords"
+
+	Scenario: Check content of database after uploading a script
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I run `cap dev "db:update[temp,dkdeploy_core.sql.gz]"`
+		And I wait 5 seconds to let the database commit the transaction
+		Then the database should have a table `demo_table` with column `demo_column`
+		And the database should not have a table `wrong_table` with column `wrong_column`
+
+	Scenario: Check dumping complete database without cache table content
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I successfully run `cap dev "db:update[temp,dkdeploy_core.sql.gz]"`
+		And I successfully run `cap dev db:download`
+		Then a file matching %r<database-dev-content.*sql.*gz> should exist
+		And a file matching %r<database-dev-structure.*sql.*gz> should exist
+
+	Scenario: Check dumping only structure of database
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I successfully run `cap dev "db:update[temp,dkdeploy_core.sql.gz]"`
+		And I successfully run `cap dev db:download_structure`
+		Then a file matching %r<database-dev-structure.*sql.*gz> should exist
+		And a file matching %r<database-dev-content.*sql.*gz> should not exist
+
+	Scenario: Check dumping content of database
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I successfully run `cap dev "db:update[temp,dkdeploy_core.sql.gz]"`
+		And I successfully run `cap dev db:download_content`
+		Then a file matching %r<database-dev-content.*sql.*gz> should exist
+		And a file matching %r<database-dev-structure.*.sql.*gz> should not exist
+
+	Scenario: Check dumping tables
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I successfully run `cap dev "db:update[temp,dkdeploy_core.sql.gz]"`
+		When I successfully run `cap dev db:dump_table[demo_table]`
+		Then a file matching %r<database-dev-demo_table.*sql.*gz> should exist
+
+	Scenario: Check dumping tables to a specific file
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I successfully run `cap dev "db:update[temp,dkdeploy_core.sql.gz]"`
+		When I successfully run `cap dev db:download_tables[demo_table,temp,demo_table.sql]`
+		Then a file matching %r<demo_table.*sql> should exist
+
+	Scenario: Check database for preseed structure
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I successfully run `cap dev db:add_default_structure`
+		And I wait 5 second to let the database commit the transaction
+		Then the database should have a table `preseed_table` with column `value`
+
+	Scenario: Check database for preseed content
+		When I successfully run `cap dev "db:upload_settings[127.0.0.1,3306,dkdeploy_core,root,ilikerandompasswords,utf8]"`
+		And I successfully run `cap dev db:add_default_structure`
+		And I successfully run `cap dev db:add_default_content`
+		And I wait 5 second to let the database commit the transaction
+		Then the database should have a value `first preseed value` in table `preseed_table` for column `value`

data/features/deploy.feature

@@ -0,0 +1,48 @@
+Feature: Test tasks for namespace 'deploy'
+
+	Background:
+		Given a test app with the default configuration
+		And the remote server is cleared
+
+	Scenario: Check if the main capistrano directory structure has been created
+		When I successfully run `cap dev deploy`
+		Then a remote directory named "deploy_path/releases" should exist
+		Then a remote directory named "deploy_path/shared" should exist
+
+	Scenario: Check if the main capistrano symlink structure has been created
+		When I successfully run `cap dev deploy`
+		Then a remote symlink named "deploy_path/current" should exist
+
+	Scenario: Check if the complete directory structure has been successfully deployed
+		When I successfully run `cap dev deploy`
+		Then a remote directory named "current_path/catalog" should exist
+
+	Scenario: Check if the complete file structure has been successfully deployed
+		When I successfully run `cap dev deploy`
+		Then a remote file named "current_path/index.html" should exist
+
+	Scenario: Check if the not wanted files have been excluded
+		When I successfully run `cap dev deploy`
+		Then a remote file named "current_path/Gemfile" should not exist
+		Then a remote file named "current_path/Gemfile.lock" should not exist
+
+	Scenario: Check if the not wanted directories have been excluded
+		When I successfully run `cap dev deploy`
+		Then a remote directory named "current_path/.hidden" should not exist
+		Then a remote directory named "current_path/catalog/.hidden" should not exist
+		Then a remote directory named "test_app/tmp_path" should not exist
+
+	Scenario Outline: Check if I can deploy a project with different root sources
+		When I extend the development capistrano configuration variable copy_source with value <configuration_value>
+		And I successfully run `cap dev deploy`
+		Then a remote directory named "<remote_directory>/<target_path>" should exist
+
+		Examples:
+			| configuration_value | target_path | remote_directory |
+			| '.'                 | htdocs      | current_path     |
+			| 'htdocs'            | catalog     | current_path     |
+
+	Scenario: Test default deployment behaviour
+		Given I extend the development capistrano configuration from the fixture file default_deployment_behaviour.rb
+		And I run `cap dev deploy`
+		Then the exit status should be 0

data/features/enhanced_symlinks.feature

@@ -0,0 +1,17 @@
+Feature: Test enhanced symlink tasks
+
+	Background:
+		Given a test app with the default configuration
+		And the remote server is cleared
+		And a remote empty file named "shared_path/sample/sample_file"
+		And a remote directory named "shared_path/sample_folder"
+		When I extend the development capistrano configuration variable enhanced_linked_files with value { 'sample/sample_file' => 'works/fine' }
+		And I extend the development capistrano configuration variable enhanced_linked_dirs with value { 'sample_folder' => 'fine/as_well' }
+
+	Scenario: Check enhanced symlinking of files
+		When I successfully run `cap dev deploy`
+		Then a remote file named "current_path/works/fine" should exist
+
+	Scenario: Check enhanced symlinking of directories
+		When I successfully run `cap dev deploy`
+		Then a remote directory named "current_path/fine/as_well" should exist

data/features/error_handlers.feature

@@ -0,0 +1,59 @@
+Feature: Test tasks for error handlers
+
+	Background:
+		Given a test app with the default configuration
+		And the remote server is cleared
+		And I extend the development capistrano configuration from the fixture file default_deployment_behaviour.rb
+		And the project is deployed
+
+	Scenario: When deployment fails before symlinking the new release
+		Given I store the symlink source of current
+		And I provoke an exception for testing purposes before symlinking the new release
+		And a remote file named "shared_path/config/maintenance.json" should not exist
+		Then I run `cap dev deploy`
+		And the output should contain "Failing this deployment on purpose!"
+		And the exit status should not be 0
+		And a remote file named "shared_path/config/maintenance.json" should not exist
+		And the symlink source of current should not have changed
+		And the exit status should not be 0
+
+	Scenario: When deployment fails after symlinking the new release
+		Given I store the symlink source of current
+		And I provoke an exception for testing purposes after symlinking the new release
+		And a remote file named "shared_path/config/maintenance.json" should not exist
+		Then I run `cap dev deploy`
+		And the output should contain "Failing this deployment on purpose!"
+		And the exit status should not be 0
+		And a remote file named "shared_path/config/maintenance.json" should not exist
+		And the symlink source of current should not have changed
+
+	Scenario: Deployment rollback to last stable version on failure when failing before symlinking
+		Given I successfully run `cap dev deploy`
+ 		And I successfully run `cap dev deploy`
+ 		And I successfully run `cap dev deploy`
+		And I store the symlink source of current
+		And I provoke an exception for testing purposes before symlinking the new release
+		Then I run `cap dev deploy`
+		And the output should contain "Failing this deployment on purpose!"
+		And the exit status should not be 0
+		And the symlink source of current should not have changed
+
+	Scenario: Deployment rollback to last stable version on failure when failing after symlinking
+		Given I successfully run `cap dev deploy`
+ 		And I successfully run `cap dev deploy`
+ 		And I successfully run `cap dev deploy`
+		And I store the symlink source of current
+		And I provoke an exception for testing purposes after symlinking the new release
+		Then I run `cap dev deploy`
+		And the output should contain "Failing this deployment on purpose!"
+		And the exit status should not be 0
+		And the symlink source of current should not have changed
+
+	Scenario: Deployment do not execute project task at rollback behaviour
+		Given I successfully run `cap dev deploy`
+ 		And I successfully run `cap dev deploy`
+		And I provoke an exception for testing purposes before symlinking the new release
+		And I extend the development capistrano configuration from the fixture file add_output_after_create_symlink.rb
+		Then I run `cap dev deploy`
+		And the output should not contain "Task 'deploy:symlink:release' executed"
+		And the exit status should not be 0

data/features/file_access.feature

@@ -0,0 +1,120 @@
+Feature: Test tasks for namespace 'file_permissions'
+
+	Background:
+		Given a test app with the default configuration
+		And the remote server is cleared
+		And the project is deployed
+		And I extend the development capistrano configuration from the fixture file custom_file_access.rb
+
+  # owner/group of shared path
+	Scenario: Check if the default owner and group of shared path are set correctly
+		Given I extend the development capistrano configuration variable default_file_access_owner_of_shared_path with value 'test-user'
+		And I extend the development capistrano configuration variable default_file_access_group_of_shared_path with value 'test-group'
+		And I successfully run `cap dev file_access:set_owner_group_of_shared_path`
+		Then remote owner of "shared_path" should be "test-user"
+		And remote group of "shared_path" should be "test-group"
+
+  # owner/group of release path
+	Scenario: Check if the default owner and group of release path are set correctly
+		Given I extend the development capistrano configuration variable default_file_access_owner_of_release_path with value 'test-user'
+		And I extend the development capistrano configuration variable default_file_access_group_of_release_path with value 'test-group'
+		And I successfully run `cap dev file_access:set_owner_group_of_release_path`
+		Then remote owner of "deploy_path/current" should be "test-user"
+		And remote owner of "current_path/index.html" should be "test-user"
+		And remote owner of "current_path/catalog" should be "test-user"
+		And remote group of "deploy_path/current" should be "test-group"
+		And remote group of "current_path/index.html" should be "test-group"
+		And remote group of "current_path/catalog" should be "test-group"
+
+  # file permission of shared path
+	Scenario: Check if the default file access properties on shared contain the following permissions
+		Given I extend the development capistrano configuration from the fixture file custom_file_access.rb
+		And I successfully run `cap dev file_access:set_permissions`
+		Then remote permissions of "shared_path" should contain "user" "read"
+		And remote permissions of "shared_path" should contain "user" "write"
+		And remote permissions of "shared_path" should contain "user" "execute"
+		And remote permissions of "shared_path" should contain "group" "read"
+		And remote permissions of "shared_path" should contain "group" "execute"
+
+  # file permission of release path
+	Scenario: Check if the default file access properties on release contain the following permissions
+		Given I extend the development capistrano configuration from the fixture file custom_file_access.rb
+		And I successfully run `cap dev file_access:set_permissions`
+		Then remote permissions of "current_path/index.html" should contain "user" "read"
+		And remote permissions of "current_path/index.html" should contain "user" "write"
+		And remote permissions of "current_path/catalog" should contain "user" "execute"
+		And remote permissions of "current_path/index.html" should contain "group" "read"
+		And remote permissions of "current_path/catalog" should contain "group" "execute"
+
+	Scenario: Check if the default file access properties on release does not contain the following permissions
+		Given I extend the development capistrano configuration from the fixture file custom_file_access.rb
+		And I successfully run `cap dev file_access:set_permissions`
+		Then remote permissions of "current_path/index.html" should not contain "user" "execute"
+		And remote permissions of "current_path/index.html" should not contain "group" "write"
+		And remote permissions of "current_path/index.html" should not contain "group" "execute"
+		And remote permissions of "current_path/index.html" should not contain "others" "read"
+		And remote permissions of "current_path/index.html" should not contain "others" "write"
+
+	Scenario: Check if the default file access properties on shared does not contain the following permissions
+		Given I extend the development capistrano configuration from the fixture file custom_file_access.rb
+		And I successfully run `cap dev file_access:set_permissions`
+		Then remote permissions of "shared_path" should not contain "group" "write"
+		And remote permissions of "shared_path" should not contain "others" "read"
+		And remote permissions of "shared_path" should not contain "others" "write"
+		And remote permissions of "shared_path" should not contain "others" "execute"
+
+	Scenario: Check if the custom file owner and group are set correctly
+		When I successfully run `cap dev file_access:set_custom_access`
+		Then remote owner of "current_path/catalog" should be "test-user"
+		And remote group of "current_path/catalog" should be "test-group"
+
+	Scenario: Check if the custom file access properties on release contain the following permissions
+		When I successfully run `cap dev file_access:set_custom_access`
+		Then remote permissions of "current_path/catalog" should contain "user" "read"
+		And remote permissions of "current_path/catalog" should contain "user" "write"
+		And remote permissions of "current_path/catalog" should contain "user" "execute"
+		And remote permissions of "current_path/catalog" should contain "group" "read"
+		And remote permissions of "current_path/catalog" should contain "group" "write"
+		And remote permissions of "current_path/catalog" should contain "group" "execute"
+		And remote permissions of "current_path/catalog" should contain "others" "read"
+
+	Scenario: Check if the custom file access properties on release does not contain the following permissions
+		When I successfully run `cap dev file_access:set_custom_access`
+		Then remote permissions of "current_path/catalog" should not contain "others" "write"
+		And remote permissions of "current_path/catalog" should not contain "others" "execute"
+
+	Scenario: Check if the set_custom_access task skips over not existing folders
+		Given I extend the development capistrano configuration variable custom_file_access with value {app: {release_path: {catalog: {mode: 'u+rwx,g+rwx,o-wx'}, not_existing: {mode: 'u+rwx,g+rwx,o-wx'}}}}
+		And a remote directory named "releases_path/not_existing" should not exist
+		When I successfully run `cap dev file_access:set_custom_access`
+		Then the output should contain "The resource /var/www/dkdeploy/current/not_existing does not exist on host dkdeploy-core.dev"
+		And the output should not contain "sudo chmod  u+rwx,g+rwx,o-wx /var/www/dkdeploy/current/not_existing"
+		And the output should contain "sudo chmod  u+rwx,g+rwx,o-wx /var/www/dkdeploy/current/catalog"
+
+	Scenario: Check if the selected_custom file_access_task skips with empty selected_custom_file_access
+		Given I extend the development capistrano configuration variable default_file_access_owner_of_shared_path with value 'test-user'
+		When I run `cap dev file_access:set_selected_custom_access`
+		Then the exit status should be 1
+		And the output should contain "The variable 'selected_custom_file_access' is empty. Aborting task..."
+
+	Scenario: Check if the selected_custom_file_access_task runs with configured selected_custom_file_access
+		Given I extend the development capistrano configuration variable default_file_access_owner_of_shared_path with value 'test-user'
+		And I extend the development capistrano configuration variable selected_custom_file_access with value [:catalog]
+		When I successfully run `cap dev file_access:set_selected_custom_access`
+		Then the output should contain "sudo chown -R test-user /var/www/dkdeploy/current/catalog"
+
+	Scenario: Check if the selected_custom_file_access task skips over not mentioned folders
+		Given I extend the development capistrano configuration variable default_file_access_owner_of_shared_path with value 'test-user'
+		And I extend the development capistrano configuration variable selected_custom_file_access with value ['another_directory']
+		When I successfully run `cap dev file_access:set_selected_custom_access`
+		Then the output should contain "Skipped setting custom_file_access permissions for 'catalog' because it is not mentioned in selected_custom_file_access!"
+		And the output should not contain "sudo chown -R test-user /var/www/dkdeploy/current/catalog"
+
+	Scenario: Check if the selected_custom_file_access task skips over not existing folders
+		Given I extend the development capistrano configuration variable custom_file_access with value {app: {release_path: {catalog: {mode: 'u+rwx,g+rwx,o-wx'}, not_existing: {mode: 'u+rwx,g+rwx,o-wx'}}}}
+		And I extend the development capistrano configuration variable selected_custom_file_access with value [:not_existing, :catalog]
+		And a remote directory named "releases_path/not_existing" should not exist
+		When I successfully run `cap dev file_access:set_selected_custom_access`
+		Then the output should contain "The resource /var/www/dkdeploy/current/not_existing does not exist on host dkdeploy-core.dev"
+		And the output should not contain "sudo chmod -R u+rwx,g+rwx,o-wx /var/www/dkdeploy/current/not_existing"
+		And the output should contain "sudo chmod -R u+rwx,g+rwx,o-wx /var/www/dkdeploy/current/catalog"

data/features/maintenance.feature

@@ -0,0 +1,25 @@
+Feature: Test tasks for namespace 'maintenance'
+
+	Background:
+		Given a test app with the default configuration
+		And the remote server is cleared
+		And the project is deployed
+
+	Scenario: Check if maintenance.json is created on server if I run maintenance:enable
+		When I successfully run `cap dev maintenance:enable`
+		Then a remote file named "shared_path/config/maintenance.json" should exist
+
+	Scenario: Check if maintenance.json is removed to the config directory if I run maintenance:disable
+		When I successfully run `cap dev maintenance:enable`
+		And I successfully run `cap dev maintenance:disable`
+		Then a remote file named "shared_path/config/maintenance.json" should not exist
+
+	Scenario: Check if maintenance.json is not removed on server if I run maintenance:disable in a permanent mode
+		When I successfully run `cap dev maintenance:enable_permanent`
+		And I successfully run `cap dev maintenance:disable`
+		Then a remote file named "shared_path/config/maintenance.json" should exist
+
+	Scenario: Check if maintenance.json is removed from the server if I run maintenance_disable_permanent in a permanent mode
+		When I successfully run `cap dev maintenance:enable_permanent`
+		And I successfully run `cap dev maintenance:disable_permanent`
+		Then a remote file named "shared_path/config/maintenance.json" should not exist

data/features/project_version.feature

@@ -0,0 +1,42 @@
+Feature: Test tasks for namespace 'project_version'
+
+	Background:
+		Given a test app with the default configuration
+		And the remote server is cleared
+		And the project is deployed
+
+	Scenario: upload the project version file
+		Given a file named "Version" with:
+		"""
+		1.0.0
+		"""
+		And I successfully run `cap dev project_version:update`
+		Then the remote file "current_path/Version" should contain exactly:
+		"""
+		1.0.0
+		"""
+
+	Scenario: update the project version file
+		Given a remote file named "Version" with:
+		"""
+		1.0.0
+		"""
+		And a file named "Version" with:
+		"""
+		2.0.0
+		"""
+		And I successfully run `cap dev project_version:update`
+		Then the remote file "current_path/Version" should contain exactly:
+		"""
+		2.0.0
+		"""
+
+	Scenario: change version file path and update the local version file
+		Given a remote directory named "current_path/version_file_directory"
+		And a file named "Version" with:
+		"""
+		1.0.0
+		"""
+		When I extend the development capistrano configuration variable version_file_path with value 'version_file_directory'
+		And I successfully run `cap dev project_version:update`
+		Then a remote file named "current_path/version_file_directory/Version" should exist