Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

Manage downtimes with dst (recurrent and realtime) #5780

Merged
merged 8 commits into from
Oct 18, 2017
4 changes: 4 additions & 0 deletions behat.yml
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,10 @@ default:
paths: [ %paths.base%/features/DowntimeStartAndStop.feature ]
contexts: [ DowntimeStartAndStopContext ]

downtime_dst:
paths: [ %paths.base%/features/DowntimeDST.feature ]
contexts: [ DowntimeDSTContext ]

command_arguments:
paths: [ %paths.base%/features/CommandArguments.feature ]
contexts: [ CommandArgumentsContext ]
Expand Down
76 changes: 76 additions & 0 deletions features/DowntimeDST.feature
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
Feature: Downtime DST
As a Centreon user
I want to be certain that the downtimes work correctly with DST
To release quality products

Background:
Given I am logged in a Centreon server located at "Europe/Paris"
And a passive service is monitored


# summer changing time

@critical
Scenario: recurrent downtime starting on summer changing time
Given a recurrent downtime starting on summer changing time
When downtime is approaching
Then the downtime is scheduled

@critical
Scenario: recurrent downtime ending on summer changing time
Given a recurrent downtime ending on summer changing time
When downtime is approaching
Then the downtime is scheduled

@critical
Scenario: recurrent downtime starting and ending on summer changing time
Given a recurrent downtime starting and ending on summer changing time
When downtime is approaching
Then the downtime is not scheduled

@critical
Scenario: recurrent downtime during all day on summer changing date
Given a recurrent downtime during all day on summer changing date
When downtime is approaching
Then the downtime is scheduled

@critical
Scenario: recurrent downtime of next day of summer changing date
Given a recurrent downtime during all day on summer changing date is scheduled
And a recurrent downtime of next day of summer changing date
When downtime is approaching
Then the downtime is scheduled


# winter changing time

@critical
Scenario: recurrent downtime starting on winter changing time
Given a recurrent downtime starting on winter changing time
When downtime is approaching
Then the downtime is scheduled

@critical
Scenario: recurrent downtime ending on winter changing time
Given a recurrent downtime ending on winter changing time
When downtime is approaching
Then the downtime is scheduled

@critical
Scenario: recurrent downtime starting and ending on winter changing time
Given a recurrent downtime starting and ending on winter changing time
When downtime is approaching
Then the downtime is scheduled

@critical
Scenario: recurrent downtime during all day on winter changing date
Given a recurrent downtime during all day on winter changing date
When downtime is approaching
Then the downtime is scheduled

@critical
Scenario: recurrent downtime of next day of winter changing date
Given a recurrent downtime during all day on winter changing date is scheduled
And a recurrent downtime of next day of winter changing date
When downtime is approaching
Then the downtime is scheduled
Loading