tempo-cli 0.1.0

data/features/project.feature

@@ -0,0 +1,246 @@
+Feature: Project Command manages a list of projects
+  The project command allows time to be tracked by project
+  New projects can be added and deleted
+  Projects can also be tagged as inactive or inactive
+
+  Scenario: Listing projects before any projects exist
+    Given a clean installation
+    When I run `tempo project`
+    Then the stdout should contain "no projects exist"
+    And the project file should contain "#" at line 1
+
+  Scenario: Listing projects before any projects exist
+    Given a clean installation
+    When I run `tempo project --list`
+    Then the stdout should contain "no projects exist"
+
+  Scenario: Adding the first project creates a file with a current project
+    Given a clean installation
+    When I successfully run `tempo project horticulture`
+    Then the project file should contain ":title: horticulture" at line 5
+    And the project file should contain "current" at line 7
+
+  Scenario: Listing the active project by default
+    Given an existing project file
+    When I successfully run `tempo project`
+    Then the stdout should contain "* horticulture"
+
+  Scenario: Listing all Projects alphabetically with --list
+    Given an existing project file
+    When I successfully run `tempo project --list`
+    Then the stdout should contain "  aquaculture"
+    And the stdout should contain "    nano aquarium"
+    And the stdout should contain "    reading aquaculture digest"
+    And the stdout should contain "* horticulture"
+    And the stdout should contain "    backyard bonsai"
+    And the stdout should contain "    basement mushrooms"
+
+  Scenario: Listing all Projects with --l
+    Given an existing project file
+    When I successfully run `tempo project -l`
+    Then the stdout should contain "  aquaculture"
+    And the stdout should contain "    nano aquarium"
+    And the stdout should contain "    reading aquaculture digest"
+    And the stdout should contain "* horticulture"
+    And the stdout should contain "    backyard bonsai"
+    And the stdout should contain "    basement mushrooms"
+
+  Scenario: Listing all Projects with --verbose
+    Given an existing project file
+    When I successfully run `tempo -v project -l`
+    Then the stdout should contain "  [4]   aquaculture                   tags: [cultivation]"
+    And the stdout should contain "  [5]     nano aquarium               tags: [miniaturization]"
+    And the stdout should contain "  [6]     reading aquaculture digest  tags: none"
+    And the stdout should contain "  [1] * horticulture                  tags: [cultivation]"
+    And the stdout should contain "  [2]     backyard bonsai             tags: [miniaturization, outdoors]"
+    And the stdout should contain "  [3]     basement mushrooms          tags: [fungi, indoors]"
+
+  Scenario: Listing all Projects with Ids displayed
+    Given an existing project file
+    When I successfully run `tempo project -li`
+    Then the stdout should contain "[4]   aquaculture"
+    And the stdout should contain "[5]     nano aquarium"
+    And the stdout should contain "[6]     reading aquaculture digest"
+    And the stdout should contain "[1] * horticulture"
+    And the stdout should contain "[2]     backyard bonsai"
+    And the stdout should contain "[3]     basement mushrooms"
+
+  Scenario: Listing Projects by matching against arguments
+    Given an existing project file
+    When I successfully run `tempo project -l culture`
+    Then the stdout should contain "  aquaculture"
+    And the stdout should contain "    reading aquaculture digest"
+    And the stdout should contain "* horticulture"
+    And the stdout should not contain "    backyard bonsai"
+
+  Scenario: Listing Projects by matching against regex
+    Given an existing project file
+    When I successfully run `tempo project -l ^aquaculture$`
+    Then the stdout should not contain "    reading aquaculture digest"
+    And the stdout should contain "  aquaculture"
+
+  Scenario: Matching Projects with an exact match
+    Given an existing project file
+    And I successfully run `tempo project -le aquaculture`
+    Then the stdout should not contain "    reading aquaculture digest"
+    And the stdout should contain "  aquaculture"
+
+  Scenario: Listing no Project when matching against arguments returns nothing
+    Given an existing project file
+    When I run `tempo project -l "beekeeping"`
+    Then the stderr should contain "no projects match the request: beekeeping"
+
+  Scenario: Adding a project
+    Given an existing project file
+    When I successfully run `tempo project "hang gliding"`
+    Then the stdout should contain "added project:\nhang gliding"
+    And the project file should contain ":title: hang gliding"
+
+  Scenario: Adding a project without quotation marks
+    Given an existing project file
+    When I successfully run `tempo project hang gliding`
+    Then the stdout should contain "added project:\nhang gliding\n"
+    And the project file should contain ":title: hang gliding"
+
+  Scenario: Attempting to add an existing project
+    Given an existing project file
+    When I run `tempo project "basement mushrooms"`
+    Then the stderr should contain "error: project 'basement mushrooms' already exists"
+
+  Scenario: Deleting a project by full match
+    Given an existing project file
+    When I successfully run `tempo project -d "backyard bonsai"`
+    Then the stdout should contain "deleted project:\nbackyard bonsai"
+    And the project file should not contain ":title: backyard bonsai"
+
+  Scenario: Deleting a project by partial match
+    Given an existing project file
+    When I successfully run `tempo project -d "bonsai"`
+    Then the stdout should contain "deleted project:\nbackyard bonsai"
+    And the project file should not contain ":title: backyard bonsai"
+
+  Scenario: Deleting a project without quotation marks
+    Given an existing project file
+    When I successfully run `tempo project -d backyard bonsai`
+    Then the stdout should contain "deleted project:\nbackyard bonsai"
+    And the project file should not contain ":title: backyard bonsai"
+
+  Scenario: Deleting a project with list flag works even without quotes around a partial match
+    Given an existing project file
+    When I successfully run `tempo project -d backyard bonsai -l`
+    Then the stdout should contain "  aquaculture"
+    And the stdout should contain "    nano aquarium"
+    And the stdout should contain "    reading aquaculture digest"
+    And the stdout should contain "* horticulture"
+    And the stdout should not contain "    backyard bonsai"
+    And the stdout should contain "    basement mushrooms"
+
+  Scenario: Deleting a project with combined '-ld' list flag also works
+    Given an existing project file
+    When I successfully run `tempo project -ld backyard bonsai`
+    Then the stdout should contain "  aquaculture"
+    And the stdout should contain "    nano aquarium"
+    And the stdout should contain "    reading aquaculture digest"
+    And the stdout should contain "* horticulture"
+    And the stdout should not contain "    backyard bonsai"
+    And the stdout should contain "    basement mushrooms"
+  Scenario: Deleting a project by Id
+    Given an existing project file
+    When I successfully run `tempo project -id 3`
+    Then the stdout should contain "deleted project:\n  [3] basement mushrooms"
+    And the project file should not contain ":title: basement mushrooms"
+
+  Scenario: Attempting to delete a non-existing project Fails
+    Given an existing project file
+    When I run `tempo project -d "sheep hearding - lanolin extraction"`
+    Then the stderr should contain "error: no projects match the request: sheep hearding - lanolin extraction"
+
+  Scenario: Attempting to Delete the current project Fails
+    Given an existing project file
+    When I run `tempo project -d "horticulture"`
+    Then the stdout should not contain "deleted project"
+    And the stderr should contain "error: cannot delete the active project"
+
+  Scenario: Attempting to Delete with ambiguous match Fails
+    Given an existing project file
+    When I run `tempo project -d aquaculture`
+    Then the stdout should not contain "deleted project"
+    And the output should match /^  reading aquaculture digest$/
+    And the output should match /^  aquaculture$/
+    And the stderr should contain "error: cannot delete multiple projects"
+
+  Scenario: Tagging a project with a tag
+    Given an existing project file
+    When I successfully run `tempo project backyard bonsai -t patience`
+    Then the stdout should contain "backyard bonsai"
+    And the stdout should contain "tags: [miniaturization, outdoors, patience]"
+    And the project file should contain "- patience"
+
+  Scenario: Tagging a project by Id with a tag
+    Given an existing project file
+    When I successfully run `tempo project -i 3 -t patience`
+    Then the stdout should contain "basement mushrooms"
+    And the stdout should contain "tags: [fungi, indoors, patience]"
+    And the project file should contain "- patience"
+
+  Scenario: Tagging a project with tags
+    Given an existing project file
+    When I successfully run `tempo project backyard bonsai -t 'patience japanese'`
+    Then the stdout should contain "backyard bonsai"
+    And the stdout should contain "tags: [japanese, miniaturization, outdoors, patience]"
+    And the project file should contain "- patience"
+    And the project file should contain "- japanese"
+
+  Scenario: Attempting to tag a project with a duplicate tag
+    Given an existing project file
+    When I successfully run `tempo project backyard bonsai -t outdoors`
+    Then the stdout should contain "backyard bonsai"
+    And the stdout should contain "tags: [miniaturization, outdoors]"
+
+  Scenario: Attemting to tag a project by non-existing id
+    Given an existing project file
+    When I run `tempo project -i 30 -t patience`
+    Then the stderr should contain "no projects match the request: id=30"
+
+  Scenario: Untagging a project with a tag
+    Given an existing project file
+    When I successfully run `tempo project mushrooms -u fungi`
+    Then the stdout should contain "basement mushrooms"
+    And the stdout should contain "tags: [indoors]"
+    And the project file should not contain "- fungi"
+
+  Scenario: Untagging a project by Id
+    Given an existing project file
+    When I successfully run `tempo project -i 3 -u fungi`
+    Then the stdout should contain "basement mushrooms"
+    And the stdout should contain "tags: [indoors]"
+    And the project file should not contain "- fungi"
+
+  Scenario: Untagging a project with tags
+    Given an existing project file
+    When I successfully run `tempo project mushrooms -u 'indoors fungi'`
+    Then the stdout should contain "basement mushrooms"
+    And the stdout should contain "tags: none"
+    And the project file should not contain "- fungi"
+
+  Scenario: Tagging and Untagging a project
+    Given an existing project file
+    When I successfully run `tempo project backyard bonsai -u miniaturization -t shrubs`
+    Then the stdout should contain "backyard bonsai"
+    And the stdout should contain "tags: [outdoors, shrubs]"
+    And the project file should contain "- shrubs"
+
+  Scenario: Adding a new project with tags
+    Given an existing project file
+    When I successfully run `tempo project -a fly fishing -t 'patience fish'`
+    Then the stdout should contain "added project:"
+    And the stdout should contain "fly fishing  tags: [fish, patience]"
+    And the project file should contain "- patience"
+    And the project file should contain "- fish"
+
+  Scenario: Attempting to tag a project with ambiguous match
+    Given an existing project file
+    When I run `tempo project 'aquaculture' -t japanese`
+    Then the stdout should not contain "japanese"
+    And the stderr should contain "error: cannot tag multiple projects"
+    And the project file should not contain "- japanese"

