features/notification_rules.feature in flapjack-0.7.2 vs features/notification_rules.feature in flapjack-0.7.3

@@ -1,13 +1,13 @@
 @notification_rules @resque
 Feature: Notification rules on a per contact basis
 
   Background:
     Given the following users exist:
-      | id  | first_name | last_name | email             | sms          |
-      | 1   | Malak      | Al-Musawi | [e-mail] | [phone] |
-      | 2   | Imani      | Farooq    | [e-mail] | [phone] |
+      | id  | first_name | last_name | email             | sms          | timezone         |
+      | 1   | Malak      | Al-Musawi | [e-mail] | [phone] | Asia/Baghdad     |
+      | 2   | Imani      | Farooq    | [e-mail] | [phone] | Europe/Moscow    |
 
     And the following entities exist:
       | id  | name | contacts |
       | 1   | foo  | 1        |
       | 2   | bar  | 1,2      |
@@ -23,10 +23,10 @@
       | 2  | bar      |             |               | sms,email        | true              |                    |                   |
       | 3  | baz      |             | email         | sms,email        |                   |                    |                   |
 
   @time_restrictions @time
   Scenario: Alerts only during specified time restrictions
-    Given the timezone is America/New_York
+    Given the timezone is Asia/Baghdad
     And   the time is February 1 2013 6:59
     And   the check is check 'ping' on entity 'foo'
     And   the check is in an ok state
     And   a critical event is received
     Then  no email alerts should be queued for [e-mail]