earth 0.11.18 → 0.11.19
Sign up to get free protection for your applications and to get access to all the features.
- data/DEVELOPERS.markdown +19 -0
- data/Rakefile +2 -25
- data/errata/electricity/electric_market/nrel_errata.csv +1 -0
- data/errata/electricity/electric_utility/eia_errata.csv +1 -0
- data/lib/earth.rb +3 -1
- data/lib/earth/air/flight_segment.rb +1 -0
- data/lib/earth/air/flight_segment/data_miner.rb +1 -2
- data/lib/earth/electricity.rb +3 -0
- data/lib/earth/electricity/electric_market.rb +12 -0
- data/lib/earth/electricity/electric_market/data_miner.rb +21 -0
- data/lib/earth/electricity/electric_utility.rb +24 -0
- data/lib/earth/electricity/electric_utility/data_miner.rb +26 -0
- data/lib/earth/electricity/green_button_adoption.rb +20 -0
- data/lib/earth/electricity/green_button_adoption/data_miner.rb +19 -0
- data/lib/earth/locality/zip_code.rb +2 -0
- data/lib/earth/rail/national_transit_database_company.rb +3 -2
- data/lib/earth/residence/residential_energy_consumption_survey_response/data_miner.rb +1 -1
- data/lib/earth/version.rb +1 -1
- data/spec/earth/air/aircraft_spec.rb +6 -5
- data/spec/earth/air/airport_spec.rb +5 -6
- data/spec/earth/air/bts_aircraft_spec.rb +7 -6
- data/spec/earth/air/flight_distance_class_spec.rb +5 -6
- data/spec/earth/air/flight_segment_spec.rb +5 -6
- data/spec/earth/automobile/automobile_fuel_spec.rb +11 -4
- data/spec/earth/automobile/automobile_make_model_year_variant_spec.rb +1 -5
- data/spec/earth/automobile/automobile_make_year_fleet_spec.rb +5 -6
- data/spec/earth/automobile/automobile_type_fuel_year_age_spec.rb +14 -8
- data/spec/earth/bus/bus_fuel_control_spec.rb +13 -6
- data/spec/earth/bus/bus_fuel_spec.rb +23 -0
- data/spec/earth/bus/bus_fuel_year_control_spec.rb +16 -9
- data/spec/earth/electricity/electric_market_spec.rb +25 -0
- data/spec/earth/electricity/electric_utility_spec.rb +54 -0
- data/spec/earth/electricity/green_button_adoption_spec.rb +26 -0
- data/spec/earth/fuel/fuel_spec.rb +9 -9
- data/spec/earth/hospitality/commercial_building_energy_consumption_survey_response_spec.rb +4 -6
- data/spec/earth/hospitality/country_lodging_class_spec.rb +5 -6
- data/spec/earth/industry/industry_spec.rb +6 -5
- data/spec/earth/industry/mecs_energy_spec.rb +4 -4
- data/spec/earth/industry/mecs_ratio_spec.rb +4 -4
- data/spec/earth/industry/naics_2002_naics_2007_concordance_spec.rb +6 -5
- data/spec/earth/industry/naics_2002_sic_1987_concordance_spec.rb +6 -5
- data/spec/earth/industry/naics_2002_spec.rb +6 -5
- data/spec/earth/industry/naics_2007_spec.rb +6 -5
- data/spec/earth/industry/sic_1987_spec.rb +4 -6
- data/spec/earth/locality/country_spec.rb +4 -6
- data/spec/earth/locality/state_spec.rb +4 -6
- data/spec/earth/locality/zip_code_spec.rb +4 -6
- data/spec/earth/pet/species_spec.rb +1 -1
- data/spec/spec_helper.rb +2 -0
- metadata +216 -361
- data/features/automobile_fuel.feature +0 -144
- data/features/automobile_make.feature +0 -24
- data/features/automobile_make_model.feature +0 -24
- data/features/automobile_make_model_year.feature +0 -34
- data/features/automobile_make_year.feature +0 -34
- data/features/automobile_size_class.feature +0 -59
- data/features/automobile_size_class_year.feature +0 -34
- data/features/automobile_type_fuel_control.feature +0 -34
- data/features/automobile_type_fuel_year.feature +0 -124
- data/features/automobile_type_fuel_year_age.feature +0 -94
- data/features/automobile_type_fuel_year_control.feature +0 -74
- data/features/automobile_type_year.feature +0 -64
- data/features/bus_class.feature +0 -39
- data/features/bus_fuel.feature +0 -114
- data/features/carrier.feature +0 -64
- data/features/carrier_mode.feature +0 -64
- data/features/computation_carrier.feature +0 -14
- data/features/computation_carrier_instance_class.feature +0 -24
- data/features/egrid_region.feature +0 -20
- data/features/egrid_subregion.feature +0 -134
- data/features/fuel_year.feature +0 -54
- data/features/greenhouse_gas.feature +0 -44
- data/features/rail_class.feature +0 -64
- data/features/shipment_mode.feature +0 -34
- data/features/step_definitions/data_steps.rb +0 -35
- data/features/support/env.rb +0 -19
- data/spec/earth/bus/bus_class_spec.rb +0 -14
@@ -1,64 +0,0 @@
|
|
1
|
-
# Feature: Data import for CarrierMode
|
2
|
-
# As a data user
|
3
|
-
# I want to import CarrierMode data
|
4
|
-
# So that I can perform carrier mode-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that carrier name is never missing
|
7
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
8
|
-
# When a data import verifies "Carrier name should never be missing"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Failing to verify that carrier name is never missing
|
12
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
13
|
-
# When a data import verifies "Carrier name should never be missing"
|
14
|
-
# Then the verification should not be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that mode name is never missing
|
17
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
18
|
-
# When a data import verifies "Mode name should never be missing"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Failing to verify that mode name is never missing
|
22
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
23
|
-
# When a data import verifies "Mode name should never be missing"
|
24
|
-
# Then the verification should not be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that transport emission factor units is never missing
|
27
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
28
|
-
# When a data import verifies "Transport emission factor units should never be missing"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Failing to verify that transport emission factor units is never missing
|
32
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
33
|
-
# When a data import verifies "Transport emission factor units should never be missing"
|
34
|
-
# Then the verification should not be successful
|
35
|
-
#
|
36
|
-
# Scenario: Successfully verifying that package volume > 0
|
37
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
38
|
-
# When a data import verifies "Package volume should be greater than zero"
|
39
|
-
# Then the verification should be successful
|
40
|
-
#
|
41
|
-
# Scenario: Failing to verify that package volume > 0
|
42
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
43
|
-
# When a data import verifies "Package volume should be greater than zero"
|
44
|
-
# Then the verification should not be successful
|
45
|
-
#
|
46
|
-
# Scenario: Successfully verifying that transport emission factor > 0
|
47
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
48
|
-
# When a data import verifies "Transport emission factor should be greater than zero"
|
49
|
-
# Then the verification should be successful
|
50
|
-
#
|
51
|
-
# Scenario: Failing to verify that transport emission factor > 0
|
52
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
53
|
-
# When a data import verifies "Transport emission factor should be greater than zero"
|
54
|
-
# Then the verification should not be successful
|
55
|
-
#
|
56
|
-
# Scenario: Successfully verifying that route inefficiency factor >= 1
|
57
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
58
|
-
# When a data import verifies "Route inefficiency factor should be one or more"
|
59
|
-
# Then the verification should be successful
|
60
|
-
#
|
61
|
-
# Scenario: Failing to verify that route inefficiency factor >= 1
|
62
|
-
# Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
63
|
-
# When a data import verifies "Route inefficiency factor should be one or more"
|
64
|
-
# Then the verification should not be successful
|
@@ -1,14 +0,0 @@
|
|
1
|
-
# Feature: Data import for ComputationCarrier
|
2
|
-
# As a data user
|
3
|
-
# I want to import ComputationCarrier data
|
4
|
-
# So that I can perform computation carrier-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that power usage effectiveness >= 1.0
|
7
|
-
# Given a "ComputationCarrier" data import fetches results listed in "computation_carrier_good"
|
8
|
-
# When a data import verifies "Power usage effectiveness should be one or more"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Failing to verify that power usage effectiveness >= 1.0
|
12
|
-
# Given a "ComputationCarrier" data import fetches results listed in "computation_carrier_bad"
|
13
|
-
# When a data import verifies "Power usage effectiveness should be one or more"
|
14
|
-
# Then the verification should not be successful
|
@@ -1,24 +0,0 @@
|
|
1
|
-
# Feature: Data import for ComputationCarrierInstanceClass
|
2
|
-
# As a data user
|
3
|
-
# I want to import ComputationCarrierInstanceClass data
|
4
|
-
# So that I can perform computation carrier instance class-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that electricity intensity is more than zero
|
7
|
-
# Given a "ComputationCarrierInstanceClass" data import fetches results listed in "computation_carrier_instance_class_good"
|
8
|
-
# When a data import verifies "Electricity intensity should be more than zero"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that electricity intensity units are kilowatts
|
12
|
-
# Given a "ComputationCarrierInstanceClass" data import fetches results listed in "computation_carrier_instance_class_good"
|
13
|
-
# When a data import verifies "Electricity intensity units should be kilowatts"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Failing to verify that electricity intensity is more than zero
|
17
|
-
# Given a "ComputationCarrierInstanceClass" data import fetches results listed in "computation_carrier_instance_class_bad"
|
18
|
-
# When a data import verifies "Electricity intensity should be more than zero"
|
19
|
-
# Then the verification should not be successful
|
20
|
-
#
|
21
|
-
# Scenario: Failing to verify that electricity intensity units are kilowatts
|
22
|
-
# Given a "ComputationCarrierInstanceClass" data import fetches results listed in "computation_carrier_instance_class_bad"
|
23
|
-
# When a data import verifies "Electricity intensity units should be kilowatts"
|
24
|
-
# Then the verification should not be successful
|
@@ -1,20 +0,0 @@
|
|
1
|
-
# Feature: Data import for EgridRegion
|
2
|
-
# As a data user
|
3
|
-
# I want to import EgridRegion data
|
4
|
-
# So that I can perform eGRID region-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that loss factor is greater than zero and less than one
|
7
|
-
# Given a "EgridRegion" data import fetches results listed in "egrid_region_good"
|
8
|
-
# When a data import verifies "Loss factor should be greater than zero and less than one"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# # FIXME TODO get this to work
|
12
|
-
# # Scenario: Successfully verifying that fallback loss factor is greater than zero and less than one
|
13
|
-
# # Given a "EgridRegion" data import fetches results listed in "egrid_region_good"
|
14
|
-
# # When a data import verifies "Fallback loss factor should be greater than zero and less than one"
|
15
|
-
# # Then the verification should be successful
|
16
|
-
#
|
17
|
-
# Scenario: Failing to verify that loss factor is greater than zero and less than one
|
18
|
-
# Given a "EgridRegion" data import fetches results listed in "egrid_region_bad"
|
19
|
-
# When a data import verifies "Loss factor should be greater than zero and less than one"
|
20
|
-
# Then the verification should not be successful
|
@@ -1,134 +0,0 @@
|
|
1
|
-
# Feature: Data import for EgridSubregion
|
2
|
-
# As a data user
|
3
|
-
# I want to import EgridSubregion data
|
4
|
-
# So that I can perform eGRID subregion-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that egrid region name is never missing
|
7
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
8
|
-
# When a data import verifies "Egrid region name should never be missing"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that net generation is > 0
|
12
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
13
|
-
# When a data import verifies "Net generation should be > 0"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that electricity co2 emission factor is > 0
|
17
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
18
|
-
# When a data import verifies "Electricity co2 emission factor should be > 0"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that electricity ch4 emission factor is > 0
|
22
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
23
|
-
# When a data import verifies "Electricity ch4 emission factor should be > 0"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that electricity n2o emission factor is > 0
|
27
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
28
|
-
# When a data import verifies "Electricity n2o emission factor should be > 0"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Successfully verifying that electricity emission factor is > 0
|
32
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
33
|
-
# When a data import verifies "Electricity emission factor should be > 0"
|
34
|
-
# Then the verification should be successful
|
35
|
-
#
|
36
|
-
# Scenario: Successfully verifying that electricity co2 biogenic emission factor is 0
|
37
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
38
|
-
# When a data import verifies "Electricity co2 biogenic emission factor should be 0"
|
39
|
-
# Then the verification should be successful
|
40
|
-
#
|
41
|
-
# Scenario: Successfully verifying that net generation units are megawatt hours
|
42
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
43
|
-
# When a data import verifies "Net generation units should be megawatt hours"
|
44
|
-
# Then the verification should be successful
|
45
|
-
#
|
46
|
-
# Scenario: Successfully verifying that electricity co2 emission factor units are kilograms per kilowatt hour
|
47
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
48
|
-
# When a data import verifies "Electricity co2 emission factor units should be kilograms per kilowatt hour"
|
49
|
-
# Then the verification should be successful
|
50
|
-
#
|
51
|
-
# Scenario: Successfully verifying that electricity co2 biogenic emission factor units are kilograms per kilowatt hour
|
52
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
53
|
-
# When a data import verifies "Electricity co2 biogenic emission factor units should be kilograms per kilowatt hour"
|
54
|
-
# Then the verification should be successful
|
55
|
-
#
|
56
|
-
# Scenario: Successfully verifying that electricity ch4 emission factor units are kilograms co2e per kilowatt hour
|
57
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
58
|
-
# When a data import verifies "Electricity ch4 emission factor units should be kilograms co2e per kilowatt hour"
|
59
|
-
# Then the verification should be successful
|
60
|
-
#
|
61
|
-
# Scenario: Successfully verifying that electricity n2o emission factor units are kilograms co2e per kilowatt hour
|
62
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
63
|
-
# When a data import verifies "Electricity n2o emission factor units should be kilograms co2e per kilowatt hour"
|
64
|
-
# Then the verification should be successful
|
65
|
-
#
|
66
|
-
# Scenario: Successfully verifying that electricity emission factor units are kilograms co2e per kilowatt hour
|
67
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
68
|
-
# When a data import verifies "Electricity emission factor units should be kilograms co2e per kilowatt hour"
|
69
|
-
# Then the verification should be successful
|
70
|
-
#
|
71
|
-
# Scenario: Failing to verify that egrid region name is never missing
|
72
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
73
|
-
# When a data import verifies "Egrid region name should never be missing"
|
74
|
-
# Then the verification should not be successful
|
75
|
-
#
|
76
|
-
# Scenario: Failing to verify that net generation is > 0
|
77
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
78
|
-
# When a data import verifies "Net generation should be > 0"
|
79
|
-
# Then the verification should not be successful
|
80
|
-
#
|
81
|
-
# Scenario: Failing to verify that electricity co2 emission factor is > 0
|
82
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
83
|
-
# When a data import verifies "Electricity co2 emission factor should be > 0"
|
84
|
-
# Then the verification should not be successful
|
85
|
-
#
|
86
|
-
# Scenario: Failing to verify that electricity ch4 emission factor is > 0
|
87
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
88
|
-
# When a data import verifies "Electricity ch4 emission factor should be > 0"
|
89
|
-
# Then the verification should not be successful
|
90
|
-
#
|
91
|
-
# Scenario: Failing to verify that electricity n2o emission factor is > 0
|
92
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
93
|
-
# When a data import verifies "Electricity n2o emission factor should be > 0"
|
94
|
-
# Then the verification should not be successful
|
95
|
-
#
|
96
|
-
# Scenario: Failing to verify that electricity emission factor is > 0
|
97
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
98
|
-
# When a data import verifies "Electricity emission factor should be > 0"
|
99
|
-
# Then the verification should not be successful
|
100
|
-
#
|
101
|
-
# Scenario: Failing to verify that electricity co2 biogenic emission factor is 0
|
102
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
103
|
-
# When a data import verifies "Electricity co2 biogenic emission factor should be 0"
|
104
|
-
# Then the verification should not be successful
|
105
|
-
#
|
106
|
-
# Scenario: Failing to verify that net generation units are megawatt hours
|
107
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
108
|
-
# When a data import verifies "Net generation units should be megawatt hours"
|
109
|
-
# Then the verification should not be successful
|
110
|
-
#
|
111
|
-
# Scenario: Failing to verify that electricity co2 emission factor units are kilograms per kilowatt hour
|
112
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
113
|
-
# When a data import verifies "Electricity co2 emission factor units should be kilograms per kilowatt hour"
|
114
|
-
# Then the verification should not be successful
|
115
|
-
#
|
116
|
-
# Scenario: Failing to verify that electricity co2 biogenic emission factor units are kilograms per kilowatt hour
|
117
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
118
|
-
# When a data import verifies "Electricity co2 biogenic emission factor units should be kilograms per kilowatt hour"
|
119
|
-
# Then the verification should not be successful
|
120
|
-
#
|
121
|
-
# Scenario: Failing to verify that electricity ch4 emission factor units are kilograms co2e per kilowatt hour
|
122
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
123
|
-
# When a data import verifies "Electricity ch4 emission factor units should be kilograms co2e per kilowatt hour"
|
124
|
-
# Then the verification should not be successful
|
125
|
-
#
|
126
|
-
# Scenario: Failing to verify that electricity n2o emission factor units are kilograms co2e per kilowatt hour
|
127
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
128
|
-
# When a data import verifies "Electricity n2o emission factor units should be kilograms co2e per kilowatt hour"
|
129
|
-
# Then the verification should not be successful
|
130
|
-
#
|
131
|
-
# Scenario: Failing to verify that electricity emission factor units are kilograms co2e per kilowatt hour
|
132
|
-
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
133
|
-
# When a data import verifies "Electricity emission factor units should be kilograms co2e per kilowatt hour"
|
134
|
-
# Then the verification should not be successful
|
data/features/fuel_year.feature
DELETED
@@ -1,54 +0,0 @@
|
|
1
|
-
# Feature: Data import for FuelYear
|
2
|
-
# As a data user
|
3
|
-
# I want to import FuelYear data
|
4
|
-
# So that I can perform fuel year control-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that fuel name is never missing
|
7
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_good"
|
8
|
-
# When a data import verifies "Fuel name should never be missing"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that year is from 1990 to 2008
|
12
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_good"
|
13
|
-
# When a data import verifies "Year should be from 1990 to 2008"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that carbon content and energy content are greater than zero
|
17
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_good"
|
18
|
-
# When a data import verifies "Carbon content and energy content should be greater than zero"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that emission factors are zero or more
|
22
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_good"
|
23
|
-
# When a data import verifies "Emission factors should be zero or more"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# # Scenario: Successfully verifying that units are correct
|
27
|
-
# # Given a "FuelYear" data import fetches results listed in "fuel_year_good"
|
28
|
-
# # When a data import verifies "Units should be correct"
|
29
|
-
# # Then the verification should be successful
|
30
|
-
# #
|
31
|
-
# Scenario: Failing to verify that fuel name is never missing
|
32
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_bad"
|
33
|
-
# When a data import verifies "Fuel name should never be missing"
|
34
|
-
# Then the verification should not be successful
|
35
|
-
#
|
36
|
-
# Scenario: Failing to verify that year is from 1990 to 2008
|
37
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_bad"
|
38
|
-
# When a data import verifies "Year should be from 1990 to 2008"
|
39
|
-
# Then the verification should not be successful
|
40
|
-
#
|
41
|
-
# Scenario: Failing to verify that carbon content and energy content are greater than zero
|
42
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_bad"
|
43
|
-
# When a data import verifies "Carbon content and energy content should be greater than zero"
|
44
|
-
# Then the verification should not be successful
|
45
|
-
#
|
46
|
-
# Scenario: Failing to verify that emission factors are zero or more
|
47
|
-
# Given a "FuelYear" data import fetches results listed in "fuel_year_bad"
|
48
|
-
# When a data import verifies "Emission factors should be zero or more"
|
49
|
-
# Then the verification should not be successful
|
50
|
-
#
|
51
|
-
# # Scenario: Failing to verify that units are correct
|
52
|
-
# # Given a "FuelYear" data import fetches results listed in "fuel_year_bad"
|
53
|
-
# # When a data import verifies "Units should be correct"
|
54
|
-
# # Then the verification should not be successful
|
@@ -1,44 +0,0 @@
|
|
1
|
-
# Feature: Data import for GreenhouseGas
|
2
|
-
# As a data user
|
3
|
-
# I want to import GreenhouseGas data
|
4
|
-
# So that I can perform global warming potential-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that abbreviation and IPCC report are never missing
|
7
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_good"
|
8
|
-
# When a data import verifies "Abbreviation and IPCC report should never be missing"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that time horizon is 100
|
12
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_good"
|
13
|
-
# When a data import verifies "Time horizon should be 100"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that time horizon units are years
|
17
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_good"
|
18
|
-
# When a data import verifies "Time horizon units should be years"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that global warming potential is one or more
|
22
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_good"
|
23
|
-
# When a data import verifies "Global warming potential should be one or more"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Failing to verify that abbreviation and IPCC report are never missing
|
27
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_bad"
|
28
|
-
# When a data import verifies "Abbreviation and IPCC report should never be missing"
|
29
|
-
# Then the verification should not be successful
|
30
|
-
#
|
31
|
-
# Scenario: Failing to verify that time horizon is 100
|
32
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_bad"
|
33
|
-
# When a data import verifies "Time horizon should be 100"
|
34
|
-
# Then the verification should not be successful
|
35
|
-
#
|
36
|
-
# Scenario: Failing to verify that time horizon units are years
|
37
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_bad"
|
38
|
-
# When a data import verifies "Time horizon units should be years"
|
39
|
-
# Then the verification should not be successful
|
40
|
-
#
|
41
|
-
# Scenario: Failing to verify that global warming potential is one or more
|
42
|
-
# Given a "GreenhouseGas" data import fetches results listed in "greenhouse_gas_bad"
|
43
|
-
# When a data import verifies "Global warming potential should be one or more"
|
44
|
-
# Then the verification should not be successful
|
data/features/rail_class.feature
DELETED
@@ -1,64 +0,0 @@
|
|
1
|
-
# Feature: Data import for RailClass
|
2
|
-
# As a data user
|
3
|
-
# I want to import RailClass data
|
4
|
-
# So that I can perform rail class-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that passengers, distance, speed, and electricity intensity are greater than zero
|
7
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_good"
|
8
|
-
# When a data import verifies "Passengers, distance, speed, and electricity intensity should be greater than zero"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that distance units are kilometres
|
12
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_good"
|
13
|
-
# When a data import verifies "Distance units should be kilometres"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that speed units are kilometres per hour
|
17
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_good"
|
18
|
-
# When a data import verifies "Speed units should be kilometres per hour"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that electricity intensity units are kilowatt hours per kilometre
|
22
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_good"
|
23
|
-
# When a data import verifies "Electricity intensity units should be kilowatt hours per kilometre"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that diesel intensity is zero or more
|
27
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_good"
|
28
|
-
# When a data import verifies "Diesel intensity should be zero or more"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Successfully verifying that diesel intensity units are litres per kilometre
|
32
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_good"
|
33
|
-
# When a data import verifies "Diesel intensity units should be litres per kilometre"
|
34
|
-
# Then the verification should be successful
|
35
|
-
#
|
36
|
-
# Scenario: Failing to verify that passengers, distance, speed, and electricity intensity are greater than zero
|
37
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_bad"
|
38
|
-
# When a data import verifies "Passengers, distance, speed, and electricity intensity should be greater than zero"
|
39
|
-
# Then the verification should not be successful
|
40
|
-
#
|
41
|
-
# Scenario: Failing to verify that distance units are kilometres
|
42
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_bad"
|
43
|
-
# When a data import verifies "Distance units should be kilometres"
|
44
|
-
# Then the verification should not be successful
|
45
|
-
#
|
46
|
-
# Scenario: Failing to verify that speed units are kilometres per hour
|
47
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_bad"
|
48
|
-
# When a data import verifies "Speed units should be kilometres per hour"
|
49
|
-
# Then the verification should not be successful
|
50
|
-
#
|
51
|
-
# Scenario: Failing to verify that electricity intensity units are kilowatt hours per kilometre
|
52
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_bad"
|
53
|
-
# When a data import verifies "Electricity intensity units should be kilowatt hours per kilometre"
|
54
|
-
# Then the verification should not be successful
|
55
|
-
#
|
56
|
-
# Scenario: Failing to verify that diesel intensity is zero or more
|
57
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_bad"
|
58
|
-
# When a data import verifies "Diesel intensity should be zero or more"
|
59
|
-
# Then the verification should not be successful
|
60
|
-
#
|
61
|
-
# Scenario: Failing to verify that diesel intensity units are litres per kilometre
|
62
|
-
# Given a "RailClass" data import fetches results listed in "rail_class_bad"
|
63
|
-
# When a data import verifies "Diesel intensity units should be litres per kilometre"
|
64
|
-
# Then the verification should not be successful
|
@@ -1,34 +0,0 @@
|
|
1
|
-
# Feature: Data import for ShipmentMode
|
2
|
-
# As a data user
|
3
|
-
# I want to import ShipmentMode data
|
4
|
-
# So that I can perform shipment mode-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that route inefficiency factor >= 1
|
7
|
-
# Given a "ShipmentMode" data import fetches results listed in "shipment_mode_good"
|
8
|
-
# When a data import verifies "Route inefficiency factor should be one or more"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Failing to verify that route inefficiency factor >= 1
|
12
|
-
# Given a "ShipmentMode" data import fetches results listed in "shipment_mode_bad"
|
13
|
-
# When a data import verifies "Route inefficiency factor should be one or more"
|
14
|
-
# Then the verification should not be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that transport emission factor > 0
|
17
|
-
# Given a "ShipmentMode" data import fetches results listed in "shipment_mode_good"
|
18
|
-
# When a data import verifies "Transport emission factor should be greater than zero"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Failing to verify that transport emission factor > 0
|
22
|
-
# Given a "ShipmentMode" data import fetches results listed in "shipment_mode_bad"
|
23
|
-
# When a data import verifies "Transport emission factor should be greater than zero"
|
24
|
-
# Then the verification should not be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that transport emission factor units is never missing
|
27
|
-
# Given a "ShipmentMode" data import fetches results listed in "shipment_mode_good"
|
28
|
-
# When a data import verifies "Transport emission factor units should never be missing"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Failing to verify that transport emission factor units is never missing
|
32
|
-
# Given a "ShipmentMode" data import fetches results listed in "shipment_mode_bad"
|
33
|
-
# When a data import verifies "Transport emission factor units should never be missing"
|
34
|
-
# Then the verification should not be successful
|