kalibro_client 0.0.1 → 0.0.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (87) hide show
  1. checksums.yaml +4 -4
  2. data/.travis.yml +1 -1
  3. data/features/kalibro_configuration/all.feature +6 -6
  4. data/features/kalibro_configuration/creation.feature +5 -5
  5. data/features/kalibro_configuration/destroy.feature +6 -6
  6. data/features/kalibro_configuration/metric_configurations.feature +4 -4
  7. data/features/{range → kalibro_range}/destroy.feature +2 -2
  8. data/features/{range → kalibro_range}/exists.feature +2 -2
  9. data/features/{range → kalibro_range}/find.feature +2 -2
  10. data/features/{range → kalibro_range}/ranges_of.feature +4 -4
  11. data/features/{range → kalibro_range}/save.feature +2 -2
  12. data/features/kalibro_range/update.feature +54 -0
  13. data/features/metric_configuration/creation.feature +2 -2
  14. data/features/metric_configuration/destroy.feature +2 -2
  15. data/features/metric_configuration/find.feature +2 -2
  16. data/features/metric_configuration/metric_configurations_of.feature +8 -8
  17. data/features/metric_result/descendant_values.feature +2 -2
  18. data/features/metric_result/history_of.feature +2 -2
  19. data/features/metric_result/metric_results_of.feature +2 -2
  20. data/features/module_result/children.feature +2 -2
  21. data/features/module_result/find.feature +2 -2
  22. data/features/module_result/history_of.feature +2 -2
  23. data/features/processing/first_processing_after.feature +2 -2
  24. data/features/processing/first_processing_of.feature +2 -2
  25. data/features/processing/has_processing.feature +2 -2
  26. data/features/processing/has_processing_after.feature +2 -2
  27. data/features/processing/has_processing_before.feature +2 -2
  28. data/features/processing/has_ready_processing.feature +2 -2
  29. data/features/processing/last_processing_before.feature +2 -2
  30. data/features/processing/last_processing_of.feature +2 -2
  31. data/features/processing/last_processing_state_of.feature +2 -2
  32. data/features/processing/last_ready_processing_of.feature +2 -2
  33. data/features/processing/processing_of.feature +4 -4
  34. data/features/processing/processing_with_date_of.feature +4 -4
  35. data/features/project/update.feature +13 -0
  36. data/features/repository/all.feature +1 -1
  37. data/features/repository/cancel_processing.feature +1 -1
  38. data/features/repository/destroy.feature +1 -1
  39. data/features/repository/exists.feature +1 -1
  40. data/features/repository/find.feature +1 -1
  41. data/features/repository/of.feature +1 -1
  42. data/features/repository/process.feature +2 -2
  43. data/features/step_definitions/kalibro_configuration_steps.rb +40 -0
  44. data/features/step_definitions/metric_configuration_steps.rb +9 -9
  45. data/features/step_definitions/module_result_steps.rb +1 -1
  46. data/features/step_definitions/project_steps.rb +12 -0
  47. data/features/step_definitions/range_steps.rb +25 -1
  48. data/features/step_definitions/reading_steps.rb +1 -1
  49. data/features/step_definitions/repository_steps.rb +1 -1
  50. data/lib/kalibro_client/entities/base.rb +53 -19
  51. data/lib/kalibro_client/entities/configurations/base.rb +4 -1
  52. data/lib/kalibro_client/entities/configurations/kalibro_configuration.rb +1 -1
  53. data/lib/kalibro_client/entities/configurations/kalibro_range.rb +8 -8
  54. data/lib/kalibro_client/entities/configurations/metric_configuration.rb +7 -5
  55. data/lib/kalibro_client/entities/configurations/reading.rb +4 -4
  56. data/lib/kalibro_client/entities/configurations/reading_group.rb +4 -0
  57. data/lib/kalibro_client/entities/processor/base.rb +2 -1
  58. data/lib/kalibro_client/entities/processor/kalibro_module.rb +1 -0
  59. data/lib/kalibro_client/entities/processor/metric_collector_details.rb +7 -2
  60. data/lib/kalibro_client/entities/processor/metric_result.rb +9 -10
  61. data/lib/kalibro_client/entities/processor/module_result.rb +10 -2
  62. data/lib/kalibro_client/entities/processor/processing.rb +26 -10
  63. data/lib/kalibro_client/entities/processor/project.rb +4 -0
  64. data/lib/kalibro_client/entities/processor/repository.rb +63 -4
  65. data/lib/kalibro_client/helpers/date_attributes.rb +11 -0
  66. data/lib/kalibro_client/helpers/request_methods.rb +9 -0
  67. data/lib/kalibro_client/version.rb +1 -1
  68. data/spec/entities/base_spec.rb +106 -24
  69. data/spec/entities/configurations/kalibro_configuration_spec.rb +8 -8
  70. data/spec/entities/configurations/kalibro_range_spec.rb +18 -24
  71. data/spec/entities/configurations/metric_configuration_spec.rb +22 -23
  72. data/spec/entities/configurations/reading_group_spec.rb +27 -0
  73. data/spec/entities/configurations/reading_spec.rb +15 -7
  74. data/spec/entities/processor/metric_collector_details_spec.rb +19 -7
  75. data/spec/entities/processor/metric_result_spec.rb +40 -54
  76. data/spec/entities/processor/module_result_spec.rb +52 -3
  77. data/spec/entities/processor/processing_spec.rb +35 -92
  78. data/spec/entities/processor/project_spec.rb +52 -5
  79. data/spec/entities/processor/repository_spec.rb +255 -5
  80. data/spec/factories/kalibro_configurations.rb +3 -3
  81. data/spec/factories/kalibro_ranges.rb +9 -3
  82. data/spec/factories/metrics.rb +1 -1
  83. data/spec/factories/readings.rb +1 -1
  84. data/spec/factories/repositories.rb +1 -1
  85. data/spec/helpers/date_attributes_spec.rb +30 -0
  86. metadata +21 -14
  87. data/features/step_definitions/configuration_steps.rb +0 -40
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 5e4067befa110600678be73bc51ab56375c2a025
4
- data.tar.gz: 181171ac9b1ded69c65085ff41d610a7fa8a6774
3
+ metadata.gz: 8e730f4e5ad4962f11f45d31b13285b451613196
4
+ data.tar.gz: 5ee7728dfa0e8b72ad71c00cc3e25ec17663adb5
5
5
  SHA512:
