No commit activity in last 3 years
No release in over 3 years
Cucumber steps for verifing metrics from NewRelic's API
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

 Project Readme

cucumber-newrelic¶ ↑

Cucumber steps for verifying New Relic Application Metrics.

Usage¶ ↑

Install the gem:

gem install cucumber-newrelic

In your features/support/env.rb:

require 'cucumber/newrelic'

You can now write crazy features like this:

Feature: Response Time
  As a impatient user
  Our app should be super fast

  Background:
    Given my NewRelic license key is 'sekret'

  Scenario: Average Response time
    Given that my application is being monitored by New Relic
    Then my application's 'response time' should be less than 500 milliseconds

  Scenario: Apdex
    Given that my application is being monitored by New Relic
    Then my application's 'apdex' should be 1

Available Metrics¶ ↑

["Apdex", "Application Busy", "CPU", "Memory", "Errors", "Error Rate", "Response Time", "Throughput", "DB"]

Available Operators¶ ↑

  • be greater than

  • be less than

  • equal OR be

  • not equal OR not be

Running Cucumber Features¶ ↑

Drop your license key into config/newrelic.yml, then run ‘em like so:

cucumber features

Note on Patches/Pull Requests¶ ↑

  • Fork the project.

  • Make your feature addition or bug fix.

  • Add cucumber features for it. This is important so I don’t break it in a future version unintentionally.

  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)

  • Send me a pull request. Bonus points for topic branches.

Copyright © 2010 Jesse Newland. See LICENSE for details.