This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 240
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(downtime): improve dst management with downtimes
- Loading branch information
Showing
7 changed files
with
648 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,132 @@ | ||
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: realtime downtime starting on summer changing time | ||
Given a downtime starting on summer changing time | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime starting on summer changing time | ||
Given a downtime starting on summer changing time | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime ending on summer changing time | ||
Given a downtime ending on summer changing time | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime ending on summer changing time | ||
Given a downtime ending on summer changing time | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime starting and ending on summer changing time | ||
Given a downtime starting and ending on summer changing time | ||
When recurrent downtime is applied | ||
Then the downtime is not scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime starting and ending on summer changing time | ||
Given a downtime starting and ending on summer changing time | ||
When realtime downtime is applied | ||
Then the downtime is not scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime during all day on summer changing date | ||
Given a downtime during all day on summer changing date | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime during all day on summer changing date | ||
Given a downtime during all day on summer changing date | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime of next day of summer changing date | ||
Given a downtime during all day on summer changing date is scheduled | ||
And a downtime of next day of summer changing date | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
|
||
|
||
# winter changing time | ||
|
||
@critical | ||
Scenario: recurrent downtime starting on winter changing time | ||
Given a downtime starting on winter changing time | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime starting on winter changing time | ||
Given a downtime starting on winter changing time | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime ending on winter changing time | ||
Given a downtime ending on winter changing time | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime ending on winter changing time | ||
Given a downtime ending on winter changing time | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime starting and ending on winter changing time | ||
Given a downtime starting and ending on winter changing time | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime starting and ending on winter changing time | ||
Given a downtime starting and ending on winter changing time | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime during all day on winter changing date | ||
Given a downtime during all day on winter changing date | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime during all day on winter changing date | ||
Given a downtime during all day on winter changing date | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: recurrent downtime of next day of winter changing date | ||
Given a downtime during all day on winter changing date is scheduled | ||
And a downtime of next day of winter changing date | ||
When recurrent downtime is applied | ||
Then the downtime is properly scheduled | ||
|
||
@critical | ||
Scenario: realtime downtime of next day of winter changing date | ||
Given a downtime during all day on winter changing date is scheduled | ||
And a downtime of next day of winter changing date | ||
When realtime downtime is applied | ||
Then the downtime is properly scheduled |
Oops, something went wrong.