data/features/report.feature

@@ -0,0 +1,62 @@
+Feature: Report Command formats and outputs time records
+  The report command echoes time records in an easy to view format.
+
+  Scenario: Attempting to report time records before any projects exist
+    Given a clean installation
+    When I run `tempo report`
+    Then the stderr should contain "no projects exist"
+    And the project file should contain "#" at line 1
+
+  Scenario: Attempting to report time records before any time records exist
+    Given an existing project file
+    When I run `tempo report`
+    Then the stderr should contain "no time records exist"
+
+  Scenario: Reporting the time entries on the current day
+    Given an existing project file
+    When I run `tempo start -a 7 my new project`
+    And I run `tempo end -a 8`
+    And I run `tempo report`
+    Then the output should match /\d{2}:\d{2} - \d{2}:\d{2}  \[\d{1,2}:\d{2}\] horticulture: my new project/
+
+  Scenario: Reporting the time entries on a specific day
+    Given an existing project file
+    And an existing time record file
+    When I run `tempo start --at "2014-01-02" this will add a new record file`
+    And I run `tempo report "2014-01-01"`
+    Then the output should contain "Records for 01/01/2014:"
+    And the output should not contain "Records for 01/02/2014:"
+    And the output should contain "horticulture: putting on overalls and straw hat"
+
+  Scenario: Reporting the time entries for multipe days
+    Given an existing project file
+    And an existing time record file
+    When I run `tempo start --at "2014-01-02" this will add a newer record file`
+    When I run `tempo start --at "2014-01-03" and an even newer record file`
+    And I run `tempo report --from "2014-01-01" --to "2014-01-03"`
+    Then the output should contain "Records for 01/01/2014:"
+    And the output should contain "Records for 01/02/2014:"
+    And the output should contain "Records for 01/03/2014:"
+
+@pending
+  Scenario: Reporting the time entries for multipe days using d_ids
+    Given an existing project file
+    And an existing time record file
+    When I run `tempo start --at "2014-01-02" this will add a newer record file`
+    When I run `tempo start --at "2014-01-03" and an even newer record file`
+    And I run `tempo report --from "20140101" --to "20140103"`
+    Then the output should contain "Records for 01/01/2014:"
+    And the output should contain "Records for 01/2/2014:"
+    And the output should contain "Records for 01/03/2014:"
+
+  Scenario: Reporting the time entries with ids
+  Given an existing project file
+  And an existing time record file
+  And I run `tempo -i report "2014-01-01"`
+  And the output should contain "[1] 05:00 - 05:15  [0:15] horticulture: putting on overalls and straw hat"
+  And the output should contain "[2] 05:15 - 08:15  [3:00] backyard bonsai: trimming the trees"
+  And the output should contain "[3] 08:15 - 10:38  [2:23] backyard bonsai: mixing up a batch of potting soil"
+  And the output should contain "[4] 12:52 - 13:26  [0:34] aquaculture: putting on the wetsuit"
+  And the output should contain "[5] 13:32 - 16:46  [3:14] nano aquarium: trimming the coral"
+
+

