RubyGems - kalibro_client - Versions diffs - 0.0.1 - Mend

kalibro_client 0.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (171) hide show

checksums.yaml +7 -0
data/.gitignore +19 -0
data/.rspec +2 -0
data/.ruby-gemset +1 -0
data/.ruby-version +1 -0
data/.travis.yml +27 -0
data/AUTHORS +4 -0
data/COPYING +674 -0
data/COPYING.LESSER +165 -0
data/Gemfile +4 -0
data/README.md +77 -0
data/Rakefile +6 -0
data/cucumber.yml +1 -0
data/features/kalibro_configuration/all.feature +10 -0
data/features/kalibro_configuration/creation.feature +9 -0
data/features/kalibro_configuration/destroy.feature +10 -0
data/features/kalibro_configuration/metric_configurations.feature +12 -0
data/features/metric_collector_details/all_names.feature +8 -0
data/features/metric_collector_details/find_by_name.feature +12 -0
data/features/metric_configuration/creation.feature +11 -0
data/features/metric_configuration/destroy.feature +12 -0
data/features/metric_configuration/find.feature +18 -0
data/features/metric_configuration/metric_configurations_of.feature +18 -0
data/features/metric_result/descendant_values.feature +19 -0
data/features/metric_result/history_of.feature +20 -0
data/features/metric_result/metric_results_of.feature +20 -0
data/features/module_result/children.feature +19 -0
data/features/module_result/find.feature +22 -0
data/features/module_result/history_of.feature +19 -0
data/features/processing/first_processing_after.feature +18 -0
data/features/processing/first_processing_of.feature +18 -0
data/features/processing/has_processing.feature +18 -0
data/features/processing/has_processing_after.feature +18 -0
data/features/processing/has_processing_before.feature +18 -0
data/features/processing/has_ready_processing.feature +18 -0
data/features/processing/last_processing_before.feature +18 -0
data/features/processing/last_processing_of.feature +18 -0
data/features/processing/last_processing_state_of.feature +18 -0
data/features/processing/last_ready_processing_of.feature +19 -0
data/features/processing/processing_of.feature +32 -0
data/features/processing/processing_with_date_of.feature +32 -0
data/features/project/all.feature +10 -0
data/features/project/creation.feature +9 -0
data/features/project/destroy.feature +10 -0
data/features/project/exists.feature +9 -0
data/features/project/find.feature +10 -0
data/features/range/destroy.feature +14 -0
data/features/range/exists.feature +13 -0
data/features/range/find.feature +14 -0
data/features/range/ranges_of.feature +22 -0
data/features/range/save.feature +14 -0
data/features/reading/destroy.feature +13 -0
data/features/reading/exists.feature +13 -0
data/features/reading/find.feature +11 -0
data/features/reading/readings_of.feature +11 -0
data/features/reading_group/all.feature +10 -0
data/features/reading_group/creation.feature +9 -0
data/features/reading_group/destroy.feature +11 -0
data/features/repository/all.feature +14 -0
data/features/repository/cancel_processing.feature +14 -0
data/features/repository/destroy.feature +14 -0
data/features/repository/exists.feature +14 -0
data/features/repository/find.feature +14 -0
data/features/repository/of.feature +15 -0
data/features/repository/process.feature +16 -0
data/features/repository/types.feature +8 -0
data/features/step_definitions/configuration_steps.rb +40 -0
data/features/step_definitions/metric_collector_details_steps.rb +28 -0
data/features/step_definitions/metric_configuration_steps.rb +61 -0
data/features/step_definitions/metric_result_steps.rb +33 -0
data/features/step_definitions/metric_steps.rb +3 -0
data/features/step_definitions/module_result_steps.rb +46 -0
data/features/step_definitions/processing_steps.rb +95 -0
data/features/step_definitions/project_steps.rb +48 -0
data/features/step_definitions/range_steps.rb +72 -0
data/features/step_definitions/reading_group_steps.rb +36 -0
data/features/step_definitions/reading_steps.rb +47 -0
data/features/step_definitions/repository_steps.rb +71 -0
data/features/support/env.rb +25 -0
data/features/support/kalibro_cucumber_helpers.yml.sample +3 -0
data/kalibro_client.gemspec +49 -0
data/lib/kalibro_client.rb +62 -0
data/lib/kalibro_client/entities.rb +40 -0
data/lib/kalibro_client/entities/base.rb +196 -0
data/lib/kalibro_client/entities/configurations/base.rb +13 -0
data/lib/kalibro_client/entities/configurations/kalibro_configuration.rb +37 -0
data/lib/kalibro_client/entities/configurations/kalibro_range.rb +77 -0
data/lib/kalibro_client/entities/configurations/metric_configuration.rb +93 -0
data/lib/kalibro_client/entities/configurations/range_snapshot.rb +37 -0
data/lib/kalibro_client/entities/configurations/reading.rb +56 -0
data/lib/kalibro_client/entities/configurations/reading_group.rb +34 -0
data/lib/kalibro_client/entities/miscellaneous/base.rb +57 -0
data/lib/kalibro_client/entities/miscellaneous/compound_metric.rb +21 -0
data/lib/kalibro_client/entities/miscellaneous/date_metric_result.rb +14 -0
data/lib/kalibro_client/entities/miscellaneous/date_module_result.rb +18 -0
data/lib/kalibro_client/entities/miscellaneous/granularity.rb +54 -0
data/lib/kalibro_client/entities/miscellaneous/metric.rb +19 -0
data/lib/kalibro_client/entities/miscellaneous/native_metric.rb +24 -0
data/lib/kalibro_client/entities/processor/base.rb +16 -0
data/lib/kalibro_client/entities/processor/kalibro_module.rb +27 -0
data/lib/kalibro_client/entities/processor/metric_collector_details.rb +53 -0
data/lib/kalibro_client/entities/processor/metric_result.rb +79 -0
data/lib/kalibro_client/entities/processor/module_result.rb +82 -0
data/lib/kalibro_client/entities/processor/process_time.rb +31 -0
data/lib/kalibro_client/entities/processor/processing.rb +109 -0
data/lib/kalibro_client/entities/processor/project.rb +34 -0
data/lib/kalibro_client/entities/processor/repository.rb +75 -0
data/lib/kalibro_client/errors.rb +18 -0
data/lib/kalibro_client/errors/record_not_found.rb +22 -0
data/lib/kalibro_client/errors/standard.rb +24 -0
data/lib/kalibro_client/helpers/aggregation_options.rb +25 -0
data/lib/kalibro_client/helpers/hash_converters.rb +48 -0
data/lib/kalibro_client/helpers/request_methods.rb +55 -0
data/lib/kalibro_client/helpers/xml_converters.rb +20 -0
data/lib/kalibro_client/kalibro_cucumber_helpers.rb +60 -0
data/lib/kalibro_client/kalibro_cucumber_helpers/configuration.rb +30 -0
data/lib/kalibro_client/kalibro_cucumber_helpers/hooks.rb +25 -0
data/lib/kalibro_client/version.rb +19 -0
data/lib/rake/test_task.rb +57 -0
data/spec/entities/base_spec.rb +313 -0
data/spec/entities/configurations/base_spec.rb +26 -0
data/spec/entities/configurations/kalibro_configuration_spec.rb +91 -0
data/spec/entities/configurations/kalibro_range_spec.rb +174 -0
data/spec/entities/configurations/metric_configuration_spec.rb +230 -0
data/spec/entities/configurations/range_snapshot_spec.rb +50 -0
data/spec/entities/configurations/reading_group_spec.rb +60 -0
data/spec/entities/configurations/reading_spec.rb +87 -0
data/spec/entities/miscellaneous/base_spec.rb +49 -0
data/spec/entities/miscellaneous/compound_metric_spec.rb +36 -0
data/spec/entities/miscellaneous/date_metric_result_spec.rb +4 -0
data/spec/entities/miscellaneous/date_module_result_spec.rb +0 -0
data/spec/entities/miscellaneous/granularity_spec.rb +96 -0
data/spec/entities/miscellaneous/metric_spec.rb +15 -0
data/spec/entities/miscellaneous/native_metric_spec.rb +37 -0
data/spec/entities/processor/base_spec.rb +26 -0
data/spec/entities/processor/metric_collector_details_spec.rb +146 -0
data/spec/entities/processor/metric_result_spec.rb +209 -0
data/spec/entities/processor/module_result_spec.rb +178 -0
data/spec/entities/processor/process_time_spec.rb +33 -0
data/spec/entities/processor/processing_spec.rb +333 -0
data/spec/entities/processor/project_spec.rb +68 -0
data/spec/entities/processor/repository_spec.rb +140 -0
data/spec/factories/date_metric_results.rb +30 -0
data/spec/factories/date_module_results.rb +24 -0
data/spec/factories/granularities.rb +23 -0
data/spec/factories/kalibro_configurations.rb +34 -0
data/spec/factories/kalibro_module.rb +28 -0
data/spec/factories/kalibro_ranges.rb +40 -0
data/spec/factories/metric_collector_details.rb +30 -0
data/spec/factories/metric_configurations.rb +31 -0
data/spec/factories/metric_results.rb +24 -0
data/spec/factories/metrics.rb +48 -0
data/spec/factories/models.rb +23 -0
data/spec/factories/module_results.rb +43 -0
data/spec/factories/process_times.rb +27 -0
data/spec/factories/processings.rb +24 -0
data/spec/factories/projects.rb +35 -0
data/spec/factories/ranges_snapshot.rb +26 -0
data/spec/factories/reading_groups.rb +28 -0
data/spec/factories/readings.rb +30 -0
data/spec/factories/repositories.rb +39 -0
data/spec/helpers/aggregation_options_spec.rb +31 -0
data/spec/helpers/hash_converters_spec.rb +111 -0
data/spec/helpers/xml_converters_spec.rb +64 -0
data/spec/kalibro_entities_spec.rb +112 -0
data/spec/savon/fixtures/config.yml +2 -0
data/spec/savon/fixtures/invalid_config.yml +2 -0
data/spec/savon/fixtures/project/does_not_exists.xml +1 -0
data/spec/savon/savon_test_helper.rb +14 -0
data/spec/spec_helper.rb +111 -0
metadata +479 -0

