Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

Add test for rollback behaviour #49

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Vagrantfile
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ unless Vagrant.has_plugin?('vagrant-berkshelf')
abort
end

Vagrant.require_version '~> 2.0.0'
Vagrant.require_version '~> 2.0'
chef_version = '12.9.41'

Vagrant.configure(2) do |config|
Expand Down
8 changes: 8 additions & 0 deletions features/error_handlers.feature
Original file line number Diff line number Diff line change
Expand Up @@ -57,3 +57,11 @@ Feature: Test tasks for error handlers
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

Scenario: Rollback execute all tasks
Given I successfully run "cap dev deploy"
And I provoke an exception for testing purposes after symlinking the new release
And I extend the development capistrano configuration from the fixture file second_server.rb
Then I run `cap dev deploy`
And the output should not contain "Skipping task"
And the exit status should not be 0
1 change: 1 addition & 0 deletions spec/fixtures/capistrano/configuration/second_server.rb
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
server '192.168.156.180', roles: %w[web app backend db], primary: false