earth 0.6.4 → 0.6.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/earth.gemspec +1 -1
- data/features/automobile_fuel.feature +144 -144
- data/features/automobile_make.feature +24 -24
- data/features/automobile_make_fleet_year.feature +34 -34
- data/features/automobile_make_model.feature +24 -24
- data/features/automobile_make_model_year.feature +34 -34
- data/features/automobile_make_model_year_variant.feature +46 -46
- data/features/automobile_make_year.feature +34 -34
- data/features/automobile_size_class.feature +59 -59
- data/features/automobile_size_class_year.feature +34 -34
- data/features/automobile_type_fuel_age.feature +55 -55
- data/features/automobile_type_fuel_control.feature +34 -34
- data/features/automobile_type_fuel_year.feature +124 -124
- data/features/automobile_type_fuel_year_age.feature +94 -94
- data/features/automobile_type_fuel_year_control.feature +74 -74
- data/features/automobile_type_year.feature +64 -64
- data/features/bus_class.feature +39 -39
- data/features/bus_fuel.feature +114 -114
- data/features/carrier.feature +64 -64
- data/features/carrier_mode.feature +64 -64
- data/features/computation_carrier.feature +14 -14
- data/features/computation_carrier_instance_class.feature +24 -24
- data/features/egrid_region.feature +20 -20
- data/features/egrid_subregion.feature +134 -134
- data/features/fuel_year.feature +54 -54
- data/features/greenhouse_gas.feature +44 -44
- data/features/rail_class.feature +64 -64
- data/features/shipment_mode.feature +34 -34
- data/lib/earth/air.rb +1 -0
- data/lib/earth/air/data_miner.rb +1 -0
- data/lib/earth/air/flight_distance_class.rb +10 -0
- data/lib/earth/air/flight_distance_class/data_miner.rb +18 -2
- data/lib/earth/air/flight_distance_class_seat_class.rb +10 -0
- data/lib/earth/air/flight_distance_class_seat_class/data_miner.rb +13 -0
- data/lib/earth/air/flight_seat_class.rb +6 -5
- data/lib/earth/air/flight_seat_class/data_miner.rb +18 -6
- data/lib/earth/version.rb +1 -1
- data/spec/earth_spec.rb +2 -2
- metadata +187 -173
|
@@ -1,74 +1,74 @@
|
|
|
1
|
-
Feature: Data import for AutomobileTypeFuelYearControl
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
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 +1,64 @@
|
|
|
1
|
-
Feature: Data import for AutomobileTypeYear
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
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
CHANGED
|
@@ -1,39 +1,39 @@
|
|
|
1
|
-
Feature: Data import for BusClass
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
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
CHANGED
|
@@ -1,114 +1,114 @@
|
|
|
1
|
-
Feature: Data import for BusFuel
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
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
|