harvested 0.3.3 → 0.4.0

data/features/tasks.feature

@@ -1,25 +0,0 @@
-@clean
-Feature: Managing Tasks
-
-  Scenario: Adding, Updating, and Removing a Task
-    Given I am using the credentials from "./support/harvest_credentials.yml"
-    When I create a task with the following:
-    | name        | Test Task |
-    | billable    | true      |
-    | deactivated | false     |
-    | hourly_rate | 120       |
-    Then there should be a task "Test Task"
-    When I update the task "Test Task" with the following:
-    | name        | Updated Task |
-    | hourly_rate | 100.0        |
-    | deactivated | true         |
-    | billable    | false        |
-    | default     | true         |
-    Then the task "Updated Task" should have the following attributes:
-    | hourly_rate | 100.0 |
-    | deactivated | true  |
-    | active?     | false |
-    | billable    | false |
-    | default?    | true  |
-    When I delete the task "Updated Task"
-    Then there should not be a task "Updated Task"

data/features/time_tracking.feature

@@ -1,29 +0,0 @@
-@clean
-Feature: Time Tracking
-
-  Scenario: Adding, Updating, and Deleting Time Entries
-    Given I am using the credentials from "./support/harvest_credentials.yml"
-    And I create a client with the following:
-    | name    | Time Client                  |
-    | details | Client to track time against |
-    And I create a project for the client "Time Client" with the following:
-    | name   | Time Project |
-    | active | true         |
-    And I create a task with the following:
-    | name        | Time Task |
-    | billable    | true      |
-    | hourly_rate | 120       |
-    And I assign the task "Time Task" to the project "Time Project"
-    When I create a time entry for the project "Time Project" and the task "Time Task" with the following:
-    | notes    | Test api support |
-    | hours    | 3.0              |
-    | spent_at | 12/28/2009       |
-    Then there should be a time entry "Test api support" on "12/28/2009"
-    When I update the time entry "Test api support" on "12/28/2009" with the following:
-    | hours | 4.0 |
-    Then the time entry "Test api support" on "12/28/2009" should have the following attributes:
-    | hours | 4.0 |
-    When I delete the time entry "Test api support" on "12/28/2009"
-    Then there should not be a time entry "Test api support" on "12/28/2009"
-    
-  Scenario: Toggling Timers

data/features/user_assignments.feature

@@ -1,33 +0,0 @@
-@clean
-Feature: User Assignments
-  
-  Scenario: Adding and Updating a User on 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 create a user with the following:
-    | first_name            | Edgar          |
-    | last_name             | Ruth           |
-    | email                 | edgar@ruth.com |
-    | password              | mypassword     |
-    | password_confirmation | mypassword     |
-    Then there should be a user "edgar@ruth.com"
-    When I assign the user "edgar@ruth.com" to the project "Test Project"
-    Then the user "edgar@ruth.com" should be assigned to the project "Test Project"
-    When I update the user "edgar@ruth.com" on the project "Test Project" with the following:
-    | hourly_rate     | 50.0 |
-    | project_manager | true |
-    Then the user "edgar@ruth.com" on the project "Test Project" should have the following attributes:
-    | active?         | true |
-    | hourly_rate     | 50.0 |
-    | project_manager | true |
-    When I remove the user "edgar@ruth.com" from the project "Test Project"
-    Then the user "edgar@ruth.com" should not be assigned to the project "Test Project"
-      
-  Scenario: Removing a user from a project that has recorded hours

data/features/users.feature