6
- metadata.gz: a0a704b44944cb6f4a1eeea21e5910c93fe2d7c05640ecac76c54bb3ba2c7a013b198c2d17e75e88b43f5547eff06963a03567fbdadf25da2292ce979a4b18d6
7
- data.tar.gz: d0c26e9940453d04652eda53d7c8df2c7aca9203e18b3ee6fba1f68e217e6055af1063f2078e7875272af431b5ffbe6d08d1792a2c68d35f13a2e4b8b00ee695
6
+ metadata.gz: e35efd43bddb4bffbcb0b90e16723457507a7bf8723fd3ab305b37ac6636cd1f41ddd5cb05985ac9c02947ee8a5f33d9f12059ad1b28bef8049eb4270a350457
7
+ data.tar.gz: 6e2a7f01e43a5932c9fe583a5fcbb4eb9d4e51a59ed0feff51ab6c4a94dfece0463018701bcb669e477891c7b2c6f16f58efb0c89e78570592e14c6a151f196a
data/.travis.yml CHANGED
@@ -6,7 +6,7 @@ addons:
6
6
  postgresql: "9.3"
7
7
 
8
8
  before_script:
9
- - git clone https://gist.github.com/6179925.git -b v2.0.beta5 kalibro_install
9
+ - git clone https://gist.github.com/6179925.git -b v2.0.rc2 kalibro_install
10
10
  - pushd kalibro_install
11
11
  # Remove bugged libzmq3 package, see https://github.com/travis-ci/travis-ci/issues/982 and https://github.com/travis-ci/travis-ci/issues/1715 for details
12
12
  - sudo apt-get remove libzmq3
data/features/kalibro_configuration/all.feature CHANGED
@@ -1,10 +1,10 @@
1
1
  Feature: All
2
- In order to be able to have configurations
2
+ In order to be able to have kalibro configurations
3
3
  As a developer
4
- I want to get all the available configurations
4
+ I want to get all the available kalibro configurations
5
5
 
6
6
  @kalibro_configuration_restart
7
- Scenario: one configuration
8
- Given I have a configuration with name "Java"
9
- When I get all the configurations
10
- Then I should get a list with the given configuration
7
+ Scenario: one kalibro configuration
8
+ Given I have a kalibro configuration with name "Java"
9
+ When I get all the kalibro configurations
10
+ Then I should get a list with the given kalibro configuration
data/features/kalibro_configuration/creation.feature CHANGED
@@ -1,9 +1,9 @@
1
1
  Feature: Creation
