Age | Commit message (Collapse) | Author |
|
Our utility class for parsing time-spans uses 00-23, rather than 00-24.
Update the use of the time-period to avoid the bogus "24 hour".
|
|
This means testing values outside the range of 0-23 (inclusive).
We did this already for the start & end times.
This updates #4451.
|
|
This class is used to determine whether an "hour" is within
a given hour-span. e.g. To cope with:
foo must run ping except between 04-06 otherwise 'alert'.
This updates issue #4551.
|
|
|
|
|
|
are followed.
Added test-cases to match.
|
|
|
|
present.
|
|
For example:
example.vm must run ping between 09-17 otherwise 'daytime ping failed'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
record-type.
Added test-case too.
|
|
|
|
incorrectly.
Fixed this now, based on the URL and added a test case.
|
|
|
|
|
|
|
|
match what we did with the alerts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*each* of the with a simple constructed test.
|
|
Allow test-inversion via "must not run".
|
|
|
|
it is named wrongly
|
|
Bytemark range into its own class & added _simple_ test-cases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
permitted.
|
|
|