techcor 0.0.1

data/Gemfile

@@ -0,0 +1,22 @@
+source :rubygems
+
+group :test do
+  gem 'rspec'
+  gem 'cucumber'
+  gem 'autotest'
+  gem 'simplecov'
+  gem 'mongoid-rspec'
+  gem 'aruba'
+end
+
+group :development do
+  gem 'pry'
+  gem 'rake'
+  gem 'jeweler'
+end
+
+gem 'activesupport'
+gem 'mongoid', '~> 3.0.0.rc'
+gem 'bson_ext'
+gem 'hirb'
+gem 'gli', '~> 2.0.0.rc'

data/Gemfile.lock

@@ -0,0 +1,96 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    ZenTest (4.8.1)
+    activemodel (3.2.6)
+      activesupport (= 3.2.6)
+      builder (~> 3.0.0)
+    activesupport (3.2.6)
+      i18n (~> 0.6)
+      multi_json (~> 1.0)
+    aruba (0.4.11)
+      childprocess (>= 0.2.3)
+      cucumber (>= 1.1.1)
+      ffi (>= 1.0.11)
+      rspec (>= 2.7.0)
+    autotest (4.4.6)
+      ZenTest (>= 4.4.1)
+    bson (1.6.4)
+    bson_ext (1.6.4)
+      bson (~> 1.6.4)
+    builder (3.0.0)
+    childprocess (0.3.2)
+      ffi (~> 1.0.6)
+    coderay (1.0.6)
+    cucumber (1.2.1)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.11.0)
+      json (>= 1.4.6)
+    diff-lcs (1.1.3)
+    ffi (1.0.11)
+    gherkin (2.11.1)
+      json (>= 1.4.6)
+    git (1.2.5)
+    gli (2.0.0.rc4)
+    hirb (0.6.2)
+    i18n (0.6.0)
+    jeweler (1.8.4)
+      bundler (~> 1.0)
+      git (>= 1.2.5)
+      rake
+      rdoc
+    json (1.7.3)
+    method_source (0.7.1)
+    mongoid (3.0.0.rc)
+      activemodel (~> 3.1)
+      moped (~> 1.0.0.rc)
+      origin (~> 1.0.0.rc)
+      tzinfo (~> 0.3.22)
+    mongoid-rspec (1.4.6)
+      mongoid (>= 3.0.0.rc)
+      rake
+      rspec (>= 2.9)
+    moped (1.0.0.rc)
+    multi_json (1.3.6)
+    origin (1.0.1)
+    pry (0.9.9.6)
+      coderay (~> 1.0.5)
+      method_source (~> 0.7.1)
+      slop (>= 2.4.4, < 3)
+    rake (0.9.2.2)
+    rdoc (3.12)
+      json (~> 1.4)
+    rspec (2.10.0)
+      rspec-core (~> 2.10.0)
+      rspec-expectations (~> 2.10.0)
+      rspec-mocks (~> 2.10.0)
+    rspec-core (2.10.1)
+    rspec-expectations (2.10.0)
+      diff-lcs (~> 1.1.3)
+    rspec-mocks (2.10.1)
+    simplecov (0.6.4)
+      multi_json (~> 1.0)
+      simplecov-html (~> 0.5.3)
+    simplecov-html (0.5.3)
+    slop (2.4.4)
+    tzinfo (0.3.33)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activesupport
+  aruba
+  autotest
+  bson_ext
+  cucumber
+  gli (~> 2.0.0.rc)
+  hirb
+  jeweler
+  mongoid (~> 3.0.0.rc)
+  mongoid-rspec
+  pry
+  rake
+  rspec
+  simplecov

data/README.md