data/features/start.feature

@@ -0,0 +1,87 @@
+Feature: Start Command starts a new time record
+  The start command starts a time record referencing the current project
+  It records projects in log files by day. Only one time entry will be
+  running at any given time; new entries close out the last running time record.
+
+  Scenario: Attempting to add time before any projects exist
+    Given a clean installation
+    When I run `tempo start`
+    Then the stderr should contain "no projects exist"
+    And the project file should contain "#" at line 1
+
+  Scenario: Adding a time record for the current time
+    Given an existing project file
+    When I run `tempo start`
+    Then the stdout should contain "time record started"
+
+  Scenario: Adding a time record for the current time with a description
+    Given an existing project file
+    When I run `tempo start my new project`
+    Then the stdout should contain "time record started"
+    And the stdout should contain "horticulture: my new project"
+
+  Scenario: Attempting to add an invalid start time
+    Given an existing project file
+    When I run `tempo start --at "invalid time"`
+    Then the stderr should contain "no valid timeframe matches the request: invalid time"
+
+  Scenario: Adding a time record for a specific time
+    Given an existing project file
+    When I run `tempo start --at "15:00 today"`
+    Then the stdout should contain "time record started"
+    And the output should match /15:00 - \d{2}:\d{2}\*/
+
+  Scenario: Adding a time record with an end time
+    Given an existing project file
+    When I run `tempo start --end "1 hour from now"`
+    Then the stdout should contain "time record started"
+    And the output should match /\d{2}:\d{2} - \d{2}:\d{2}/
+@pending
+  Scenario: Adding a time record with tags
+    Given an existing project file
+
+  Scenario: Attempting to add time that collides with an existing record
+    Given an existing project file
+    When I run `tempo start --at "1-1-2014 7:00"`
+    And I run `tempo end --at "1-1-2014 10:00"`
+    And I run `tempo start --at "1-1-2014 8:00"`
+    Then the stderr should contain "error: Time conflict with existing record"
+
+  Scenario: Adding a time record and closing out the last one
+    Given an existing project file
+    When I run `tempo start --at "1-1-2014 7:00"`
+    And I run `tempo start --at "1-1-2014 8:00"`
+    Then the stdout should contain "time record started"
+    And the time record 20140101 should contain ":end_time: 2014-01-01 08:00:00" at line 5
+
+  Scenario: Adding a time record and closing out the previous day
+    Given an existing project file
+    When I run `tempo start --at "1-1-2014 7:00"`
+    And I run `tempo start --at "1-3-2014 10:00"`
+    Then the stdout should contain "time record started"
+    And the time record 20140101 should contain ":end_time: 2014-01-01 23:59" at line 5
+@pending
+  Scenario: Adding an evening time record should compensate for local time
+    # need to mock entering time in the evening, 21:26:46 -0400
+    # make sure --at "5:00" is recorded for the local day, not GMC
+
+# Adding a time record at the beginning of the day seems to close out at the last time record
+# check on and fix this bug.
+ @pending
+  Scenario: Adding an earlier time record should immediately close out
+    Given an existing project file
+    When I run `tempo start --at "1-1-2014 9:00"`
+    And I run `tempo start --at "1-1-2014 17:00"`
+    And I run `tempo start --at "1-1-2014 6:00"`
+    Then the stdout should contain "time record started"
+    And the time record 20140101 should contain ":end_time: 2014-01-01 9:00" at line 5
+
+  Scenario: Adding an earlier day time record should immediately close out
+    Given an existing project file
+    When I run `tempo start --at "1-5-2014 7:00"`
+    And I run `tempo start --at "1-1-2014 7:00"`
+    Then the stdout should contain "time record started"
+    And the time record 20140101 should contain ":end_time: 2014-01-01 23:59" at line 5
+
+
+

