harvested 0.3.3 → 0.4.0

data/features/clients.feature

@@ -1,29 +0,0 @@
-@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

@@ -1,25 +0,0 @@
-@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

@@ -1,21 +0,0 @@
-@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

@@ -1,55 +0,0 @@
-@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

@@ -1,40 +0,0 @@
-@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

@@ -1,39 +0,0 @@
-@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

@@ -1,72 +0,0 @@
-@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

@@ -1,7 +0,0 @@
-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
-

data/features/step_definitions/assignment_steps.rb

@@ -1,100 +0,0 @@
-When 'I create and assign a task "$1" to the project "$2"' do |task_name, project_name|
-  project = Then %Q{there should be a project "#{project_name}"}
-  p = harvest_api.projects.create_task(project, task_name)
-  p.should == project
-end
-
-When 'I assign the task "$1" to the project "$2"' do |task_name, project_name|
-  task = Then %Q{there should be a task "#{task_name}"}
-  project = Then %Q{there should be a project "#{project_name}"}
-  assignment = Harvest::TaskAssignment.new(:project => project, :task => task)
-  harvest_api.task_assignments.create(assignment)
-end
-
-Then 'the task "$1" should be assigned to the project "$2"' do |task_name, project_name|
-  task = Then %Q{there should be a task "#{task_name}"}
-  project = Then %Q{there should be a project "#{project_name}"}
-  assignments = harvest_api.task_assignments.all(project)
-  assignment = assignments.detect {|a| a.project_id == project.to_i && a.task_id == task.to_i }
-  assignment.should_not be_nil
-  assignment
-end
-
-Then 'the task "$1" should not be assigned to the project "$2"' do |task_name, project_name|
-  task = Then %Q{there should be a task "#{task_name}"}
-  project = Then %Q{there should be a project "#{project_name}"}
-  assignments = harvest_api.task_assignments.all(project)
-  assignment = assignments.detect {|a| a.project_id == project.to_i && a.task_id == task.to_i }
-  assignment.should be_nil
-end
-
-When 'I update the task "$1" for the project "$2" with the following:' do |task_name, project_name, table|
-  assignment = Then %Q{the task "#{task_name}" should be assigned to the project "#{project_name}"}
-  assignment.attributes = table.rows_hash
-  harvest_api.task_assignments.update(assignment)
-end
-
-Then 'the task "$1" for the project "$2" should have the following attributes:' do |task_name, project_name, table|
-  assignment = Then %Q{the task "#{task_name}" should be assigned to the project "#{project_name}"}
-  table.rows_hash.each do |key, value|
-    assignment.send(key).to_s.should == value
-  end
-end
-
-When 'I remove the task "$1" from the project "$2"' do |task_name, project_name|
-  assignment = Then %Q{the task "#{task_name}" should be assigned to the project "#{project_name}"}
-  id = harvest_api.task_assignments.delete(assignment)
-  id.should == assignment.id
-end
-
-When 'I try to remove the task "$1" from the project "$2"' do |task_name, project_name|
-  assignment = Then %Q{the task "#{task_name}" should be assigned to the project "#{project_name}"}
-  begin
-    harvest_api.task_assignments.delete(assignment)
-  rescue Harvest::HTTPError => e
-    @error = e
-  end
-end
-
-When 'I assign the user "$1" to the project "$2"' do |email, project_name|
-  user = Then %Q{there should be a user "#{email}"}
-  project = Then %Q{there should be a project "#{project_name}"}
-  assignment = Harvest::UserAssignment.new(:project => project, :user => user)
-  harvest_api.user_assignments.create(assignment)
-end
-
-When 'I remove the user "$1" from the project "$2"' do |email, project_name|
-  assignment = Then %Q{the user "#{email}" should be assigned to the project "#{project_name}"}
-  id = harvest_api.user_assignments.delete(assignment)
-  id.should == assignment.id
-end
-
-Then 'the user "$1" should be assigned to the project "$2"' do |email, project_name|
-  user = Then %Q{there should be a user "#{email}"}
-  project = Then %Q{there should be a project "#{project_name}"}
-  assignments = harvest_api.user_assignments.all(project)
-  assignment = assignments.detect {|a| a.project_id == project.to_i && a.user_id == user.to_i }
-  assignment.should_not be_nil
-  assignment
-end
-
-Then 'the user "$1" should not be assigned to the project "$2"' do |email, project_name|
-  user = Then %Q{there should be a user "#{email}"}
-  project = Then %Q{there should be a project "#{project_name}"}
-  assignments = harvest_api.user_assignments.all(project)
-  assignment = assignments.detect {|a| a.project_id == project.to_i && a.user_id == user.to_i }
-  assignment.should be_nil
-end
-
-When 'I update the user "$1" on the project "$2" with the following:' do |email, project_name, table|
-  assignment = Then %Q{the user "#{email}" should be assigned to the project "#{project_name}"}
-  assignment.attributes = table.rows_hash
-  harvest_api.user_assignments.update(assignment)
-end
-
-Then 'the user "$1" on the project "$2" should have the following attributes:' do |email, project_name, table|
-  assignment = Then %Q{the user "#{email}" should be assigned to the project "#{project_name}"}
-  table.rows_hash.each do |key, value|
-    assignment.send(key).to_s.should == value
-  end
-end