@@ -0,0 +1,27 @@
+[![Build Status](https://secure.travis-ci.org/maksar/tc.png)](http://travis-ci.org/maksar/tc)
+[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/maksar/tc)
+
+Technical Coordination project
+---------------
+
+This repository contains code, related and useful for performing technical coordination tasks -- collecting informational (technology, start date, current status, etc.) and statistical (unit tests count, unit tests coverage, build time, etc.) information about projects.
+
+`tc` console tools allows to manage mentioned above information (add projects, edit metrics, etc.). Information itself is stored in `mongodb`. `tc` tool can be used in CI environments to automatically collect metrics (like coverage and build time).
+
+In future, it is planned to have web interface for doing same operation as with cli `tc` tool. For now, use `tc --help` to get information about supported operations and commands.
+
+Examples:
+
+* Add new project
+
+        tc add project_name
+
+* Add new metric
+
+        tc add_metric --mt number --pn project_name metric_name
+
+* List unit tests count for all ruby projects
+
+        tc list --fm "{'Name' => 'name', 'Unit tests' => 'property(\"unit tests count\").value'}" "property('technology') == 'ruby'"
+
+Code is not released as a separate gem, but will be in a nearest future.

data/Rakefile

@@ -0,0 +1,45 @@
+require 'rspec/core/rake_task'
+require 'cucumber/rake/task'
+
+Cucumber::Rake::Task.new(:cucumber)
+RSpec::Core::RakeTask.new(:rspec) do |t|
+  t.rspec_opts = ' -r simplecov'
+end
+
+desc "Creates bunch of test data in database"
+task :seed do
+  require_relative 'db/seed'
+  seed
+end
+
+desc "Run Cucumber & RSpec to generate aggregated coverage"
+task :default do
+  FileUtils.rm_rf('coverage')
+
+  Rake::Task['rspec'].invoke
+  Rake::Task["cucumber"].invoke
+end
+
+require 'jeweler'
+require_relative 'lib/tc/version'
+Jeweler::Tasks.new do |gem|
+  gem.name = "techcor"
+  gem.homepage = "http://github.com/maksar/tc"
+  gem.license = "MIT"
+  gem.summary = %Q{Console tool allowing to perform technical coordination activities}
+  gem.description = %Q{This gem provides 'tc' console utility, which allows to collect and manage different metrics on software projects.}
+  gem.email = "Maksar.mail@gmail.com"
+  gem.authors = ["Alexander Shestakov"]
+
+  gem.executables = %w(tc)
+  gem.version = TC::Version::STRING
+
+  gem.files.exclude '.*'
+  gem.files.exclude '*.gemspec'
+
+  gem.add_dependency 'mongoid', '~> 3.0.0.rc'
+  gem.add_dependency 'bson_ext'
+  gem.add_dependency 'hirb'
+  gem.add_dependency 'gli', '~> 2.0.0.rc'
+end
+Jeweler::RubygemsDotOrgTasks.new

data/bin/tc

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+
+require_relative '../lib/gli_interface'
+
+exit TcCli.exec(ARGV)
+

data/config/cucumber.yml

@@ -0,0 +1,2 @@
+---
+default: --color --format progress  

data/config/mongoid.yml

@@ -0,0 +1,29 @@
+development:
+  sessions:
+    default:
+      hosts:
+        - localhost:27017
+      database: tc_development
+      logger: false
+  options:
+    raise_not_found_error: false
+
+test:
+  sessions:
+    default:
+      hosts:
+        - localhost:27017
+      database: tc_test
+      logger: false
+  options:
+    raise_not_found_error: false
+
+production:
+  sessions:
+    default:
+      hosts:
+        - localhost:27017
+      database: tc_production
+      logger: false
+  options:
+    raise_not_found_error: false

data/config/mongoid.yml.sample

@@ -0,0 +1,29 @@
+development:
+  sessions:
+    default:
+      hosts:
+        - localhost:27017
+      database: tc_development
+      logger: false
+  options:
+    raise_not_found_error: false
+
+test:
+  sessions:
+    default:
+      hosts:
+        - localhost:27017
+      database: tc_test
+      logger: false
+  options:
+    raise_not_found_error: false
+
+production:
+  sessions:
+    default:
+      hosts:
+        - localhost:27017
+      database: tc_production
+      logger: false
+  options:
+    raise_not_found_error: false

data/db/seed.rb

@@ -0,0 +1,37 @@
+ENV['RACK_ENV'] ||= 'development'
+
+require_relative '../lib/tc'
+
+def seed
+  Project.delete_all
+
+  user = 'a.shestakov'
+
+  ProjectCatalog.new.
+      add_project(
+      Project.new(name: 'TC').
+          add_metric(StringMetric.new(name: 'Technology').edit('Ruby', user)).
+          add_metric(BooleanMetric.new(name: 'Active').edit(true, user)).
+          add_metric(StringMetric.new(name: 'SCM').edit('http://github.com/maksar/tc', user)).
+          add_metric(StringMetric.new(name: 'CI').edit('http://travis-ci.org/#!/maksar/tc', user)).
+          add_metric(NumberMetric.new(name: 'Unit Tests Coverage').edit(98.55, user)).
+          add_metric(NumberMetric.new(name: 'Unit Tests Count').edit(40, user)).
+          add_metric(NumberMetric.new(name: 'Cucumber Tests Coverage').edit(92.68, user)).
+          add_metric(NumberMetric.new(name: 'Cucumber Tests Count').edit(10, user)).
+          add_metric(NumberMetric.new(name: 'Tests Coverage').edit(100, user)).
+          edit_property('Unit Tests Count', 45, user).
+          edit_property('Unit Tests Count', 60, user).
+          edit_property('Unit Tests Count', 100, user).
+          edit_property('Unit Tests Coverage', 99, user).
+          edit_property('Unit Tests Coverage', 100, user)
+  ).
+      add_project(Project.new(name: 'Anagrams').
+                      add_metric(StringMetric.new(name: 'Technology').edit('Ruby', user)).
+                      add_metric(BooleanMetric.new(name: 'Active').edit(false, user)).
+                      add_metric(StringMetric.new(name: 'SCM').edit('http://github.com/maksar/anagrams', user)).
+                      add_metric(StringMetric.new(name: 'CI').edit('http://travis-ci.org/#!/maksar/anagrams', user)).
+                      add_metric(NumberMetric.new(name: 'Unit Tests Coverage').edit(100, user)).
+                      add_metric(NumberMetric.new(name: 'Unit Tests Count').edit(6, user)).
+                      add_metric(NumberMetric.new(name: 'Tests Coverage').edit(100, 'john.dow'))).
+      save
+end

data/features/add_metric.feature

@@ -0,0 +1,9 @@
+Feature: Adding metric
+  In order to add new metric to the project
+  As a console user
+  I want to be able to do that
+
+  Scenario: adding metric
+    Given catalog filled by seeds script
+    When I execute cli "add_metric --pn TC --mt number new_metric"
+    Then the cli output should contain "Metric new_metric with type number was successfully added to project TC."

data/features/add_project.feature

@@ -0,0 +1,9 @@
+Feature: Adding project
+  In order to add new project
+  As a console user
+  I want to be able to do that
+
+  Scenario: adding project
+    Given no projects in catalog
+    When I execute cli "add TC"
+    Then the cli output should contain "Project TC was successfully added."

data/features/console_interface.feature

@@ -0,0 +1,58 @@
+Feature: console command
+  In order to do technical coordination
+  As a console user
+  I want use cli (command line interface)
+
+  Scenario: View general help in cli
+    When I execute cli "help"
+    Then the cli output should contain "Command Line Interface for Technical Coordination"
+    And the cli output should contain "[global options] command [command options] [arguments...]"
+    And the output have option "add" with description "Adds new project"
+    And the output have option "add_metric" with description "Adds new metric to the project"
+    And the output have option "edit_property" with description "Edits one metric of the project"
+    And the output have option "list" with description "List projects from catalog"
+
+  Scenario: View help of add command
+    When I execute cli "help add"
+    Then the cli output should contain "Adds new project"
+    And the cli output should contain "add [command options] {project_name}"
+    And the cli output should contain "Adds new project"
+    And the cli output should contain "Allows to create new project"
+
+  Scenario: View help of add_metric command
+    When I execute cli "help add_metric"
+    Then the cli output should contain "add_metric [command options] {metric_name}"
+    And the cli output should contain "Adds new metric to the project"
+    And the cli output should contain "Allows to add new metric to the project"
+    And the output should have flag "mt/metric_type" with name "metric type" and description "type of the metric you want to add (string, number, boolean) (default: string)"
+    And the output should have flag "pn/project_name" with name "project name" and description "name of the project, to which you want to add metric"
+
+  Scenario: View help of edit_property command
+    When I execute cli "help edit_property"
+    Then the cli output should contain "edit_property [command options] {value}"
+    And the cli output should contain "Edits one metric of the project"
+    And the cli output should contain "Allows to edit one of the project's metrics"
+    And the output should have flag "mn/metric_name" with name "metric name" and description "name of the metric, which you want to edit"
+    And the output should have flag "pn/project_name" with name "project name" and description "name of the project, property of which you want to edit"
+
+  Scenario: View help of list command
+    When I execute cli "help list"
+    Then the cli output should contain "list [command options] {criteria}"
+    And the cli output should contain "List projects from catalog"
+    And the cli output should contain "Lists projects from catalog matching specified criteria"
+    And the output should have flag "fm/format" with name "table format" and description "ruby code for table format"
+
+  Scenario: View help of history command
+    When I execute cli "help history"
+    Then the cli output should contain "history [command options] [{property}],[{another_property}],[...]"
+    And the cli output should contain "Displays property history"
+    And the cli output should contain "Displays one or more properties history (list of values over time)"
+    And the output should have flag "pn/project_name" with name "project name" and description "name of the project, property of which you want to edit"
+    And the output should have flag "df/date_format" with name "date format" and description "ruby date format to display time of change (default: %d-%m-%Y)"
+
+  Scenario: View help of describe command
+    When I execute cli "help describe"
+    Then the cli output should contain "describe [command options] {project_name}"
+    And the cli output should contain "Describes current state of the project"
+    And the cli output should contain "Displays current metrics of the project, date and author of last modification"
+    And the output should have flag "df/date_format" with name "date format" and description "ruby date format to display time of change (default: %d-%m-%Y)"

data/features/describe_project.feature

@@ -0,0 +1,25 @@
+Feature: Describing project
+  In order to view project metrics
+  As a console user
+  I want to see state of all current project metrics
+
+  Scenario: describing project
+    Given catalog filled by seeds script
+    When I execute cli "describe --df ---- TC"
+    Then the cli output should contain:
+    """
+    +-------------------------+-----------------------------------+------------+-------------+
+    | Metric                  | Value                             | Changed at | Changed by  |
+    +-------------------------+-----------------------------------+------------+-------------+
+    | Technology              | Ruby                              | ----       | a.shestakov |
+    | Active                  | true                              | ----       | a.shestakov |
+    | SCM                     | http://github.com/maksar/tc       | ----       | a.shestakov |
+    | CI                      | http://travis-ci.org/#!/maksar/tc | ----       | a.shestakov |
+    | Unit Tests Coverage     | 100.0                             | ----       | a.shestakov |
+    | Unit Tests Count        | 100.0                             | ----       | a.shestakov |
+    | Cucumber Tests Coverage | 92.68                             | ----       | a.shestakov |
+    | Cucumber Tests Count    | 10.0                              | ----       | a.shestakov |
+    | Tests Coverage          | 100.0                             | ----       | a.shestakov |
+    +-------------------------+-----------------------------------+------------+-------------+
+    9 rows in set
+    """

data/features/edit_property.feature

@@ -0,0 +1,9 @@
+Feature: Edit property
+  In order to edit property of the project
+  As a console user
+  I want to be able to do that
+
+  Scenario: editing property
+    Given catalog filled by seeds script
+    When I execute cli "edit_property --pn TC --mn Technology RoR"
+    Then the cli output should contain "Metric Technology in project TC now has value RoR."

data/features/list_projects.feature

@@ -0,0 +1,69 @@
+Feature: Listing projects in console
+  In order to view projects by criteria
+  As a console user
+  I want to specify criteria and see list of the projects
+
+  Scenario: listing empty project catalog with empty criteria
+    Given no projects in catalog
+    When I execute cli "list --fm "{'Name' => 'name', 'Count' => '\\'Count: \\' + property(\\'Unit Tests Count\\').value.to_s'}" "
+    Then the cli output should contain "0 rows in set"
+
+  Scenario: listing empty project catalog with specified criteria
+    Given no projects in catalog
+    When I execute cli "list --fm "{'Name' => 'name', 'Count' => '\\'Count: \\' + property(\\'Unit Tests Count\\').value.to_s'}" "property('Unit Tests Count').value == 1""
+    Then the cli output should contain "0 rows in set"
+
+  Scenario: listing projects catalog with empty criteria
+    Given catalog filled by seeds script
+    When I execute cli "list --fm "{'Name' => 'name', 'Count' => '\\'Count: \\' + property(\\'Unit Tests Count\\').value.to_s'}" "
+    Then the cli output should contain:
+    """
+    +----------+--------------+
+    | Name     | Count        |
+    +----------+--------------+
+    | Anagrams | Count: 6.0   |
+    | TC       | Count: 100.0 |
+    +----------+--------------+
+    2 rows in set
+    """
+
+  Scenario: listing projects catalog with simple criteria
+    Given catalog filled by seeds script
+    When I execute cli "list --fm "{'Name' => 'name', 'Count' => '\\'Count: \\' + property(\\'Unit Tests Count\\').value.to_s'}" "property('Unit Tests Count').value == 6""
+    Then the cli output should contain:
+    """
+    +----------+------------+
+    | Name     | Count      |
+    +----------+------------+
+    | Anagrams | Count: 6.0 |
+    +----------+------------+
+    1 row in set
+    """
+
+  Scenario: listing projects catalog with complex criteria
+    Given catalog filled by seeds script
+    When I execute cli "list --fm "{'Name' => 'name', 'Count' => '\\'Count: \\' + property(\\'Unit Tests Count\\').value.to_s'}" "property('Unit Tests Count').value == 6 || property('Unit Tests Count').value == 100""
+    Then the cli output should contain:
+    """
+    +----------+--------------+
+    | Name     | Count        |
+    +----------+--------------+
+    | Anagrams | Count: 6.0   |
+    | TC       | Count: 100.0 |
+    +----------+--------------+
+    2 rows in set
+    """
+
+  Scenario: listing projects catalog with empty format
+    Given catalog filled by seeds script
+    When I execute cli "list"
+    Then the cli output should contain:
+    """
+    +----------+------------+--------+-----------------------------------+-----------------------------------------+---------------------+------------------+----------------+-------------------------+----------------------+
+    | Name     | Technology | Active | SCM                               | CI                                      | Unit Tests Coverage | Unit Tests Count | Tests Coverage | Cucumber Tests Coverage | Cucumber Tests Count |
+    +----------+------------+--------+-----------------------------------+-----------------------------------------+---------------------+------------------+----------------+-------------------------+----------------------+
+    | Anagrams | Ruby       | false  | http://github.com/maksar/anagrams | http://travis-ci.org/#!/maksar/anagrams | 100.0               | 6.0              | 100.0          |                         |                      |
+    | TC       | Ruby       | true   | http://github.com/maksar/tc       | http://travis-ci.org/#!/maksar/tc       | 100.0               | 100.0            | 100.0          | 92.68                   | 10.0                 |
+    +----------+------------+--------+-----------------------------------+-----------------------------------------+---------------------+------------------+----------------+-------------------------+----------------------+
+    2 rows in set
+    """

data/features/property_history.feature

@@ -0,0 +1,51 @@
+Feature: Property history
+  In order to view property history
+  As a console user
+  I want to specify property(ies) and see its history
+
+  Background:
+    Given catalog filled by seeds script
+
+  Scenario: trying to list non-existing property
+    When I execute cli "history --pn TC --df ---- "non existing property""
+    Then the cli output should contain "0 rows in set"
+
+  Scenario: listing property history
+    When I execute cli "history --pn TC --df ---- "Unit Tests Count""
+    Then the cli output should contain:
+    """
+    +------+------------------+
+    | Date | Unit Tests Count |
+    +------+------------------+
+    | ---- | 40.0             |
+    | ---- | 45.0             |
+    | ---- | 60.0             |
+    | ---- | 100.0            |
+    +------+------------------+
+    4 rows in set
+    """
+
+  Scenario: listing all properties history
+    When I execute cli "history --pn TC --df ----"
+    Then the cli output should contain:
+    """
+    +------+------------+--------+-----------------------------+-----------------------------------+---------------------+------------------+-------------------------+----------------------+----------------+
+    | Date | Technology | Active | SCM                         | CI                                | Unit Tests Coverage | Unit Tests Count | Cucumber Tests Coverage | Cucumber Tests Count | Tests Coverage |
+    +------+------------+--------+-----------------------------+-----------------------------------+---------------------+------------------+-------------------------+----------------------+----------------+
+    | ---- | Ruby       |        |                             |                                   |                     |                  |                         |                      |                |
+    | ---- |            | true   |                             |                                   |                     |                  |                         |                      |                |
+    | ---- |            |        | http://github.com/maksar/tc |                                   |                     |                  |                         |                      |                |
+    | ---- |            |        |                             | http://travis-ci.org/#!/maksar/tc |                     |                  |                         |                      |                |
+    | ---- |            |        |                             |                                   | 98.55               |                  |                         |                      |                |
+    | ---- |            |        |                             |                                   | 99.0                |                  |                         |                      |                |
+    | ---- |            |        |                             |                                   | 100.0               |                  |                         |                      |                |
+    | ---- |            |        |                             |                                   |                     | 40.0             |                         |                      |                |
+    | ---- |            |        |                             |                                   |                     | 45.0             |                         |                      |                |
+    | ---- |            |        |                             |                                   |                     | 60.0             |                         |                      |                |
+    | ---- |            |        |                             |                                   |                     | 100.0            |                         |                      |                |
+    | ---- |            |        |                             |                                   |                     |                  | 92.68                   |                      |                |
+    | ---- |            |        |                             |                                   |                     |                  |                         | 10.0                 |                |
+    | ---- |            |        |                             |                                   |                     |                  |                         |                      | 100.0          |
+    +------+------------+--------+-----------------------------+-----------------------------------+---------------------+------------------+-------------------------+----------------------+----------------+
+    14 rows in set
+    """

data/features/rake.feature

@@ -0,0 +1,11 @@
+Feature: rake support
+  In order to do technical coordination
+  As a console user
+  I want use rake tasks
+
+  Scenario: View list of rake commands
+    When I run `rake -T`
+    And the output should contain rake command "default" with description "Run Cucumber & RSpec to generate aggregated coverage"
+    And the output should contain rake command "cucumber" with description "Run Cucumber features"
+    And the output should contain rake command "rspec" with description "Run RSpec code examples"
+    And the output should contain rake command "seed" with description "Creates bunch of test data in database"

data/features/seeds.feature

@@ -0,0 +1,9 @@
+Feature: rake seed task
+  In order to do technical coordination
+  As a console user
+  I want use seed rake task
+
+  Scenario: Generate seed data in database
+    Given catalog filled by seeds script
+    When I execute cli "list"
+    Then the cli output should contain "2 rows in set"

data/features/step_definitions/add_project.rb

@@ -0,0 +1,22 @@
+When /^I execute cli "(.*)"$/ do |command|
+  old_stdout = $stdout
+  $stdout = Tempfile.new("")
+
+  TcCli.exec Shellwords.shellwords command
+
+  $stdout.rewind
+  @console = $stdout.readlines.join
+  $stdout = old_stdout
+end
+
+Then /^the cli output should contain "(.*)"$/ do |text|
+  @console.should include text
+end
+
+Then /^the cli output should match \/(.*)\/$/ do |text|
+  @console.should =~ Regexp.new(text)
+end
+
+Then /^the cli output should contain:$/ do |text|
+  @console.should include text
+end

data/features/step_definitions/console_interface.rb

@@ -0,0 +1,7 @@
+Then /^the output have option "(\w+)" with description "(.*)"$/ do |option, description|
+  step "the cli output should match /#{option}\\s+- #{Regexp.quote description}/"
+end
+
+When /^the output should have flag "(\w+)\/(\w+)" with name "(.*)" and description "(.*)"$/ do |short_flag, long_flag, name, description|
+  step "the cli output should match /--#{Regexp.quote short_flag}, --#{Regexp.quote long_flag}=#{Regexp.quote name}[\\s]+- #{Regexp.quote description}/"
+end

data/features/step_definitions/list_projects.rb

@@ -0,0 +1,3 @@
+Given /^no projects in catalog$/ do
+  Project.delete_all
+end

data/features/step_definitions/property_history.rb

@@ -0,0 +1,4 @@
+Given /^catalog filled by seeds script$/ do
+  require_relative '../../db/seed'
+  seed
+end

data/features/step_definitions/rake.rb

@@ -0,0 +1,3 @@
+When /^the output should contain rake command "(\w+)" with description "(.*)"$/ do |name, description|
+  step "the output should match /rake #{Regexp.quote name}[\\s]+\\# #{Regexp.quote description}/"
+end

data/features/support/env.rb

@@ -0,0 +1,9 @@
+ENV['RACK_ENV'] = 'test'
+
+require_relative '../../lib/tc'
+
+require 'tempfile'
+require 'gli_interface'
+
+require 'aruba/cucumber'
+ENV['PATH'] = "#{File.expand_path(File.dirname(__FILE__) + '/../../bin')}#{File::PATH_SEPARATOR}#{ENV['PATH']}"

data/lib/commands/add_metric.rb

@@ -0,0 +1,17 @@
+class AddMetric < Struct.new :project_name, :type, :name
+  def call project = project, metric = metric
+    project.add_metric(metric)
+  end
+
+  def project project_name = project_name
+    Project.find_by(name: project_name)
+  end
+
+  def metric metric_class = metric_class, name = name
+    metric_class.new name: name
+  end
+
+  def metric_class type = type
+    "#{type}Metric".classify.constantize
+  end
+end

data/lib/commands/add_project.rb

@@ -0,0 +1,5 @@
+class AddProject < Struct.new :name
+  def call name = name
+    Project.create(name: name)
+  end
+end