quilted-harvested 0.3.1

data/.document

@@ -0,0 +1,3 @@
+README.md
+lib/**/*.rb
+MIT-LICENSE

data/.gitignore

@@ -0,0 +1,25 @@
+## MAC OS
+.DS_Store
+
+## TEXTMATE
+*.tmproj
+tmtags
+
+## EMACS
+*~
+\#*
+.\#*
+
+## VIM
+*.swp
+
+## PROJECT::GENERAL
+coverage
+rdoc
+pkg
+spec.opts
+doc
+.yardoc
+
+## PROJECT::SPECIFIC
+features/support/harvest_credentials.yml

data/HISTORY

@@ -0,0 +1,19 @@
+0.3.1 - October 14, 2010
+  * Updated docs removing :ssl => false since Harvest released SSL to everyone
+  * Added department to the User model (Steve McKinney)
+0.3.0 - April 11, 2010
+  * Added users
+  * Added clients
+  * Added contacts
+  * Added expense categories
+  * Added expenses
+  * Added projects
+  * Added tasks
+  * Added task assignments
+  * Added user assignments
+  * Added time tracking
+  * Added reporting
+  * Added account information
+  * Added common errors
+  * Added Harvest#hardy_client
+  

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2009 Zach Moazeni
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,68 @@
+# Harvested: A Ruby Harvest API
+
+This is a Ruby wrapper for the [Harvest API](http://www.getharvest.com/).
+
+## Installation
+
+    gem install harvested
+
+## Examples
+
+    harvest = Harvest.client('yoursubdomain', 'yourusername', 'yourpassword')
+    harvest.projects() # list out projects
+    
+    client = Harvest::Client.new(:name => "Billable Company LTD.")
+    client = harvest.clients.create(client)
+    harvest.clients.find(client.id) # returns a Harvest::Client
+
+You can find more examples in `/examples` and in the documentation for Harvest::Base
+
+## Hardy Client
+
+The guys at Harvest built a great API, but there are always dangers in writing code that depends on an API. For example, HTTP Timeouts, Occasional Bad Gateways, and Rate Limiting issues need to be accounted for.
+
+Using `Harvested#client` your code needs to handle all these situations. However you can also use `Harvested#hardy_client` which will retry errors and wait for Rate Limit resets.
+
+    harvest = Harvest.hardy_client('yoursubdomain', 'yourusername', 'yourpassword')
+    harvest.projects() # This will wait for the Rate Limit reset if you have gone over your limit
+
+## Links
+
+* [Harvested Documentation](http://rdoc.info/projects/zmoazeni/harvested)
+* [Harvest API Documentation](http://www.getharvest.com/api)
+* [Source Code for Harvested](http://github.com/zmoazeni/harvested)
+* [Pivotal Tracker for Harvested](http://www.pivotaltracker.com/projects/63260)
+* [Mailing List for Harvested](http://groups.google.com/group/harvested)
+
+## How to Contribute
+
+If you find what looks like a bug:
+
+1. Check the GitHub issue tracker to see if anyone else has had the same issue.
+http://github.com/zmoazeni/harvested/issues/
+2. If you don’t see anything, create an issue with information on how to reproduce it.
+
+If you want to contribute an enhancement or a fix:
+ 
+1. Fork the project on github http://github.com/zmoazeni/harvested
+2. Make your changes with tests
+3. Commit the changes without messing with the Rakefile, VERSION, or history
+4. Send me a pull request
+
+Note on running tests: most cucumber features run against a live Harvest account. To run the suite, sign up for a free trial account and fill out `/features/support/harvest_credentials.yml` *(a sample harvest_credentials.example.yml has been included)*. The tests use the hardy_client so they will wait for a rate limit reset when they detect the limit has been hit.
+
+## TODO
+
+* Write Documentation
+* Implement Invoices
+* Allow Timer Toggling
+
+Other Roadmap items can be found on [Pivotal Tracker](http://www.pivotaltracker.com/projects/63260)
+
+## Notes on Harvest Estimates
+
+Estimates aren't currently supported due to lack of an API. If this opens up, harvested will include them.
+
+## Copyright
+
+Copyright (c) 2010 Zach Moazeni. See LICENSE for details.

data/Rakefile

@@ -0,0 +1,25 @@
+require 'rubygems'
+require 'rake'
+
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |gem|
+    gem.name = "quilted-harvested"
+    gem.summary = %Q{A Ruby Wrapper for the Harvest API http://www.getharvest.com/}
+    gem.description = %Q{Harvested wraps the Harvest API concisely without the use of Rails dependencies. More information about the Harvest API can be found on their website (http://www.getharvest.com/api). For support hit up the Mailing List (http://groups.google.com/group/harvested)}
+    gem.email = "michelle@quilted.coop"
+    gem.homepage = "http://github.com/quilted/harvested"
+    gem.authors = ["Zach Moazeni, Michelle Moon Lee (updated)"]
+    gem.add_development_dependency "rspec", ">= 1.2.9"
+    gem.add_development_dependency "cucumber", ">= 0"
+    gem.add_development_dependency "ruby-debug", ">= 0"
+    gem.add_development_dependency "fakeweb", ">= 0"
+    gem.add_dependency "httparty", ">= 0"
+    gem.add_dependency "happymapper", ">= 0"
+    gem.add_dependency "builder", ">= 0"
+  end
+  Jeweler::GemcutterTasks.new
+rescue LoadError => e
+  p e
+  puts "Jeweler (or a dependency) not available. Install it with: gem install jeweler"
+end

data/VERSION

@@ -0,0 +1 @@
+0.3.1

data/examples/basics.rb

@@ -0,0 +1,35 @@
+require "harvested"
+
+subdomain = 'yoursubdomain'
+username = 'yourusername'
+password = 'yourpassword'
+
+harvest = Harvest.hardy_client(subdomain, username, password)
+
+# Print out all users, clients, and projects on the account
+puts "Users:"
+harvest.users.all.each {|u| p u }
+
+puts "Clients:"
+harvest.clients.all.each {|c| p c }
+
+puts "Projects:"
+harvest.projects.all.each {|project| p project }
+
+# Create a Client add a Project to that Client, Add a Task to the Project, track some Time against the Project/Task, and then Run a report against all time I've submitted
+
+client = Harvest::Client.new(:name => 'SuprCorp')
+client = harvest.clients.create(client)
+
+project = Harvest::Project.new(:name => 'SuprGlu', :client_id => client.id, :notes => 'Some notes about this project')
+project = harvest.projects.create(project)
+
+harvest.projects.create_task(project, 'Bottling Glue')
+task_assignment = harvest.task_assignments.all(project).first
+
+time_entry = Harvest::TimeEntry.new(:notes => 'Bottled glue today', :hours => 8, :spent_at => "04/11/2010", :project_id => project.id, :task_id => task_assignment.task_id)
+time_entry = harvest.time.create(time_entry)
+
+entries = harvest.reports.time_by_project(project, Time.parse("04/11/2010"), Time.parse("04/12/2010"))
+puts "Entries:"
+entries.each {|e| p e}

data/examples/clear_account.rb

@@ -0,0 +1,28 @@
+# This is commented out because it can be very dangerous if run against a production account
+
+# require "harvested"
+# 
+# subdomain = 'yoursubdomain'
+# username = 'yourusername'
+# password = 'yourpassword'
+# 
+# api = Harvest.hardy_client(subdomain, username, password)
+# 
+# raise "Are you sure you want to do this? (comment out this exception if so)"
+# 
+# api.users.all.each do |u|
+#   api.users.delete(u) if u.email != username
+# end
+# my_user = api.users.all.first
+# 
+# api.reports.time_by_user(my_user, Time.parse('01/01/2000'), Time.now).each do |time|
+#   api.time.delete(time)
+# end
+# 
+# api.reports.expenses_by_user(my_user, Time.parse('01/01/2000'), Time.now).each do |time|
+#   api.expenses.delete(time)
+# end
+# 
+# %w(expenses expense_categories projects contacts clients tasks).each do |collection|
+#   api.send(collection).all.each {|m| api.send(collection).delete(m) }
+# end

data/examples/task_assignments.rb

@@ -0,0 +1,27 @@
+require "harvested"
+
+subdomain = 'yoursubdomain'
+username = 'yourusername'
+password = 'yourpassword'
+
+harvest = Harvest.hardy_client(subdomain, username, password)
+
+# Create a Client add a Project to that Client
+
+client = Harvest::Client.new(:name => 'SuprCorp')
+client = harvest.clients.create(client)
+
+project = Harvest::Project.new(:name => 'SuprGlu', :client_id => client.id, :notes => 'Some notes about this project')
+project = harvest.projects.create(project)
+
+# You can create an assign a task in one call
+harvest.projects.create_task(project, 'Bottling Glue')
+puts "Assigned the task 'Bottling Glue' to the project 'SuprGlu'"
+
+# You can explicitly create the task and then assign it
+task = Harvest::Task.new(:name => 'Packaging Glue', :hourly_rate => 30, :billable => true)
+task = harvest.tasks.create(task)
+
+task_assignment = Harvest::TaskAssignment.new(:task_id => task.id, :project_id => project.id)
+task_assignment = harvest.task_assignments.create(task_assignment)
+puts "Assigned the task 'Packaging Glue' to the project 'SuprGlu'"

data/examples/user_assignments.rb

@@ -0,0 +1,24 @@
+require "harvested"
+
+subdomain = 'yoursubdomain'
+username = 'userusername'
+password = 'yourpassword'
+
+harvest = Harvest.hardy_client(subdomain, username, password)
+
+# Create a Client, Project, and a User then assign that User to that Project
+
+client = Harvest::Client.new(:name => 'SuprCorp')
+client = harvest.clients.create(client)
+
+project = Harvest::Project.new(:name => 'SuprGlu', :client_id => client.id, :notes => 'Some notes about this project')
+project = harvest.projects.create(project)
+
+harvest.projects.create_task(project, 'Bottling Glue')
+
+user = Harvest::User.new(:first_name => 'Jane', :last_name => 'Doe', :email => 'jane@doe.com', :timezone => :est, :password => 'secure', :password_confirmation => 'secure')
+user = harvest.users.create(user)
+
+user_assignment = Harvest::UserAssignment.new(:user_id => user.id, :project_id => project.id)
+harvest.user_assignments.create(user_assignment)
+puts 'Assigned Jane Doe to the project "SuprGlu"'

data/features/account.feature

@@ -0,0 +1,7 @@
+@clean
+Feature: Account API
+
+  Scenario: Requesting Rate Limit
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    When I request the current rate limit I should get the following:
+    | max_calls | 40 |

data/features/client_contacts.feature

@@ -0,0 +1,23 @@
+@clean
+Feature: Managing Client Contacts
+
+  Scenario: Adding, Updating, and Removing a Contact
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    And I create a client with the following:
+    | name    | Client Contacts                         |
+    | details | Building API Widgets across the country |
+    When I create a contact for the client "Client Contacts" with the following:
+    | email        | jane@doe.com |
+    | first_name   | Jane         |
+    | last_name    | Doe          |
+    | phone_office | 555.123.4567 |
+    | phone_mobile | 555.333.1111 |
+    | fax          | 555.222.1111 |
+    Then there should be a contact "jane@doe.com"
+    And there should be a contact "jane@doe.com" for the client "Client Contacts"
+    When I update the contact "jane@doe.com" with the following:
+    | last_name | Smith |
+    Then the contact "jane@doe.com" should have the following attributes:
+    | last_name | Smith |
+    When I delete the contact "jane@doe.com"
+    Then there should not be a contact "jane@doe.com"

data/features/clients.feature

@@ -0,0 +1,29 @@
+@clean
+Feature: Managing Clients
+
+  Scenario: Adding, Updating, and Removing a Client
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    When I create a client with the following:
+    | name    | Client                                  |
+    | details | Building API Widgets across the country |
+    Then there should be a client "Client"
+    When I update the client "Client" with the following:
+    | name    | Updated Client                      |
+    | details | Building API Widgets in the Midwest |
+    Then the client "Updated Client" should have the following attributes:
+    | details | Building API Widgets in the Midwest |
+    When I delete the client "Updated Client"
+    Then there should not be a client "Updated Client"
+
+  Scenario: Activating and Deactivating a Client
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    When I create a client with the following:
+    | name    | Client                                  |
+    | details | Building API Widgets across the country |
+    Then the client "Client" should be activated
+    When I deactivate the client "Client"
+    Then the client "Client" should be deactivated
+    When I activate the client "Client"
+    Then the client "Client" should be activated
+    Then I delete the client "Client"
+    

data/features/errors.feature

@@ -0,0 +1,25 @@
+@disconnected
+Feature: Handling Harvest Errors
+
+  Scenario: Raising Bad Responses
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    
+    Given the next request will receive a bad request response
+    When I make a request with the standard client
+    Then a 400 error should be raised
+    
+    Given the next request will receive a not found response
+    When I make a request with the standard client
+    Then a 404 error should be raised
+    
+    Given the next request will receive a bad gateway response
+    When I make a request with the standard client
+    Then a 502 error should be raised
+    
+    Given the next request will receive a server error response
+    When I make a request with the standard client
+    Then a 500 error should be raised
+    
+    Given the next request will receive a rate limit response
+    When I make a request with the standard client
+    Then a 503 error should be raised

data/features/expense_categories.feature

@@ -0,0 +1,21 @@
+@clean
+Feature: Expense Categories
+
+  Scenario: Adding, Updating, and Removing an Expense Category
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    When I create an expense category with the following:
+    | name       | Mileage |
+    | unit_name  | Miles   |
+    | unit_price | 0.485   |
+    Then there should be an expense category "Mileage"
+    When I update the expense category "Mileage" with the following:
+    | unit_name   | Kilometers |
+    | deactivated | true       |
+    | unit_price  | 1.2        |
+    Then the expense category "Mileage" should have the following attributes:
+    | unit_name   | Kilometers |
+    | unit_price  | 1.2        |
+    | deactivated | true       |
+    | active?     | false      |
+    When I delete the expense category "Mileage"
+    Then there should not be an expense category "Mileage"

data/features/expenses.feature

@@ -0,0 +1,55 @@
+@clean
+Feature: Expenses
+
+  Scenario: Adding, Updating, and Removing an Expenses
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    When I create an expense category with the following:
+    | name       | Mileage |
+    | unit_name  | Miles   |
+    | unit_price | 0.485   |
+    Then there should be an expense category "Mileage"
+    When I create a client with the following:
+    | name | Expense Client |
+    When I create a project for the client "Expense Client" with the following:
+    | name | Test Project |
+    When I create an expense for the project "Test Project" with the category "Mileage" with the following:
+    | notes      | Drive to Chicago |
+    | total_cost | 75.00            |
+    | spent_at   | 12/28/2009       |
+    Then there should be an expense "Drive to Chicago" on "12/28/2009"
+    And the expense "Drive to Chicago" on "12/28/2009" should have the following attributes:
+    | total_cost | 75.0 |
+    | units      | 1    |
+    When I update the expense "Drive to Chicago" on "12/28/2009" with the following:
+    | total_cost | 50 |
+    Then the expense "Drive to Chicago" on "12/28/2009" should have the following attributes:
+    | total_cost | 50.0 |
+    | units      | 1    |
+    When I update the expense "Drive to Chicago" on "12/28/2009" with the following:
+    | total_cost |   |
+    | units      | 3 |
+    Then the expense "Drive to Chicago" on "12/28/2009" should have the following attributes:
+    | total_cost | 1.46 |
+    | units      | 3    |
+    When I delete the expense "Drive to Chicago" on "12/28/2009"
+    Then there should not be an expense "Drive to Chicago" on "12/28/2009"
+  
+  @wip
+  Scenario: Attaching a receipt to an Expense
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    When I create an expense category with the following:
+    | name       | Mileage |
+    | unit_name  | Miles   |
+    | unit_price | 0.485   |
+    Then there should be an expense category "Mileage"
+    When I create a client with the following:
+    | name | Expense Client |
+    When I create a project for the client "Expense Client" with the following:
+    | name | Test Project |
+    When I create an expense for the project "Test Project" with the category "Mileage" with the following:
+    | notes      | Drive to Chicago |
+    | total_cost | 75.00            |
+    | spent_at   | 12/28/2009       |
+    Then there should be an expense "Drive to Chicago" on "12/28/2009"
+    When I attach the receipt "./support/fixtures/receipt.png" to the expense "Drive to Chicago" on "12/28/2009"
+    Then there should be a receipt "./support/fixtures/receipt.png" attached to the expense "Drive to Chicago" on "12/28/2009"

data/features/hardy_client.feature

@@ -0,0 +1,40 @@
+@disconnected
+Feature: Hardy Client
+
+  Background:
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    And the rate limit status indicates I'm under my limit
+
+  Scenario: Hardy Client waiting for Rate Limit resets
+    Given the next request will receive a rate limit response with a refresh in 5 seconds
+    When I make a request with the hardy client
+    Then the hardy client should wait 5 seconds for the rate limit to reset
+    And I should be able to make a request again
+    
+  Scenario: Hardy Client waiting for Rate Limit resets
+    Given the next request will receive a rate limit response without a refresh set
+    When I make a request with the hardy client
+    Then the hardy client should wait 16 seconds for the rate limit to reset
+    And I should be able to make a request again
+    
+  Scenario: Hardy Client retrying Bad Gateway responses
+    Given the next 2 requests will receive a bad gateway response
+    When I make a request with the hardy client
+    Then no errors should be raised
+  
+  Scenario: Hardy Client retrying HTTP Errors
+    Given the next 2 requests will receive an HTTP Error
+    When I make a request with the hardy client
+    Then no errors should be raised
+  
+  Scenario: Hardy Client stop retrying Bad Gateway responses
+    Given the next 6 requests will receive a bad gateway response
+    When I make a request with the hardy client
+    Then a 502 error should be raised
+    
+  Scenario: Check rate limit before retrying bad gateway requests
+    Given the next request will receive a bad gateway response
+    And the rate limit status indicates I'm over my limit
+    When I make a request with the hardy client
+    Then the hardy client should wait 16 seconds for the rate limit to reset
+    And I should be able to make a request again

data/features/projects.feature

@@ -0,0 +1,39 @@
+@clean
+Feature: Managing Projects
+
+  Scenario: Adding, Updating, and Removing a Project
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    When I create a client with the following:
+    | name    | Client Projects                         |
+    | details | Building API Widgets across the country |
+    When I create a project for the client "Client Projects" with the following:
+    | name   | Test Project            |
+    | active | true                    |
+    | notes  | project to test the api |
+    Then there should be a project "Test Project"
+    When I update the project "Test Project" with the following:
+    | name        | Updated Project |
+    | code        | new-code        |
+    | bill_by     | Project         |
+    | hourly_rate | 150             |
+    Then the project "Updated Project" should have the following attributes:
+    | code        | new-code |
+    | bill_by     | Project  |
+    | hourly_rate | 150.0    |
+    When I delete the project "Updated Project"
+    Then there should not be a project "Updated Project"
+    
+  Scenario: Activating and Deactivating a Project
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    And I create a client with the following:
+    | name    | Client Projects                         |
+    | details | Building API Widgets across the country |
+    And I create a project for the client "Client Projects" with the following:
+    | name   | Test Project            |
+    | active | true                    |
+    | notes  | project to test the api |
+    Then the project "Test Project" should be activated
+    When I deactivate the project "Test Project"
+    Then the project "Test Project" should be deactivated
+    When I activate the project "Test Project"
+    Then the project "Test Project" should be activated

data/features/reporting.feature

@@ -0,0 +1,72 @@
+@clean
+Feature: Harvest Reporting
+
+  Background:
+    Given I am using the credentials from "./support/harvest_credentials.yml"
+    And I create a client with the following:
+    | name    | Report Client         |
+    | details | Client to run reports |
+    And I create a project for the client "Report Client" with the following:
+    | name | Report Project1 |
+    And I create a project for the client "Report Client" with the following:
+    | name | Report Project2 |
+
+  Scenario: Time Entry Reporting
+    Given I create a task with the following:
+    | name        | Report Task |
+    | billable    | true        |
+    | hourly_rate | 120         |
+    And I assign the task "Report Task" to the project "Report Project1"
+    And I assign the task "Report Task" to the project "Report Project2"
+    And I create a time entry for the project "Report Project1" and the task "Report Task" with the following:
+    | notes    | project1 time |
+    | hours    | 2.0           |
+    | spent_at | 12/28/2009    |
+    And I create a time entry for the project "Report Project2" and the task "Report Task" with the following:
+    | notes    | project2 time |
+    | hours    | 2.0           |
+    | spent_at | 12/28/2009    |
+    When I run a project report for "Report Project1" for "12/20/2009" and "12/30/2009" the following entries should be returned:
+    | project1 time |
+    When I run a project report for "Report Project1" for "12/20/2009" and "12/30/2009" the following entries should not be returned:
+    | project2 time |
+    When I run a a project report for "Report Project1" for "12/20/2009" and "12/30/2009" filtered by my user the following entries should be returned:
+    | project1 time |
+    When I run a a project report for "Report Project1" for "12/20/2009" and "12/30/2009" filtered by my user the following entries should not be returned:
+    | project2 time |
+    When I run a people report for my user for "12/20/2009" and "12/30/2009" the following entries should be returned:
+    | project1 time |
+    | project2 time |
+  
+  @wip
+  Scenario: People Reports filtered by Project
+    Given I create a task with the following:
+    | name        | Report Task |
+    | billable    | true        |
+    | hourly_rate | 120         |
+    And I assign the task "Report Task" to the project "Report Project1"
+    And I assign the task "Report Task" to the project "Report Project2"
+    And I create a time entry for the project "Report Project1" and the task "Report Task" with the following:
+    | notes    | project1 time |
+    | hours    | 2.0           |
+    | spent_at | 12/28/2009    |
+    And I create a time entry for the project "Report Project2" and the task "Report Task" with the following:
+    | notes    | project2 time |
+    | hours    | 2.0           |
+    | spent_at | 12/28/2009    |
+    When I run a people report for my user for "12/20/2009" and "12/30/2009" filtered by the project "Report Project1" the following entries should be returned:
+    | project1 time |
+    When I run a people report for my user for "12/20/2009" and "12/30/2009" filtered by the project "Report Project1" the following entries should not be returned:
+    | project2 time |
+    
+  Scenario: Expenses by People
+    Given I create an expense category with the following:
+    | name       | Conference |
+    | unit_name  | Ticket     |
+    | unit_price | 300        |
+    And I create an expense for the project "Report Project1" with the category "Conference" with the following:
+    | notes      | RubyConf   |
+    | total_cost | 300        |
+    | spent_at   | 12/28/2009 |
+    When I run an expense report for my user for "12/20/2009" and "12/30/2009" the following entries should be returned:
+    | RubyConf |

data/features/step_definitions/account_steps.rb

@@ -0,0 +1,7 @@
+When 'I request the current rate limit I should get the following:' do |table|
+  rate_limit_status = harvest_api.account.rate_limit_status
+  table.rows_hash.each do |key, value|
+    rate_limit_status.send(key).to_s.should == value
+  end
+end
+