summaryrefslogtreecommitdiff
path: root/features/language/delayed_notifications.feature
blob: 87373d860997799868634b002fc84f9b52c3c073 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
@language @delayed_notifications
Feature: Delayed Notifications
  In order to not impact the system we are configuring unduly
  As a developer
  I want to be able to trigger an action on a resource only at the end of a run
  
  Scenario: Notify a resource from a single source
    Given a validated node
      And it includes the recipe 'delayed_notifications::notify_a_resource_from_a_single_source'
     When I run the chef-client
     Then the run should exit '0'
      And a file named 'notified_file.txt' should exist
      
  Scenario: Notify a resource from multiple sources
    Given a validated node
      And it includes the recipe 'delayed_notifications::notify_a_resource_from_multiple_sources'
     When I run the chef-client
     Then the run should exit '0'
      And a file named 'notified_file.txt' should contain 'bob dylan' only '1' time
  
  Scenario: Notify different resources for different actions
    Given a validated node
      And it includes the recipe 'delayed_notifications::notify_different_resources_for_different_actions'
     When I run the chef-client
     Then the run should exit '0'
      And a file named 'notified_file_2.txt' should exist
      And a file named 'notified_file_3.txt' should exist
  
  Scenario: Notify a resource that is defined later in the recipe
    Given a validated node
      And it includes the recipe 'delayed_notifications::forward_references'
     When I run the chef-client
     Then the run should exit '0'
      And a file named 'notified_file.txt' should exist

  Scenario: Notifying a resource that doesn't exist should fail before convergence starts
    Given a validated node
      And it includes the recipe 'delayed_notifications::invalid_forward_reference'
     When I run the chef-client
     Then the run should exit '1'
      And 'stdout' should not have 'should-not-execute'
      And a file named 'notified_file.txt' should not exist

  Scenario: Notifying a resource with invalid syntax should fail before convergence starts
    Given a validated node
      And it includes the recipe 'delayed_notifications::bad_syntax_notifies'
     When I run the chef-client
     Then the run should exit '1'
      And 'stdout' should not have 'should-not-execute'
      And a file named 'notified_file.txt' should not exist