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,94 +0,0 @@
|
|
1
|
-
# Feature: Data import for AutomobileTypeFuelYearAge
|
2
|
-
# As a data user
|
3
|
-
# I want to import AutomobileTypeFuelYearAge data
|
4
|
-
# So that I can perform type fuel year age-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that type name is not missing
|
7
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
8
|
-
# When a data import verifies "Type name should never be missing"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that fuel common name is not missing
|
12
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
13
|
-
# When a data import verifies "Fuel common name should never be missing"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that type fuel year name is not missing
|
17
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
18
|
-
# When a data import verifies "Type fuel year name should never be missing"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that year is 2008
|
22
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
23
|
-
# When a data import verifies "Year should be 2008"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that age is from zero to thirty
|
27
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
28
|
-
# When a data import verifies "Age should be from 0 to 30"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Successfully verifying that total travel percent is from zero to one
|
32
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
33
|
-
# When a data import verifies "Total travel percent should be from 0 to 1"
|
34
|
-
# Then the verification should be successful
|
35
|
-
#
|
36
|
-
# Scenario: Successfully verifying that annual distance is greater than zero
|
37
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
38
|
-
# When a data import verifies "Annual distance should be greater than zero"
|
39
|
-
# Then the verification should be successful
|
40
|
-
#
|
41
|
-
# Scenario: Successfully verifying that vehicles is greater than zero
|
42
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
43
|
-
# When a data import verifies "Vehicles should be greater than zero"
|
44
|
-
# Then the verification should be successful
|
45
|
-
#
|
46
|
-
# Scenario: Successfully verifying that annual distance units are kilometres
|
47
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
|
48
|
-
# When a data import verifies "Annual distance units should be kilometres"
|
49
|
-
# Then the verification should be successful
|
50
|
-
#
|
51
|
-
# Scenario: Failing to verify that type name is not missing
|
52
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
53
|
-
# When a data import verifies "Type name should never be missing"
|
54
|
-
# Then the verification should not be successful
|
55
|
-
#
|
56
|
-
# Scenario: Failing to verify that fuel common name is not missing
|
57
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
58
|
-
# When a data import verifies "Fuel common name should never be missing"
|
59
|
-
# Then the verification should not be successful
|
60
|
-
#
|
61
|
-
# Scenario: Failing to verify that type fuel year name is not missing
|
62
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
63
|
-
# When a data import verifies "Type fuel year name should never be missing"
|
64
|
-
# Then the verification should not be successful
|
65
|
-
#
|
66
|
-
# Scenario: Failing to verify that year is 2008
|
67
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
68
|
-
# When a data import verifies "Year should be 2008"
|
69
|
-
# Then the verification should not be successful
|
70
|
-
#
|
71
|
-
# Scenario: Failing to verify that age is from zero to thirty
|
72
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
73
|
-
# When a data import verifies "Age should be from 0 to 30"
|
74
|
-
# Then the verification should not be successful
|
75
|
-
#
|
76
|
-
# Scenario: Failing to verify that total travel percent is from zero to one
|
77
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
78
|
-
# When a data import verifies "Total travel percent should be from 0 to 1"
|
79
|
-
# Then the verification should not be successful
|
80
|
-
#
|
81
|
-
# Scenario: Failing to verify that annual distance is greater than zero
|
82
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
83
|
-
# When a data import verifies "Annual distance should be greater than zero"
|
84
|
-
# Then the verification should not be successful
|
85
|
-
#
|
86
|
-
# Scenario: Failing to verify that vehicles is greater than zero
|
87
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
88
|
-
# When a data import verifies "Vehicles should be greater than zero"
|
89
|
-
# Then the verification should not be successful
|
90
|
-
#
|
91
|
-
# Scenario: Failing to verify that annual distance units are kilometres
|
92
|
-
# Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
|
93
|
-
# When a data import verifies "Annual distance units should be kilometres"
|
94
|
-
# Then the verification should not be successful
|
@@ -1,74 +0,0 @@
|
|
1
|
-
# Feature: Data import for AutomobileTypeFuelYearControl
|
2
|
-
# As a data user
|
3
|
-
# I want to import AutomobileTypeFuelYearControl data
|
4
|
-
# So that I can perform type fuel year control-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that type name is not missing
|
7
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
|
8
|
-
# When a data import verifies "Type name should never be missing"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that fuel common name is not missing
|
12
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
|
13
|
-
# When a data import verifies "Fuel common name should never be missing"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that control name is not missing
|
17
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
|
18
|
-
# When a data import verifies "Control name should never be missing"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that type fuel control name is not missing
|
22
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
|
23
|
-
# When a data import verifies "Type fuel control name should never be missing"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that type fuel year name is not missing
|
27
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
|
28
|
-
# When a data import verifies "Type fuel year name should never be missing"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Successfully verifying that year is from 1990 to 2008
|
32
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
|
33
|
-
# When a data import verifies "Year should be from 1990 to 2008"
|
34
|
-
# Then the verification should be successful
|
35
|
-
#
|
36
|
-
# # Scenario: Successfully verifying that total travel percent for each fuel type year sums to one
|
37
|
-
# # Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
|
38
|
-
# # When a data import verifies "Total travel percent for each type fuel year should sum to one"
|
39
|
-
# # Then the verification should be successful
|
40
|
-
# #
|
41
|
-
# Scenario: Failing to verify that type name is not missing
|
42
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
|
43
|
-
# When a data import verifies "Type name should never be missing"
|
44
|
-
# Then the verification should not be successful
|
45
|
-
#
|
46
|
-
# Scenario: Failing to verify that fuel common name is not missing
|
47
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
|
48
|
-
# When a data import verifies "Fuel common name should never be missing"
|
49
|
-
# Then the verification should not be successful
|
50
|
-
#
|
51
|
-
# Scenario: Failing to verify that control name is not missing
|
52
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
|
53
|
-
# When a data import verifies "Control name should never be missing"
|
54
|
-
# Then the verification should not be successful
|
55
|
-
#
|
56
|
-
# Scenario: Failing to verify that type fuel control name is not missing
|
57
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
|
58
|
-
# When a data import verifies "Type fuel control name should never be missing"
|
59
|
-
# Then the verification should not be successful
|
60
|
-
#
|
61
|
-
# Scenario: Failing to verify that type fuel year name is not missing
|
62
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
|
63
|
-
# When a data import verifies "Type fuel year name should never be missing"
|
64
|
-
# Then the verification should not be successful
|
65
|
-
#
|
66
|
-
# Scenario: Failing to verify that year is from 1990 to 2008
|
67
|
-
# Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
|
68
|
-
# When a data import verifies "Year should be from 1990 to 2008"
|
69
|
-
# Then the verification should not be successful
|
70
|
-
#
|
71
|
-
# # Scenario: Failing to verify that total travel percent for each fuel type year sums to one
|
72
|
-
# # Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
|
73
|
-
# # When a data import verifies "Total travel percent for each type fuel year should sum to one"
|
74
|
-
# # Then the verification should not be successful
|
@@ -1,64 +0,0 @@
|
|
1
|
-
# Feature: Data import for AutomobileTypeYear
|
2
|
-
# As a data user
|
3
|
-
# I want to import AutomobileTypeYear data
|
4
|
-
# So that I can perform type year-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that type name is never missing
|
7
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
|
8
|
-
# When a data import verifies "Type 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 "AutomobileTypeYear" data import fetches results listed in "automobile_type_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 HFC emissions is zero or more
|
17
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
|
18
|
-
# When a data import verifies "Hfc emissions should be zero or more"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that HFC emission factor is zero or more
|
22
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
|
23
|
-
# When a data import verifies "Hfc emission factor should be zero or more"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that HFC emissions units are kilograms CO2e
|
27
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
|
28
|
-
# When a data import verifies "Hfc emissions units should be kilograms co2e"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Successfully verifying that HFC emission factor units are kilograms CO2e per litre
|
32
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
|
33
|
-
# When a data import verifies "Hfc emission factor units should be kilograms co2e per litre"
|
34
|
-
# Then the verification should be successful
|
35
|
-
#
|
36
|
-
# Scenario: Failing to verify that type name is never missing
|
37
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
|
38
|
-
# When a data import verifies "Type name should never be missing"
|
39
|
-
# Then the verification should not be successful
|
40
|
-
#
|
41
|
-
# Scenario: Failing to verify that year is from 1990 to 2008
|
42
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
|
43
|
-
# When a data import verifies "Year should be from 1990 to 2008"
|
44
|
-
# Then the verification should not be successful
|
45
|
-
#
|
46
|
-
# Scenario: Failing to verify that HFC emissions is zero or more
|
47
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
|
48
|
-
# When a data import verifies "Hfc emissions should be zero or more"
|
49
|
-
# Then the verification should not be successful
|
50
|
-
#
|
51
|
-
# Scenario: Failing to verify that HFC emission factor is zero or more
|
52
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
|
53
|
-
# When a data import verifies "Hfc emission factor should be zero or more"
|
54
|
-
# Then the verification should not be successful
|
55
|
-
#
|
56
|
-
# Scenario: Failing to verify that HFC emissions units are kilograms CO2e
|
57
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
|
58
|
-
# When a data import verifies "Hfc emissions units should be kilograms co2e"
|
59
|
-
# Then the verification should not be successful
|
60
|
-
#
|
61
|
-
# Scenario: Failing to verify that HFC emission factor units are kilograms CO2e per litre
|
62
|
-
# Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
|
63
|
-
# When a data import verifies "Hfc emission factor units should be kilograms co2e per litre"
|
64
|
-
# Then the verification should not be successful
|
data/features/bus_class.feature
DELETED
@@ -1,39 +0,0 @@
|
|
1
|
-
# Feature: Data import for BusClass
|
2
|
-
# As a data user
|
3
|
-
# I want to import BusClass data
|
4
|
-
# So that I can perform bus class-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that some attributes are greater than zero
|
7
|
-
# Given a "BusClass" data import fetches results listed in "bus_class_good"
|
8
|
-
# When a data import verifies "Some attributes should be greater than zero"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Successfully verifying that some attributes are zero or more
|
12
|
-
# Given a "BusClass" data import fetches results listed in "bus_class_good"
|
13
|
-
# When a data import verifies "Some attributes should be zero or more"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that distance units are correct
|
17
|
-
# Given a "BusClass" data import fetches results listed in "bus_class_good"
|
18
|
-
# When a data import verifies "Units should be correct"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that fallbacks satisfy same criteria as data
|
22
|
-
# Given a "BusClass" data import fetches results listed in "bus_class_good"
|
23
|
-
# When a data import verifies "Fallbacks should satisfy same constraints as data"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Failing to verify that some attributes are greater than zero
|
27
|
-
# Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
28
|
-
# When a data import verifies "Some attributes should be greater than zero"
|
29
|
-
# Then the verification should not be successful
|
30
|
-
#
|
31
|
-
# Scenario: Failing to verify that some attributes are zero or more
|
32
|
-
# Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
33
|
-
# When a data import verifies "Some attributes should be zero or more"
|
34
|
-
# Then the verification should not be successful
|
35
|
-
#
|
36
|
-
# Scenario: Failing to verify that distance units are correct
|
37
|
-
# Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
38
|
-
# When a data import verifies "Units should be correct"
|
39
|
-
# Then the verification should not be successful
|
data/features/bus_fuel.feature
DELETED
@@ -1,114 +0,0 @@
|
|
1
|
-
# Feature: Data import for BusFuel
|
2
|
-
# As a data user
|
3
|
-
# I want to import BusFuel data
|
4
|
-
# So that I can perform bus fuel-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that fuel name is never missing
|
7
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_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 energy content is greater than zero if present
|
12
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
13
|
-
# When a data import verifies "Energy content should be greater than zero if present"
|
14
|
-
# Then the verification should be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that co2 emission factor is 0 or more
|
17
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
18
|
-
# When a data import verifies "Co2 emission factor should be 0 or more"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Successfully verifying that co2 biogenic emission factor is 0 or more
|
22
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
23
|
-
# When a data import verifies "Co2 biogenic emission factor should be 0 or more"
|
24
|
-
# Then the verification should be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that ch4 emission factor is > 0
|
27
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
28
|
-
# When a data import verifies "Ch4 emission factor should be > 0"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Successfully verifying that n2o emission factor is > 0
|
32
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
33
|
-
# When a data import verifies "N2o emission factor should be > 0"
|
34
|
-
# Then the verification should be successful
|
35
|
-
#
|
36
|
-
# Scenario: Successfully verifying that energy content units are megajoules per litre if present
|
37
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
38
|
-
# When a data import verifies "Energy content units should be megajoules per litre if present"
|
39
|
-
# Then the verification should be successful
|
40
|
-
#
|
41
|
-
# Scenario: Successfully verifying that co2 emission factor units are kilgrams per litre
|
42
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
43
|
-
# When a data import verifies "Co2 emission factor units should be kilograms per litre"
|
44
|
-
# Then the verification should be successful
|
45
|
-
#
|
46
|
-
# Scenario: Successfully verifying that co2 biogenic emission factor units are kilgrams per litre
|
47
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
48
|
-
# When a data import verifies "Co2 biogenic emission factor units should be kilograms per litre"
|
49
|
-
# Then the verification should be successful
|
50
|
-
#
|
51
|
-
# Scenario: Successfully verifying that ch4 emission factor units are kilgrams co2e per kilometre
|
52
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
53
|
-
# When a data import verifies "Ch4 emission factor units should be kilograms co2e per kilometre"
|
54
|
-
# Then the verification should be successful
|
55
|
-
#
|
56
|
-
# Scenario: Successfully verifying that n2o emission factor units are kilgrams co2e per kilometre
|
57
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_good"
|
58
|
-
# When a data import verifies "N2o emission factor units should be kilograms co2e per kilometre"
|
59
|
-
# Then the verification should be successful
|
60
|
-
#
|
61
|
-
# Scenario: Failing to verify that fuel name is never missing
|
62
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
63
|
-
# When a data import verifies "Fuel name should never be missing"
|
64
|
-
# Then the verification should not be successful
|
65
|
-
#
|
66
|
-
# Scenario: Failing to verify that energy content is greater than zero if present
|
67
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
68
|
-
# When a data import verifies "Energy content should be greater than zero if present"
|
69
|
-
# Then the verification should not be successful
|
70
|
-
#
|
71
|
-
# Scenario: Failing to verify that co2 emission factor is 0 or more
|
72
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
73
|
-
# When a data import verifies "Co2 emission factor should be 0 or more"
|
74
|
-
# Then the verification should not be successful
|
75
|
-
#
|
76
|
-
# Scenario: Failing to verify that co2 biogenic emission factor is 0 or more
|
77
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
78
|
-
# When a data import verifies "Co2 biogenic emission factor should be 0 or more"
|
79
|
-
# Then the verification should not be successful
|
80
|
-
#
|
81
|
-
# Scenario: Failing to verify that ch4 emission factor is > 0
|
82
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
83
|
-
# When a data import verifies "Ch4 emission factor should be > 0"
|
84
|
-
# Then the verification should not be successful
|
85
|
-
#
|
86
|
-
# Scenario: Failing to verify that n2o emission factor is > 0
|
87
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
88
|
-
# When a data import verifies "N2o emission factor should be > 0"
|
89
|
-
# Then the verification should not be successful
|
90
|
-
#
|
91
|
-
# Scenario: Failing to verify that energy content units are megajoules per litre if present
|
92
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
93
|
-
# When a data import verifies "Energy content units should be megajoules per litre if present"
|
94
|
-
# Then the verification should not be successful
|
95
|
-
#
|
96
|
-
# Scenario: Failing to verify that co2 emission factor units are kilgrams per litre
|
97
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
98
|
-
# When a data import verifies "Co2 emission factor units should be kilograms per litre"
|
99
|
-
# Then the verification should not be successful
|
100
|
-
#
|
101
|
-
# Scenario: Failing to verify that co2 biogenic emission factor units are kilgrams per litre
|
102
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
103
|
-
# When a data import verifies "Co2 biogenic emission factor units should be kilograms per litre"
|
104
|
-
# Then the verification should not be successful
|
105
|
-
#
|
106
|
-
# Scenario: Failing to verify that ch4 emission factor units are kilgrams co2e per kilometre
|
107
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
108
|
-
# When a data import verifies "Ch4 emission factor units should be kilograms co2e per kilometre"
|
109
|
-
# Then the verification should not be successful
|
110
|
-
#
|
111
|
-
# Scenario: Failing to verify that n2o emission factor units are kilgrams co2e per kilometre
|
112
|
-
# Given a "BusFuel" data import fetches results listed in "bus_fuel_bad"
|
113
|
-
# When a data import verifies "N2o emission factor units should be kilograms co2e per kilometre"
|
114
|
-
# Then the verification should not be successful
|
data/features/carrier.feature
DELETED
@@ -1,64 +0,0 @@
|
|
1
|
-
# Feature: Data import for Carrier
|
2
|
-
# As a data user
|
3
|
-
# I want to import Carrier data
|
4
|
-
# So that I can perform carrier-based calculations
|
5
|
-
#
|
6
|
-
# Scenario: Successfully verifying that package volume > 0
|
7
|
-
# Given a "Carrier" data import fetches results listed in "carrier_good"
|
8
|
-
# When a data import verifies "Package volume should be greater than zero"
|
9
|
-
# Then the verification should be successful
|
10
|
-
#
|
11
|
-
# Scenario: Failing to verify that package volume > 0
|
12
|
-
# Given a "Carrier" data import fetches results listed in "carrier_bad"
|
13
|
-
# When a data import verifies "Package volume should be greater than zero"
|
14
|
-
# Then the verification should not be successful
|
15
|
-
#
|
16
|
-
# Scenario: Successfully verifying that route inefficiency factor >= 1
|
17
|
-
# Given a "Carrier" data import fetches results listed in "carrier_good"
|
18
|
-
# When a data import verifies "Route inefficiency factor should be one or more"
|
19
|
-
# Then the verification should be successful
|
20
|
-
#
|
21
|
-
# Scenario: Failing to verify that route inefficiency factor >= 1
|
22
|
-
# Given a "Carrier" data import fetches results listed in "carrier_bad"
|
23
|
-
# When a data import verifies "Route inefficiency factor should be one or more"
|
24
|
-
# Then the verification should not be successful
|
25
|
-
#
|
26
|
-
# Scenario: Successfully verifying that transport emission factor > 0
|
27
|
-
# Given a "Carrier" data import fetches results listed in "carrier_good"
|
28
|
-
# When a data import verifies "Transport emission factor should be greater than zero"
|
29
|
-
# Then the verification should be successful
|
30
|
-
#
|
31
|
-
# Scenario: Failing to verify that transport emission factor > 0
|
32
|
-
# Given a "Carrier" data import fetches results listed in "carrier_bad"
|
33
|
-
# When a data import verifies "Transport emission factor should be greater than zero"
|
34
|
-
# Then the verification should not be successful
|
35
|
-
#
|
36
|
-
# Scenario: Successfully verifying that transport emission factor units is never missing
|
37
|
-
# Given a "Carrier" data import fetches results listed in "carrier_good"
|
38
|
-
# When a data import verifies "Transport emission factor units should never be missing"
|
39
|
-
# Then the verification should be successful
|
40
|
-
#
|
41
|
-
# Scenario: Failing to verify that transport emission factor units is never missing
|
42
|
-
# Given a "Carrier" data import fetches results listed in "carrier_bad"
|
43
|
-
# When a data import verifies "Transport emission factor units should never be missing"
|
44
|
-
# Then the verification should not be successful
|
45
|
-
#
|
46
|
-
# Scenario: Successfully verifying that corporate emission factor > 0
|
47
|
-
# Given a "Carrier" data import fetches results listed in "carrier_good"
|
48
|
-
# When a data import verifies "Corporate emission factor should be greater than zero"
|
49
|
-
# Then the verification should be successful
|
50
|
-
#
|
51
|
-
# Scenario: Failing to verify that corporate emission factor > 0
|
52
|
-
# Given a "Carrier" data import fetches results listed in "carrier_bad"
|
53
|
-
# When a data import verifies "Corporate emission factor should be greater than zero"
|
54
|
-
# Then the verification should not be successful
|
55
|
-
#
|
56
|
-
# Scenario: Successfully verifying that corporate emission factor units is never missing
|
57
|
-
# Given a "Carrier" data import fetches results listed in "carrier_good"
|
58
|
-
# When a data import verifies "Corporate emission factor units should never be missing"
|
59
|
-
# Then the verification should be successful
|
60
|
-
#
|
61
|
-
# Scenario: Failing to verify that corporate emission factor units is never missing
|
62
|
-
# Given a "Carrier" data import fetches results listed in "carrier_bad"
|
63
|
-
# When a data import verifies "Corporate emission factor units should never be missing"
|
64
|
-
# Then the verification should not be successful
|