| Age | Commit message (Collapse) | Author | 
|---|
|  | We've always had an implicit rule in macro-definitions, that they
end with a period.  This meant that the first line is valid:
        FOO is bar.vm.bytemark.co.uk.
However we'd expect this to fail:
        FOO is bar.vm.bytemark.co.uk
A similar issue would arise if a macro-definition involved more than
one host, only the first would be valid.
We've fixed this now, such that the trailing period is optional. | 
|  | In the past we needed to write:
        must run tcp on 3306.
Now we can add the "port" to match the rest of the tests:
        must run tcp on port 3306. | 
|  | This allows you to write the following (identical) tests:
        foo must run FTP.
        foo must run ftp.
        foo must run FtP.
This is mostly a neatness update. | 
|  | This will ensure that it uses the correct port. | 
|  | Specifically that we can get the value back as a string, and
work with the ordinal too. | 
|  | Rather than having "inverted" we now name the test-method
"inverted?" which is more ideomatic. | 
|  | Hard-coding IPs is a bad choice, but the alternative here is to
exec( `dig -t a`) or similar which seems equally bad. | 
|  | We now use the Test::Unit::TestCase.skip() method if the
gem is missing, rather than kill the whole suite. | 
|  | The method-stubbing doesn't work, and so it is obsolete. | 
|  | This is designed to ensure that we meet the style/code guideline
defined in `.rubocop.yml`. | 
|  |  | 
|  |  | 
|  |  | 
|  | These were all identified and suggested by rubocop. | 
|  |  | 
|  | So "foo" is less good than 'foo'. | 
|  | Ruby is not Perl, much as I sometimes wish it were. | 
|  |  | 
|  | This is neater.  Flagged by rubocop | 
|  | Instead use {} + (). | 
|  | This is neater. | 
|  | Instead prefer ".".
Flagged by rubocop | 
|  |  | 
|  | Instead of "$0" use $PROGRAM_NAME, instead of $! use "$LOAD_PATH".  This
is more explicit and less-magic.
Flagged by rubocop | 
|  | This fully explores the parsing and unparsing of the test-objects,
with the exceptions of DNS, FTP, LDAP, and SSLCertificates. | 
|  | Now we have multiple HTTP-implementations we need to update to
make sure they're all caught. | 
|  | The class-factory for instantiating tests now returns an array
rather than a string. | 
|  | Now that the class-factory returns an Array, we've updated the
test-cases to continue to pass. | 
|  |  | 
|  |  | 
|  |  | 
|  | This will be needed when we want to save to the redis-log. | 
|  |  | 
|  |  | 
|  | These days google.com resolves over both IPv4 and IPv6. | 
|  | Added test for run_test. | 
|  |  | 
|  |  | 
|  |  | 
|  | Since we test dns lookups and reverse DNS lookups then we need to
 update the hostnames which have aged into a broken set of tests. | 
|  |  | 
|  |  | 
|  |  | 
|  | Broke down the inside? function into a function for returning the hours
in a period, and for sanitizing hour strings "14" vs. "2pm", etc.
Updated test-cases to match. | 
|  | parser test, is matching against a period that covers the full
24 hours.
Correctly terminate this case, and add a new test-case to ensure
that this is always correct. | 
|  | 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. | 
|  |  | 
|  |  |