data/features/step_definitions/tempo_steps.rb

@@ -0,0 +1,138 @@
+When /^I get help for "([^""]*)"$/ do |app_name|
+  @app_name = app_name
+  step %(I run `#{app_name} help`)
+end
+
+Given /^a clean installation$/ do
+  @testing_env = File.join( ENV['HOME'], 'tempo' )
+  FileUtils.rm_r( @testing_env ) if File.exists?( @testing_env )
+end
+
+Given /^an existing project file$/ do
+  @testing_env = File.join( ENV['HOME'], 'tempo' )
+  FileUtils.rm_r( @testing_env ) if File.exists?( @testing_env )
+  Dir.mkdir( @testing_env, 0700 )
+  projects_file = File.join( @testing_env, 'tempo_projects.yaml' )
+
+  File.open( projects_file,'w' ) do |f|
+    projects = ["---", ":id: 1", ":parent: :root", ":children:", "- 2", "- 3", ":title: horticulture", ":tags:", "- cultivation", ":current: true",
+                "---", ":id: 2", ":parent: 1", ":children: []", ":title: backyard bonsai", ":tags:", "- miniaturization", "- outdoors",
+                "---", ":id: 3", ":parent: 1", ":children: []", ":title: basement mushrooms", ":tags:", "- fungi", "- indoors",
+                "---", ":id: 4", ":parent: :root", ":children:", "- 5", "- 6", ":title: aquaculture", ":tags:", "- cultivation",
+                "---", ":id: 5", ":parent: 4", ":children: []", ":title: nano aquarium", ":tags:", "- miniaturization",
+                "---", ":id: 6", ":parent: 4", ":children: []", ":title: reading aquaculture digest", ":tags: []"]
+
+    projects.each do |p|
+      f.puts p
+    end
+  end
+end
+
+Given /^an existing time record file$/ do
+  @records_directory = File.join( ENV['HOME'], 'tempo/tempo_time_records' )
+  FileUtils.rm_r( @records_directory ) if File.exists?( @records_directory )
+  Dir.mkdir( @records_directory, 0700 )
+  projects_file = File.join( @records_directory, '20140101.yaml' )
+
+  File.open( projects_file,'w' ) do |f|
+    records = [ ":description: putting on overalls and straw hat",
+                ":start_time: 2014-01-01 05:00:00.000000000 -05:00",
+                ":end_time: 2014-01-01 05:15:00.000000000 -05:00",
+                ":id: 1",
+                ":project: 1",
+                ":tags: []",
+                "---",
+                ":project_title: backyard bonsai",
+                ":description: trimming the trees",
+                ":start_time: 2014-01-01 05:15:00.000000000 -05:00",
+                ":end_time: 2014-01-01 08:15:00.000000000 -05:00",
+                ":id: 2",
+                ":project: 2",
+                ":tags: []",
+                "---",
+                ":project_title: backyard bonsai",
+                ":description: mixing up a batch of potting soil",
+                ":start_time: 2014-01-01 08:15:00.000000000 -05:00",
+                ":end_time: 2014-01-01 10:38:00.000000000 -05:00",
+                ":id: 3",
+                ":project: 2",
+                ":tags: []",
+                "---",
+                ":project_title: aquaculture",
+                ":description: putting on the wetsuit",
+                ":start_time: 2014-01-01 12:52:00.000000000 -05:00",
+                ":end_time: 2014-01-01 13:26:00.000000000 -05:00",
+                ":id: 4",
+                ":project: 4",
+                ":tags: []",
+                "---",
+                ":project_title: nano aquarium",
+                ":description: trimming the coral",
+                ":start_time: 2014-01-01 13:32:00.000000000 -05:00",
+                ":end_time: 2014-01-01 16:46:00.000000000 -05:00",
+                ":id: 5",
+                ":project: 5",
+                ":tags: []" ]
+    records.each do |p|
+      f.puts p
+    end
+  end
+end
+
+
+
+
+Then /^the time record (.*?) should contain "(.*?)" at line (\d+)$/ do |arg1, arg2, arg3|
+  file = File.join( ENV['HOME'], 'tempo/tempo_time_records', "#{arg1}.yaml")
+  contents = []
+  File.open(file, "r") do |f|
+    f.readlines.each do |line|
+      contents << line.chomp
+    end
+  end
+  contents[arg3.to_i - 1].should include arg2
+end
+
+Then /^the time record (.*?) should not contain "(.*?)"$/ do |arg1, arg2|
+  file = File.join( ENV['HOME'], 'tempo/tempo_time_records', "#{arg1}.yaml")
+  contents = []
+  File.open(file, "r") do |f|
+    f.readlines.each do |line|
+      contents << line.chomp
+    end
+  end
+  contents.should_not include arg2
+end
+
+Then /^the (.*?) file should contain "(.*?)" at line (\d+)$/ do |arg1, arg2, arg3|
+  file = File.join( ENV['HOME'], 'tempo', "tempo_#{arg1}s.yaml")
+  contents = []
+  File.open(file, "r") do |f|
+    f.readlines.each do |line|
+      contents << line.chomp
+    end
+  end
+  contents[arg3.to_i - 1].should include arg2
+end
+
+Then /^the (.*?) file should contain "(.*?)"$/ do |arg1, arg2|
+  file = File.join( ENV['HOME'], 'tempo', "tempo_#{arg1}s.yaml")
+  contents = []
+  File.open(file, "r") do |f|
+    f.readlines.each do |line|
+      contents << line.chomp
+    end
+  end
+  contents.should include arg2
+end
+
+Then /^the (.*?) file should not contain "(.*?)"$/ do |arg1, arg2|
+  file = File.join( ENV['HOME'], 'tempo', "tempo_#{arg1}s.yaml")
+  contents = []
+  File.open(file, "r") do |f|
+    f.readlines.each do |line|
+      contents << line.chomp
+    end
+  end
+  contents.should_not include arg2
+end