2
- In order to be able to have configurations
2
+ In order to be able to have kalibro configurations
3
3
  As a developer
4
- I want to create configurations
4
+ I want to create kalibro configurations
5
5
 
6
6
  @kalibro_configuration_restart
7
- Scenario: create a valid configuration
8
- When I create the configuration with name "Kalibro"
9
- Then the configuration should exist
7
+ Scenario: create a valid kalibro configuration
8
+ When I create the kalibro configuration with name "Kalibro"
9
+ Then the kalibro configuration should exist
data/features/kalibro_configuration/destroy.feature CHANGED
@@ -1,10 +1,10 @@
1
1
  Feature: Destroy
2
- In order to manipulate configurations
2
+ In order to manipulate kalibro configurations
3
3
  As a developer
4
- I want to destroy a given configuration
4
+ I want to destroy a given kalibro configuration
5
5
 
6
6
  @kalibro_configuration_restart
7
- Scenario: destroying a configuration
8
- Given I have a configuration with name "Java"
9
- When I destroy the configuration
10
- Then the configuration should no longer exist
7
+ Scenario: destroying a kalibro configuration
8
+ Given I have a kalibro configuration with name "Java"
9
+ When I destroy the kalibro configuration
10
+ Then the kalibro configuration should no longer exist
data/features/kalibro_configuration/metric_configurations.feature CHANGED
@@ -1,12 +1,12 @@
1
1
  Feature: Metric Configurations
2
2
  In order to see the metric configurations
3
3
  As a developer
4
- I want to list all the metric configurations of a configuration
4
+ I want to list all the metric configurations of a kalibro configuration
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: one metric configuration
8
- Given I have a configuration with name "Java"
9
- And the configuration has a metric configuration
10
- When I list all the metric configurations of the configuration
8
+ Given I have a kalibro configuration with name "Java"
9
+ And the kalibro configuration has a metric configuration
10
+ When I list all the metric configurations of the kalibro configuration
11
11
  Then I should get a list with the given metric configuration
12
12
 
data/features/{range → kalibro_range}/destroy.feature RENAMED
@@ -5,9 +5,9 @@ Feature: Destroy
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: destroying an existing range
8
- Given I have a configuration with name "Java"
8
+ Given I have a kalibro configuration with name "Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a metric configuration within the given configuration
10
+ And I have a metric configuration within the given kalibro configuration
11
11
  And I have a reading within the given reading group
12
12
  And I have a range within the given reading
13
13
  When I destroy the range
data/features/{range → kalibro_range}/exists.feature RENAMED
@@ -5,9 +5,9 @@ Feature: Exists
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: find a valid range
8
- Given I have a configuration with name "Java"
8
+ Given I have a kalibro configuration with name "Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a metric configuration within the given configuration
10
+ And I have a metric configuration within the given kalibro configuration
11
11
  And I have a reading within the given reading group
12
12
  And I have a range within the given reading
13
13
  Then the range should exist
data/features/{range → kalibro_range}/find.feature RENAMED
@@ -5,9 +5,9 @@ Feature: Find
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: find a valid range
8
- Given I have a configuration with name "Java"
8
+ Given I have a kalibro configuration with name "Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a metric configuration within the given configuration
10
+ And I have a metric configuration within the given kalibro configuration
11
11
  And I have a reading within the given reading group
12
12
  And I have a range within the given reading
13
13
  When I search a range with the same id of the given range
data/features/{range → kalibro_range}/ranges_of.feature RENAMED
@@ -5,17 +5,17 @@ Feature: Range of
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: With an inexistent range
8
- Given I have a configuration with name "Java"
8
+ Given I have a kalibro configuration with name "Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a metric configuration within the given configuration
10
+ And I have a metric configuration within the given kalibro configuration
11
11
  When I ask ranges of the given metric configuration
12
12
  Then I should get an empty list
13
13
 
14
14
  @kalibro_configuration_restart
15
15
  Scenario: With an existing range
16
- Given I have a configuration with name "Java"
16
+ Given I have a kalibro configuration with name "Java"
17
17
  And I have a reading group with name "Group"
18
- And I have a metric configuration within the given configuration
18
+ And I have a metric configuration within the given kalibro configuration
19
19
  And I have a reading within the given reading group
20
20
  And I have a range within the given reading
21
21
  When I ask ranges of the given metric configuration