data/features/step_definitions/contact_steps.rb

@@ -1,11 +0,0 @@
-Then 'there should be a contact "$1" for the client "$2"' do |email, client_name|
-  client = Then %Q{there should be a client "#{client_name}"}
-  contact = Then %Q{there should be a contact "#{email}"}
-  contact.client_id.should == client.id
-  
-  contacts = harvest_api.contacts.all(client.id)
-  contact2 = contacts.detect {|c| c.email == email}
-  contact2.should == contact
-  
-  contact
-end

data/features/step_definitions/debug_steps.rb

@@ -1,3 +0,0 @@
-Then 'I debug' do
-  debugger
-end

data/features/step_definitions/error_steps.rb

@@ -1,113 +0,0 @@
-Given /^the next request will receive a (bad request|not found|bad gateway|server error|rate limit) response$/ do |type|
-  statuses = {
-    'bad request' => ['400', 'Bad Request'],
-    'not found' => ['404', 'Not Found'],
-    'bad gateway' => ['502', 'Bad Gateway'],
-    'server error' => ['500', 'Server Error'],
-    'rate limit' => ['503', 'Rake Limited']
-  }
-  
-  if status = statuses[type]
-    FakeWeb.register_uri(:get, /\/clients/, [
-      {:status => status, :times => 1},
-      {:body => File.read(File.dirname(__FILE__) + '/../support/fixtures/empty_clients.xml')}
-    ])
-  else
-    pending
-  end
-end
-
-Given /^the next request will receive a rate limit response with a refresh in (\d+) seconds$/ do |seconds|
-  FakeWeb.register_uri(:get, /\/clients/, [
-    {:status => ['503', 'Rake Limited'], "Retry-After" => seconds},
-    {:body => File.read(File.dirname(__FILE__) + '/../support/fixtures/empty_clients.xml')}
-  ])
-end
-
-Given 'the next request will receive a rate limit response without a refresh set' do
-  FakeWeb.register_uri(:get, /\/clients/, [
-    {:status => ['503', 'Rake Limited']},
-    {:body => File.read(File.dirname(__FILE__) + '/../support/fixtures/empty_clients.xml')}
-  ])
-end
-
-When 'I make a request with the standard client' do
-  set_time_and_return_and_error do
-    standard_api.clients.all
-  end
-end
-
-When 'I make a request with the hardy client' do
-  set_time_and_return_and_error do
-    harvest_api.clients.all
-  end
-end
-
-When /^I make a request with the hardy client with (\d+) max retries$/ do |times|
-  set_time_and_return_and_error do
-    api = Harvest.hardy_client(@subdomain, @username, @password, :ssl => @ssl, :retry => times.to_i)
-    api.clients.all
-  end
-end
-
-Then /a (\d+) error should be raised/ do |code|
-  case code
-  when '400'
-    @error.should be_a(Harvest::BadRequest)
-  when '404'
-    @error.should be_a(Harvest::NotFound)
-  when '502'
-    @error.should be_a(Harvest::Unavailable)
-  when '500'
-    @error.should be_a(Harvest::ServerError)
-  when '503'
-    @error.should be_a(Harvest::RateLimited)
-  else
-    pending
-  end
-end
-
-Then /the hardy client should wait (\d+) seconds for the rate limit to reset/ do |seconds|
-  Time.now.should be_close(@time + seconds.to_i, 2)
-end
-
-Then 'I should be able to make a request again' do
-  harvest_api.clients.all
-  harvest_api.clients.all
-end
-
-Given /^the next (\d+) requests will receive a bad gateway response$/ do |times|
-  FakeWeb.register_uri(:get, /\/clients/, [
-    {:status => ['502', 'Bad Gateway'], :times => times.to_i},
-    {:body => File.read(File.dirname(__FILE__) + '/../support/fixtures/empty_clients.xml')}
-  ])
-end
-
-Given /^the next (\d+) requests will receive a server error response$/ do |times|
-  FakeWeb.register_uri(:get, /\/clients/, [
-    {:status => ['500', 'Server Error'], :times => times.to_i},
-    {:body => File.read(File.dirname(__FILE__) + '/../support/fixtures/empty_clients.xml')}
-  ])
-end
-
-Given /^the next (\d+) requests will receive an HTTP Error$/ do |times|
-  FakeWeb.register_uri(:get, /\/clients/, [
-    {:exception => Net::HTTPError, :times => times.to_i},
-    {:body => File.read(File.dirname(__FILE__) + '/../support/fixtures/empty_clients.xml')}
-  ])
-end
-
-Then 'no errors should be raised' do
-  @error.should be_nil
-  @clients.should == []
-end
-
-Given 'the rate limit status indicates I\'m over my limit' do
-  over_limit_response = File.read(File.dirname(__FILE__) + '/../support/fixtures/over_limit.xml')
-  FakeWeb.register_uri(:get, /\/account\/rate_limit_status/, :body => over_limit_response)
-end
-
-Given 'the rate limit status indicates I\'m under my limit' do
-  over_limit_response = File.read(File.dirname(__FILE__) + '/../support/fixtures/under_limit.xml')
-  FakeWeb.register_uri(:get, /\/account\/rate_limit_status/, :body => over_limit_response)
-end