data/features/support/env.rb

@@ -0,0 +1,26 @@
+require 'aruba/cucumber'
+
+ENV['PATH'] = "#{File.expand_path(File.dirname(__FILE__) + '/../../bin')}#{File::PATH_SEPARATOR}#{ENV['PATH']}"
+LIB_DIR = File.join(File.expand_path(File.dirname(__FILE__)),'..','..','lib')
+
+Before do
+
+  ## Using "announce" causes massive warnings on 1.9.2
+  # @puts = true
+  # @original_rubylib = ENV['RUBYLIB']
+  # ENV['RUBYLIB'] = LIB_DIR + File::PATH_SEPARATOR + ENV['RUBYLIB'].to_s
+
+  # switch home environment for testing in Rakefile
+  # example for doing this within cucumber:
+  #
+  @real_home = ENV['HOME']
+  @testing_env = File.join(ENV['HOME'], 'testing_features')
+  #FileUtils.rm_rf @testing_env, :secure => true
+  Dir.mkdir(@testing_env, 0700) unless File.exists?(@testing_env)
+  ENV['HOME'] = @testing_env
+end
+
+After do
+  #FileUtils.rm_rf @testing_env, :secure => true
+  ENV['HOME'] = @real_home
+end

data/features/tempo.feature

@@ -0,0 +1,13 @@
+Feature: GLI bootstrapping sets up cucumber
+  GLI scaffold includes aruba and cucumber setup
+  Running the tempo project for the first time sets up the folder stucture
+
+  Scenario: App just runs
+    When I get help for "tempo"
+    Then the exit status should be 0
+
+  Scenario: App initialization creates all necessary files
+    Given a clean installation
+    When I successfully run `tempo project new project`
+    Then the exit status should be 0
+    And the project file should contain ":title: new project"