data/features/{range → kalibro_range}/save.feature RENAMED
@@ -5,9 +5,9 @@ Feature: Save
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: When there is a metric configuration
8
- Given I have a configuration with name "Java"
8
+ Given I have a kalibro configuration with name "Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a metric configuration within the given configuration
10
+ And I have a metric configuration within the given kalibro configuration
11
11
  And I have a reading within the given reading group
12
12
  And I have an unsaved range within the given reading
13
13
  When I ask to save the given range
data/features/kalibro_range/update.feature ADDED
@@ -0,0 +1,54 @@
1
+ Feature: Update
2
+ In order to be able to change kalibro ranges
3
+ As a developer
4
+ I want to update a kalibro range
5
+
6
+ @kalibro_configuration_restart
7
+ Scenario: When the update is successful
8
+ Given I have a kalibro configuration with name "Java"
9
+ And I have a reading group with name "Group"
10
+ And I have a metric configuration within the given kalibro configuration
11
+ And I have a reading within the given reading group
12
+ And I have a range within the given reading
13
+ When I change the "beginning" to "-250"
14
+ And I change the "end" to "250"
15
+ And I change the "comments" to "my new range"
16
+ And I ask to update the given range
17
+ Then I should not receive errors
18
+
19
+ @kalibro_configuration_restart
20
+ Scenario: When trying to update beginning with an invalid value
21
+ Given I have a kalibro configuration with name "Java"
22
+ And I have a reading group with name "Group"
23
+ And I have a metric configuration within the given kalibro configuration
24
+ And I have a reading within the given reading group
25
+ And I have a range within the given reading
26
+ When I change the "beginning" to "bla"
27
+ And I ask to update the given range
28
+ Then I should get the error "Beginning is not a number"
29
+
30
+ @kalibro_configuration_restart
31
+ Scenario: When trying to set the beginning with a number greater than the end
32
+ Given I have a kalibro configuration with name "Java"
33
+ And I have a reading group with name "Group"
34
+ And I have a metric configuration within the given kalibro configuration
35
+ And I have a reading within the given reading group
36
+ And I have a range within the given reading
37
+ When I change the "beginning" to "INF"
38
+ And I change the "end" to "-INF"
39
+ And I ask to update the given range
40
+ Then I should get the error "End The End value should be greater than the Beginning value."
41
+
42
+ @kalibro_configuration_restart
43
+ Scenario: When trying to set the beginning with a number greater than end
44
+ Given I have a kalibro configuration with name "Java"
45
+ And I have a reading group with name "Group"
46
+ And I have a metric configuration within the given kalibro configuration
47
+ And I have a reading within the given reading group
48
+ And I have a range within the given reading
49
+ And I have another range within the given reading
50
+ When I change the "beginning" to "0"
51
+ And I ask to update the given range
52
+ Then I should get the error "Beginning Should be unique within a Metric Configuration"
53
+ And I should get the error "Beginning There is already a KalibroRange within these boundaries! Please, choose another interval."
54
+
data/features/metric_configuration/creation.feature CHANGED
@@ -5,7 +5,7 @@ Feature: Create
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: creating a metric configuration
8
- Given I have a configuration with name "Kalibro for Java"
8
+ Given I have a kalibro configuration with name "Kalibro for Java"
9
9
  And I have a reading group with name "Group"
10
- When I have a loc configuration within the given configuration
10
+ When I have a loc configuration within the given kalibro configuration
11
11
  Then the metric configuration should exist
data/features/metric_configuration/destroy.feature CHANGED
@@ -5,8 +5,8 @@ Feature: Destroy
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: destroying a metric configuration
8
- Given I have a configuration with name "Kalibro for Java"
8
+ Given I have a kalibro configuration with name "Kalibro for Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a loc configuration within the given configuration
10
+ And I have a loc configuration within the given kalibro configuration
11
11
  When I destroy the metric configuration
12
12
  Then the metric configuration should no longer exist
data/features/metric_configuration/find.feature CHANGED
@@ -5,9 +5,9 @@ Feature: Find
5
5
 
6
6
  @kalibro_configuration_restart
7
7
  Scenario: find a valid metric configuration
8
- Given I have a configuration with name "Kalibro for Java"
8
+ Given I have a kalibro configuration with name "Kalibro for Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a loc configuration within the given configuration
10
+ And I have a loc configuration within the given kalibro configuration
11
11
  When I search a metric configuration with the same id of the given metric configuration
12
12
  Then it should return the same metric configuration as the given one
13
13
 