@@ -1,55 +0,0 @@
-@clean
-Feature: Managing People
-
-  Scenario: Adding and Removing a User
-    Given I am using the credentials from "./support/harvest_credentials.yml"
-    When I create a user with the following:
-    | first_name            | Edgar          |
-    | last_name             | Ruth           |
-    | email                 | edgar@ruth.com |
-    | password              | mypassword     |
-    | password_confirmation | mypassword     |
-    | timezone              | cst            |
-    | admin                 | false          |
-    | telephone             | 444-4444       |
-    Then there should be a user "edgar@ruth.com"
-    When I update the user "edgar@ruth.com" with the following:
-    | first_name | Jonah |
-    | timezone   | pst   |
-    Then the user "edgar@ruth.com" should have the following attributes:
-    | first_name | Jonah                      |
-    | timezone   | Pacific Time (US & Canada) |
-    When I delete the user "edgar@ruth.com"
-    Then there should not be a user "edgar@ruth.com"
-    
-  Scenario: Activating and Deactivating a User
-    Given I am using the credentials from "./support/harvest_credentials.yml"
-    Then I create a user with the following:
-    | first_name            | Simon           |
-    | last_name             | Steel           |
-    | email                 | simon@steel.com |
-    | password              | mypassword      |
-    | password_confirmation | mypassword      |
-    | timezone              | cst             |
-    | admin                 | false           |
-    | telephone             | 444-4444        |
-    Then the user "simon@steel.com" should be activated
-    When I deactivate the user "simon@steel.com"
-    Then the user "simon@steel.com" should be deactivated
-    When I activate the user "simon@steel.com"
-    Then the user "simon@steel.com" should be activated
-    Then I delete the user "simon@steel.com"
-  
-  Scenario: Resetting a User's password
-    Given I am using the credentials from "./support/harvest_credentials.yml"
-    Then I create a user with the following:
-    | first_name            | Edgar          |
-    | last_name             | Ruth           |
-    | email                 | edgar@ruth.com |
-    | password              | mypassword     |
-    | password_confirmation | mypassword     |
-    | timezone              | cst            |
-    | admin                 | false          |
-    | telephone             | 444-4444       |
-    Then there should be a user "edgar@ruth.com"
-    Then I reset the password of "edgar@ruth.com"

data/lib/harvest/base_model.rb

@@ -1,73 +0,0 @@
-module Harvest
-  # The parent class of all Harvest models. Contains useful inheritable methods
-  class BaseModel
-    
-    # Initializes the model. You can pass the attributes as a hash in a ActiveRecord-like style
-    #
-    # == Examples
-    #   client = Harvest::Client.new(:name => 'John Doe')
-    #   client.name # returns 'John Doe'
-    def initialize(attributes = {})
-      self.attributes = attributes
-    end
-    
-    # Given a hash, sets the corresponding attributes
-    #
-    # == Examples
-    #   client = Harvest::Client.new(:name => 'John Doe')
-    #   client.name # returns 'John Doe'
-    #   client.attributes = {:name => 'Terry Vaughn'}
-    #   client.name # returns 'Terry Vaughn'
-    #
-    # @return [void]
-    def attributes=(attributes)
-      attributes.each {|k,v| send("#{k}=", v)}
-    end
-    
-    # Checks the equality of another model based on the id
-    #
-    # == Examples
-    #  client1 = Harvest::Client.new(:id => 1)
-    #  client2 = Harvest::Client.new(:id => 1)
-    #  client3 = Harvest::Client.new(:id => 2)
-    #  
-    #  client1 == client2 # returns true
-    #  client1 == client3 # returns false
-    #
-    # @return [Boolean]
-    def ==(other)
-      id == other.id
-    end
-    
-    # Returns the id of the model
-    #
-    # == Examples
-    #  client = Harvest::Client.new(:id => 1)
-    #  client.to_i # returns 1
-    #
-    # @return [Fixnum]
-    def to_i
-      id
-    end
-    
-    # Builds the XML of the model. Primarily used to interact with the Harvest API.
-    # 
-    # @return [String]
-    def to_xml
-      builder = Builder::XmlMarkup.new
-      builder.tag!(self.class.tag_name) do |c|
-        self.class.elements.each do |f|
-          c.tag!(f.tag, send(f.name)) if send(f.name)
-        end
-      end
-    end
-  
-    class << self
-      # This sets the API path so the API collections can use them in an agnostic way
-      # @return [void]
-      def api_path(path = nil)
-        @path ||= path
-      end
-    end
-  end
-end

data/spec/spec.default.opts

@@ -1 +0,0 @@
---color