| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Rather than showing "2, 4, etc" we use the expansion routine
to show TEST_FAILED, TEST_PASSED, etc. This reads more neatly.
|
|
Specifically that we can get the value back as a string, and
work with the ordinal too.
|
|
We no longer test for open-relays so we don't need to run the test.
|
|
Rather than having "inverted" we now name the test-method
"inverted?" which is more ideomatic.
|
|
This update consists of two changes:
* No longer return "true" or "false" instead return "TEST_FAILED", or "TEST_SUCCEEDED".
* Removed the testing of test-inversion from the class, now it lives in the base-class where it should have done all along.
|
|
|
|
This stops warnings when running with "ruby -w".
|
|
Now tests will no longe return "true" or "false", instead they
will return "TEST_FAILED" or "TEST_PASSED". There is a third
return-value of "TEST_SKIPPED" which essentially ignores a test.
|
|
This commit introduces a major change in custodian. In the past
any test had either two results:
* return false - The test failed.
* return true - The test passed.
We're now using an enum, more or less, such that a test may return a
"skipped" result which will neither raise nor clear any alert(s).
This is useful in its own right but is being introduced specifically
to allow SSL-certificate tests to avoid raising and clearing outside
working days/hours.
This closes #10328.
This fixes #10328.
|
|
We do that with the standard "_"-prefix.
|
|
We've now prefixed our transient/unused variables with "_" to stop
any future errors about variables not being used.
|
|
We'd failed to set the default value of our loaded-marker to false,
although in-practice this wasn't a problem.
|
|
|
|
|
|
|
|
Due to some sloppy edits this module was not correct.
|
|
|
|
|
|
|
|
There was a bug in that we used the same local-variable "result"
for two purposes, trashing the intended use-case.
|
|
Hard-coding IPs is a bad choice, but the alternative here is to
exec( `dig -t a`) or similar which seems equally bad.
|
|
The Bytemark-specific notifier, using mauve, appends some text to
the bottom of each alert:
http://example.com/ resolves to 1.2.3.4 which is INSIDE|OUTSIDE bytemark
This text was previously limited to the IPv4 address, but now is repeated
for each family which resolves successfully.
This closes #10568.
This fixes #10568.
|
|
|
|
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`.
|
|
This was failing because '$ERROR_INFO' is only available if
you
require 'English'
|
|
|
|
|
|
This removes the nasty self-parsing of the script to generate the
help/manual output. I've also removed global-variables and made
the code almost-100% warning free.
|
|
|
|
These might change in the future, but for the moment the formatting
codes are useful to ensure consistent code.
|
|
|
|
|
|
|
|
|
|
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.
|
|
The last expression of a method is the return value. So:
def foo; false ; end
Is the same as:
def foo; return false; end
|
|
So "getURL" becomes "get_url_contents"
|
|
|
|
This is neater. Flagged by rubocop
|
|
Instead use {} + ().
|
|
|
|
This is neater.
|