data/features/module_result/children.feature ADDED

@@ -0,0 +1,19 @@
+Feature: Children
+  In order to be able to have the children of a module result
+  As a developer
+  I want to find children module results
+  @kalibro_configuration_restart @kalibro_processor_restart
+  Scenario: find a valid module result
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |              address                        |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up for a ready processing
+    When I ask for the children of the processing root module result
+    Then I should get a list with the children module results
+    And The first children should have a module

data/features/module_result/find.feature ADDED

@@ -0,0 +1,22 @@
+Feature: Find
+  In order to be able to have module result
+  As a developer
+  I want to find module results
+  @kalibro_configuration_restart @kalibro_processor_restart
+  Scenario: find a valid module result
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |              address                        |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    When I call the process method for the given repository
+    And I wait up for a ready processing
+    And I get the module result of the processing
+    Then I should get a module_result
+  Scenario: get a module result by inexistent name
+    When I ask for an inexistent module result
+    Then I should get an error

data/features/module_result/history_of.feature ADDED

@@ -0,0 +1,19 @@
+Feature: /history of
+  In order to be able to have the history of a module result
+  As a developer
+  I want to get the history of module results
+  @kalibro_configuration_restart @kalibro_processor_restart
+  Scenario: get the history of a module result
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |              address                        |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up for a ready processing
+    And I get the module result of the processing
+    When I ask for the history of the given module result
+    Then I should get a list with date module results