data/features/metric_configuration/metric_configurations_of.feature CHANGED
@@ -1,18 +1,18 @@
1
1
  Feature: MetricConfigurationsOf
2
2
  In order to be able to have configurations
3
3
  As a developer
4
- I want to get all metric_configurations of a configuration
4
+ I want to get all metric_configurations of a kalibro configuration
5
5
 
6
6
  @kalibro_configuration_restart
7
- Scenario: get a list of all metric configurations of some configuration
8
- Given I have a configuration with name "Kalibro for Java"
7
+ Scenario: get a list of all metric configurations of some kalibro configuration
8
+ Given I have a kalibro configuration with name "Kalibro for Java"
9
9
  And I have a reading group with name "Group"
10
- And I have a metric configuration within the given configuration
11
- When I request all metric configurations of the given configuration
10
+ And I have a metric configuration within the given kalibro configuration
11
+ When I request all metric configurations of the given kalibro configuration
12
12
  Then I should get a list of its metric configurations
13
13
 
14
14
  @kalibro_configuration_restart
15
- Scenario: get an empty list for a configuration without metric configurations
16
- Given I have a configuration with name "Kalibro for Java"
17
- When I request all metric configurations of the given configuration
15
+ Scenario: get an empty list for a kalibro configuration without metric configurations
16
+ Given I have a kalibro configuration with name "Kalibro for Java"
17
+ When I request all metric configurations of the given kalibro configuration
18
18
  Then I should get an empty list of metric configurations
data/features/metric_result/descendant_values.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Descendant values
6
6
  @kalibro_configuration_restart @kalibro_processor_restart
7
7
  Scenario: when there is a metric result
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/metric_result/history_of.feature CHANGED
@@ -6,10 +6,10 @@ Feature: history of
6
6
  @kalibro_configuration_restart @kalibro_processor_restart
7
7
  Scenario: when there is a metric result
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
11
  And I have a metric with name "Lines of Code"
12
- And I have a loc configuration within the given configuration
12
+ And I have a loc configuration within the given kalibro configuration
13
13
  And the given project has the following Repositories:
14
14
  | name | scm_type | address |
15
15
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/metric_result/metric_results_of.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Metric results of
6
6
  @kalibro_configuration_restart @kalibro_processor_restart
7
7
  Scenario: when there is a metric result
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/module_result/children.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Children
6
6
  @kalibro_configuration_restart @kalibro_processor_restart
7
7
  Scenario: find a valid module result
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/module_result/find.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Find
6
6
  @kalibro_configuration_restart @kalibro_processor_restart
7
7
  Scenario: find a valid module result
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/module_result/history_of.feature CHANGED
@@ -6,9 +6,9 @@ Feature: /history of
6
6
  @kalibro_configuration_restart @kalibro_processor_restart
7
7
  Scenario: get the history of a module result
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/processing/first_processing_after.feature CHANGED
@@ -6,9 +6,9 @@ Feature: First processing after
6
6
  @kalibro_processor_restart @kalibro_configuration_restart
7
7
  Scenario: With one repository just after starting to process
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/processing/first_processing_of.feature CHANGED
@@ -6,9 +6,9 @@ Feature: First processing of
6
6
  @kalibro_processor_restart @kalibro_configuration_restart
7
7
  Scenario: With one repository just after starting to process
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/processing/has_processing.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Has processing
6
6
  @kalibro_processor_restart @kalibro_configuration_restart
7
7
  Scenario: With one repository after process
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/processing/has_processing_after.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Has processing after
6
6
  @kalibro_processor_restart @kalibro_configuration_restart
7
7
  Scenario: With one repository just after starting to process
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/processing/has_processing_before.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Has processing before
6
6
  @kalibro_processor_restart @kalibro_configuration_restart
7
7
  Scenario: With one repository just after starting to process
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |
data/features/processing/has_ready_processing.feature CHANGED
@@ -6,9 +6,9 @@ Feature: Has ready processing
6
6
  @kalibro_processor_restart @kalibro_configuration_restart
7
7
  Scenario: With one repository just after starting to process
8
8
  Given I have a project with name "Kalibro"
9
- And I have a configuration with name "Java"
9
+ And I have a kalibro configuration with name "Java"
10
10
  And I have a reading group with name "Group"
11
- And I have a loc configuration within the given configuration
11
+ And I have a loc configuration within the given kalibro configuration
12
12
  And the given project has the following Repositories:
13
13
  | name | scm_type | address |
14
14
  | Kalibro | GIT | https://git.gitorious.org/sbking/sbking.git |