Synopsis

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

Description

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)

Special tags

Scenarios tagged with @warn will be reported with WARN level in nagios.

See also

The pherkin / Test-BDD-Cucumber documentation:

pherkin, Test::BDD::Cucumber

A collection of generic step definitions for infrastructure tests:

Test::BDD::Infrastructure