data/features/processing/first_processing_after.feature ADDED

@@ -0,0 +1,18 @@
+Feature: First processing after
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to retrieve the first processing after a given date
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the first_processing_after method for the given repository and yesterday's date
+    Then I should get a Processing

data/features/processing/first_processing_of.feature ADDED

@@ -0,0 +1,18 @@
+Feature: First processing of
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to retrieve the first processing
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the first_processing_of method for the given repository
+    Then I should get a Processing

data/features/processing/has_processing.feature ADDED

@@ -0,0 +1,18 @@
+Feature: Has processing
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to check if a repository has processings
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository after process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the has_processing for the given repository
+    Then I should get true

data/features/processing/has_processing_after.feature ADDED

@@ -0,0 +1,18 @@
+Feature: Has processing after
+  In order to be able to retrieve processing results from a given date
+  As a developer
+  I want to be able to check if a repository has processings after it
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the has_processing_after for the given repository with yerterday's date
+    Then I should get true

data/features/processing/has_processing_before.feature ADDED

@@ -0,0 +1,18 @@
+Feature: Has processing before
+  In order to be able to retrieve processing results from a given date
+  As a developer
+  I want to be able to check if a repository has processings before it
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the has_processing_before for the given repository with tomorrows's date
+    Then I should get true