data/features/update.feature

@@ -0,0 +1,69 @@
+Feature: Update Command manages edits to the time records
+  Time record start and end times, descriptions, and projects can be changed,
+  or whole records can be deleted. Time records can be chosen by id and day
+
+  Scenario: Attempting to update on a day with no records
+    Given an existing project file
+    And an existing time record file
+    When I run `tempo update --on 1/1/2015 practicing banjo`
+    Then the stderr should contain "no time records on 01/01/2015 exist"
+
+  Scenario: Attempting to update by id with no matching records
+    Given an existing project file
+    And an existing time record file
+    When I run `tempo update --id 22 practicing banjo`
+    Then the stderr should contain "no time record on 01/01/2014 matches the request: id = 22"
+
+  Scenario: Deleting the last record
+    Given an existing project file
+    And an existing time record file
+    When I successfully run `tempo update --delete`
+    Then the stdout should contain "time record deleted:\n13:32 - 16:46  [3:14] nano aquarium: trimming the coral"
+    And the time record 20140101 should not contain "nano aquarium"
+
+  Scenario: Updating the description for the last time record
+    Given an existing project file
+    And an existing time record file
+    When I successfully run `tempo update anemone feeding`
+    Then the stdout should contain "time record updated:\n13:32 - 16:46  [3:14] nano aquarium: anemone feeding"
+    And the time record 20140101 should contain ":description: anemone feeding" at line 35
+
+  Scenario: Updating the start time for the last time record
+    Given an existing project file
+    And an existing time record file
+    When I successfully run `tempo update --start "2014-01-01 13:45"`
+    Then the stdout should contain "time record updated:\n13:45 - 16:46  [3:01] nano aquarium: trimming the coral"
+    And the time record 20140101 should contain ":start_time: 2014-01-01 13:45:00" at line 36
+
+  Scenario: Updating the end time for the last time record
+    Given an existing project file
+    And an existing time record file
+    When I successfully run `tempo update --end "2014-01-01 16:35"`
+    Then the stdout should contain "time record updated:\n13:32 - 16:35  [3:03] nano aquarium: trimming the coral"
+    And the time record 20140101 should contain ":end_time: 2014-01-01 16:35:00" at line 37
+
+  Scenario: Updating to the project for the last time record
+    Given an existing project file
+    And an existing time record file
+    When I successfully run `tempo update --project`
+    Then the stdout should contain "time record updated:\n13:32 - 16:46  [3:14] horticulture: trimming the coral"
+    And the time record 20140101 should contain ":description: trimming the coral" at line 35
+
+  Scenario: Updating a time record on an earlier day
+    Given an existing project file
+    And an existing time record file
+    When I run `tempo start --at "12/1/2013 7:00" --end "12/1/2013 8:00" raking leaves`
+    And I run `tempo start --at "12/1/2013 8:00" --end "12/1/2013 9:00" counting rosebuds`
+    When I successfully run `tempo update --on "12/1/2013" --id 1 feeding flytraps`
+    Then the stdout should contain "time record updated:\n07:00 - 08:00  [1:00] horticulture: feeding flytraps"
+    And the time record 20131201 should contain ":description: feeding flytraps" at line 3
+
+  Scenario: Updating the end time on a time record on an earlier day
+    Given an existing project file
+    And an existing time record file
+    When I run `tempo start --at "12/1/2013 7:00" --end "12/1/2013 8:00" raking leaves`
+    And I run `tempo start --at "12/1/2013 9:00" --end "12/1/2013 10:00" counting rosebuds`
+    When I successfully run `tempo update --on "12/1/2013" --id 1 --end "12/1/2013 8:35"`
+    Then the stdout should contain "time record updated:\n07:00 - 08:35  [1:35] horticulture: raking leaves"
+    And the time record 20131201 should contain ":end_time: 2013-12-01 08:35:00" at line 5
+

data/lib/file_record/directory.rb

@@ -0,0 +1,11 @@
+module FileRecord
+  class Directory
+    class << self
+      def create_new
+        cwd = File.expand_path File.dirname(__FILE__)
+        source = File.join(cwd, "directory_structure/tempo")
+        FileUtils.cp_r( source, Dir.home )
+      end
+    end
+  end
+end

data/lib/file_record/directory_structure/tempo/README.txt

@@ -0,0 +1,4 @@
+Tempo is a command line time tracking application for creating time sheets based on a project hierarchy.
+
+
+All records will be stored in the tempo folder in the users home directory.  Records are stored in yaml, and can be edited by hand, with discretion.  Be aware that editing by hand could create unresolvable conflicts, especially when it comes to the ids assigned to projects.

data/lib/file_record/directory_structure/tempo/tempo_projects.yaml

@@ -0,0 +1,6 @@
+# Tempo projects file for tempo command line time tracker
+# No projects have been created yet, run
+#
+#   `tempo projects 'my new project name'
+#
+# to create a new project that will replace this message