check_pherkin - nagios wrapper for pherkin (Test::BDD::Cucumber)
version 1.002
Short output in case of success:
$ check_pherkin examples/ OK - all 5 scenarios passed $ echo $? 0
Or in case of failure:
$ check_pherkin examples/http.feature line 10: And the http response status code must be 302 failed ok 1 - Starting to execute step: the http response status code must be 302 not ok 2 - the status code must be 302 # Failed test 'the status code must be 302' # at lib/Test/BDD/Infrastructure/HTTP.pm line 125. # got: 500 # expected: 302 1..2 CRITICAL - 1 (critical) / 0 (warn) out of 1 scenarios failed $ echo $? 2
check_pherkin is nagios command wrapper for pherkin.
The program behaves like pherkin but the output is always Nagios and the return status is a nagios return code. (0=OK,1=WARN,2=CRITICAL)
Scenarios tagged with @warn will be reported with WARN level in nagios.
The pherkin / Test-BDD-Cucumber documentation:
pherkin, Test::BDD::Cucumber
A collection of generic step definitions for infrastructure tests:
Test::BDD::Infrastructure
Markus Benning <ich@markusbenning.de>
This software is copyright (c) 2015 by Markus Benning.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
To install Test::BDD::Cucumber::Harness::Nagios, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Test::BDD::Cucumber::Harness::Nagios
CPAN shell
perl -MCPAN -e shell install Test::BDD::Cucumber::Harness::Nagios
For more information on module installation, please visit the detailed CPAN module installation guide.