data/features/processing/has_ready_processing.feature ADDED

@@ -0,0 +1,18 @@
+Feature: Has ready processing
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to check if a repository has ready processings
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the has_ready_processing for the given repository
+    Then I should get false

data/features/processing/last_processing_before.feature ADDED

@@ -0,0 +1,18 @@
+Feature: Last processing before
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to retrieve the last processing before a given date
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the last_processing_before method for the given repository and tomorrow's date
+    Then I should get a Processing

data/features/processing/last_processing_of.feature ADDED

@@ -0,0 +1,18 @@
+Feature: Last processing of
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to retrieve the last processing
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the last_processing_of method for the given repository
+    Then I should get a Processing

data/features/processing/last_processing_state_of.feature ADDED

@@ -0,0 +1,18 @@
+Feature: Last processing state of
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to check the last processing status
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the last_processing_state_of method for the given repository
+    Then I should get "PREPARING"

data/features/processing/last_ready_processing_of.feature ADDED

@@ -0,0 +1,19 @@
+Feature: Last ready processing of
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to check the last ready processing
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after with ready processing
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up for a ready processing
+    When I call the last_ready_processing_of method for the given repository
+    Then I should get a Processing
+    And this processing should have process times

data/features/processing/processing_of.feature ADDED

@@ -0,0 +1,32 @@
+Feature: Processing of
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to retrieve the processing
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the processing_of method for the given repository
+    Then I should get a Processing with state "PREPARING"
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after with ready processing
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up for a ready processing
+    When I call the processing_of method for the given repository
+    Then I should get a Processing with state "READY"

data/features/processing/processing_with_date_of.feature ADDED

@@ -0,0 +1,32 @@
+Feature: Processing with date of
+  In order to be able to retrieve processing results
+  As a developer
+  I want to be able to retrieve the processing for a given date
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process and tomorrow's date
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the processing_with_date_of method for the given repository and tomorrow's date
+    Then I should get a Processing
+  @kalibro_processor_restart @kalibro_configuration_restart
+  Scenario: With one repository just after starting to process and yesterday's date
+    Given I have a project with name "Kalibro"
+    And I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a loc configuration within the given configuration
+    And the given project has the following Repositories:
+      |   name    | scm_type |                  address                    |
+      |  Kalibro  |    GIT   | https://git.gitorious.org/sbking/sbking.git |
+    And I call the process method for the given repository
+    And I wait up to 1 seconds
+    When I call the processing_with_date_of method for the given repository and yesterday's date
+    Then I should get a Processing

data/features/project/all.feature ADDED

@@ -0,0 +1,10 @@
+Feature: All
+  In order to be able to have projects
+  As a developer
+  I want to get all the available projects
+  @kalibro_processor_restart
+  Scenario: one project
+    Given I have a project with name "Kalibro"
+    When I ask for all the projects
+    Then I should get a list with the given project

data/features/project/creation.feature ADDED

@@ -0,0 +1,9 @@
+Feature: Creation
+  In order to be able to have projects
+  As a developer
+  I want to create projects
+  @kalibro_processor_restart
+  Scenario: create a valid project
+    When I create the project with name "Kalibro"
+    Then the project should exist

data/features/project/destroy.feature ADDED

@@ -0,0 +1,10 @@
+Feature: Destroy
+  In order to be able to have projects
+  As a developer
+  I want to detroy projects
+  @kalibro_processor_restart
+  Scenario: destroy an existing project
+    Given I have a project with name "Kalibro"
+    When I destroy the project with the same id of the given project
+    Then the project should no longer exist

data/features/project/exists.feature ADDED

@@ -0,0 +1,9 @@
+Feature: Exists
+  In order to be able to have projects
+  As a developer
+  I want to find wich projects exists
+  @kalibro_processor_restart
+  Scenario: check a valid project
+    Given I have a project with name "Kalibro"
+    Then the project should exist

data/features/project/find.feature ADDED

@@ -0,0 +1,10 @@
+Feature: Find
+  In order to be able to have projects
+  As a developer
+  I want to find projects
+  @kalibro_processor_restart
+  Scenario: find a valid project
+    Given I have a project with name "Kalibro"
+    When I search a project with the same id of the given project
+    Then it should return the same project as the given one

data/features/range/destroy.feature ADDED

@@ -0,0 +1,14 @@
+Feature: Destroy
+  In order to be able to have ranges
+  As a developer
+  I want to destroy ranges
+  @kalibro_configuration_restart
+  Scenario: destroying an existing range
+    Given I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a metric configuration within the given configuration
+    And I have a reading within the given reading group
+    And I have a range within the given reading
+    When I destroy the range
+    Then the range should no longer exist

data/features/range/exists.feature ADDED

@@ -0,0 +1,13 @@
+Feature: Exists
+  In order to be able to have ranges
+  As a developer
+  I want to find which range exists
+@kalibro_configuration_restart
+Scenario: find a valid range
+    Given I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a metric configuration within the given configuration
+    And I have a reading within the given reading group
+    And I have a range within the given reading
+    Then the range should exist

data/features/range/find.feature ADDED

@@ -0,0 +1,14 @@
+Feature: Find
+  In order to be able to have ranges
+  As a developer
+  I want to find ranges
+@kalibro_configuration_restart
+Scenario: find a valid range
+    Given I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a metric configuration within the given configuration
+    And I have a reading within the given reading group
+    And I have a range within the given reading
+    When I search a range with the same id of the given range
+    Then it should return the same range as the given one

data/features/range/ranges_of.feature ADDED

@@ -0,0 +1,22 @@
+Feature: Range of
+  In order to be able to get all the ranges of a metric configuration
+  As a developer
+  I want to see all the ranges of the given metric configuration
+  @kalibro_configuration_restart
+  Scenario: With an inexistent range
+    Given I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a metric configuration within the given configuration
+    When I ask ranges of the given metric configuration
+    Then I should get an empty list
+  @kalibro_configuration_restart
+  Scenario: With an existing range
+    Given I have a configuration with name "Java"
+    And I have a reading group with name "Group"
+    And I have a metric configuration within the given configuration
+    And I have a reading within the given reading group
+    And I have a range within the given reading
+    When I ask ranges of the given metric configuration
+    Then I should get a list with the given range