earth 0.3.9 → 0.3.10
Sign up to get free protection for your applications and to get access to all the features.
- data/Gemfile +5 -0
- data/Gemfile.lock +58 -20
- data/features/automobile_fuel_type.feature +44 -0
- data/features/automobile_make.feature +24 -0
- data/features/automobile_make_fleet_year.feature +44 -0
- data/features/automobile_make_model.feature +24 -0
- data/features/automobile_make_model_year.feature +34 -0
- data/features/automobile_make_model_year_variant.feature +46 -0
- data/features/automobile_make_year.feature +44 -0
- data/features/automobile_size_class.feature +59 -0
- data/features/bus_class.feature +69 -0
- data/features/carrier.feature +64 -0
- data/features/carrier_mode.feature +74 -0
- data/features/egrid_region.feature +14 -0
- data/features/egrid_subregion.feature +36 -0
- data/features/rail_class.feature +64 -0
- data/features/shipment_mode.feature +34 -0
- data/features/support/env.rb +7 -0
- data/features/support/imports/automobile_fuel_type_bad.csv +3 -0
- data/features/support/imports/automobile_fuel_type_good.csv +3 -0
- data/features/support/imports/automobile_make_bad.csv +3 -0
- data/features/support/imports/automobile_make_fleet_year_bad.csv +3 -0
- data/features/support/imports/automobile_make_fleet_year_good.csv +3 -0
- data/features/support/imports/automobile_make_good.csv +3 -0
- data/features/support/imports/automobile_make_model_bad.csv +3 -0
- data/features/support/imports/automobile_make_model_good.csv +3 -0
- data/features/support/imports/automobile_make_model_year_bad.csv +3 -0
- data/features/support/imports/automobile_make_model_year_good.csv +3 -0
- data/features/support/imports/automobile_make_model_year_variant_bad.csv +3 -0
- data/features/support/imports/automobile_make_model_year_variant_good.csv +3 -0
- data/features/support/imports/automobile_make_year_bad.csv +3 -0
- data/features/support/imports/automobile_make_year_good.csv +3 -0
- data/features/support/imports/automobile_size_class_bad.csv +3 -0
- data/features/support/imports/automobile_size_class_good.csv +3 -0
- data/features/support/imports/bus_class_bad.csv +3 -0
- data/features/support/imports/bus_class_good.csv +3 -0
- data/features/support/imports/carrier_bad.csv +3 -0
- data/features/support/imports/carrier_good.csv +3 -0
- data/features/support/imports/carrier_mode_bad.csv +3 -0
- data/features/support/imports/carrier_mode_good.csv +3 -0
- data/features/support/imports/egrid_region_bad.csv +3 -0
- data/features/support/imports/egrid_region_good.csv +3 -0
- data/features/support/imports/egrid_subregion_bad.csv +3 -0
- data/features/support/imports/egrid_subregion_good.csv +3 -0
- data/features/support/imports/rail_class_bad.csv +3 -0
- data/features/support/imports/rail_class_good.csv +3 -0
- data/features/support/imports/shipment_mode_bad.csv +3 -0
- data/features/support/imports/shipment_mode_good.csv +3 -0
- data/lib/earth/automobile/automobile_fuel_type/data_miner.rb +35 -14
- data/lib/earth/automobile/automobile_make/data_miner.rb +24 -9
- data/lib/earth/automobile/automobile_make_fleet_year/data_miner.rb +32 -1
- data/lib/earth/automobile/automobile_make_model/data_miner.rb +27 -5
- data/lib/earth/automobile/automobile_make_model_year/data_miner.rb +35 -5
- data/lib/earth/automobile/automobile_make_model_year_variant/data_miner.rb +80 -39
- data/lib/earth/automobile/automobile_make_year/data_miner.rb +32 -1
- data/lib/earth/automobile/automobile_size_class/data_miner.rb +67 -4
- data/lib/earth/bus/bus_class/data_miner.rb +73 -0
- data/lib/earth/locality/egrid_region/data_miner.rb +8 -0
- data/lib/earth/locality/egrid_subregion/data_miner.rb +26 -0
- data/lib/earth/rail/rail_class/data_miner.rb +51 -0
- data/lib/earth/shipping/carrier/data_miner.rb +47 -8
- data/lib/earth/shipping/carrier_mode/data_miner.rb +57 -8
- data/lib/earth/shipping/shipment_mode/data_miner.rb +23 -4
- metadata +110 -98
@@ -0,0 +1,69 @@
|
|
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 distance, passengers, speed, and diesel intensity are greater than zero
|
7
|
+
Given a "BusClass" data import fetches results listed in "bus_class_good"
|
8
|
+
When a data import verifies "Distance, passengers, speed, and diesel intensity should be greater than zero"
|
9
|
+
Then the verification should be successful
|
10
|
+
|
11
|
+
Scenario: Successfully verifying that alternative fuels intensity and air conditioning emission factor are zero or more
|
12
|
+
Given a "BusClass" data import fetches results listed in "bus_class_good"
|
13
|
+
When a data import verifies "Alternative fuels intensity and air conditioning emission factor should be zero or more"
|
14
|
+
Then the verification should be successful
|
15
|
+
|
16
|
+
Scenario: Successfully verifying that distance units are kilometres
|
17
|
+
Given a "BusClass" data import fetches results listed in "bus_class_good"
|
18
|
+
When a data import verifies "Distance units should be kilometres"
|
19
|
+
Then the verification should be successful
|
20
|
+
|
21
|
+
Scenario: Successfully verifying that speed units are kilometres per hour
|
22
|
+
Given a "BusClass" data import fetches results listed in "bus_class_good"
|
23
|
+
When a data import verifies "Speed units should be kilometres per hour"
|
24
|
+
Then the verification should be successful
|
25
|
+
|
26
|
+
Scenario: Successfully verifying that diesel intensity and alternative fuels intensity units are litres per kilometre
|
27
|
+
Given a "BusClass" data import fetches results listed in "bus_class_good"
|
28
|
+
When a data import verifies "Diesel intensity and alternative fuel intensity units should be litres per kilometre"
|
29
|
+
Then the verification should be successful
|
30
|
+
|
31
|
+
Scenario: Successfully verifying that air conditioning emission factor units are kilograms per kilometre
|
32
|
+
Given a "BusClass" data import fetches results listed in "bus_class_good"
|
33
|
+
When a data import verifies "Air conditioning emission factor units should be kilograms per kilometre"
|
34
|
+
Then the verification should be successful
|
35
|
+
|
36
|
+
Scenario: Successfully verifying that fallbacks satisfy same criteria as data
|
37
|
+
Given a "BusClass" data import fetches results listed in "bus_class_good"
|
38
|
+
When a data import verifies "Fallbacks should satisfy same constraints as data"
|
39
|
+
Then the verification should be successful
|
40
|
+
|
41
|
+
Scenario: Failing to verify that distance, passengers, speed, and diesel intensity are greater than zero
|
42
|
+
Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
43
|
+
When a data import verifies "Distance, passengers, speed, and diesel intensity should be greater than zero"
|
44
|
+
Then the verification should not be successful
|
45
|
+
|
46
|
+
Scenario: Failing to verify that alternative fuels intensity and air conditioning emission factor are zero or more
|
47
|
+
Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
48
|
+
When a data import verifies "Alternative fuels intensity and air conditioning emission factor should be zero or more"
|
49
|
+
Then the verification should not be successful
|
50
|
+
|
51
|
+
Scenario: Failing to verify that distance units are kilometres
|
52
|
+
Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
53
|
+
When a data import verifies "Distance units should be kilometres"
|
54
|
+
Then the verification should not be successful
|
55
|
+
|
56
|
+
Scenario: Failing to verify that speed units are kilometres per hour
|
57
|
+
Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
58
|
+
When a data import verifies "Speed units should be kilometres per hour"
|
59
|
+
Then the verification should not be successful
|
60
|
+
|
61
|
+
Scenario: Failing to verify that diesel intensity and alternative fuels intensity units are litres per kilometre
|
62
|
+
Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
63
|
+
When a data import verifies "Diesel intensity and alternative fuel intensity units should be litres per kilometre"
|
64
|
+
Then the verification should not be successful
|
65
|
+
|
66
|
+
Scenario: Failing to verify that air conditioning emission factor units are kilograms per kilometre
|
67
|
+
Given a "BusClass" data import fetches results listed in "bus_class_bad"
|
68
|
+
When a data import verifies "Air conditioning emission factor units should be kilograms per kilometre"
|
69
|
+
Then the verification should not be successful
|
@@ -0,0 +1,64 @@
|
|
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
|
@@ -0,0 +1,74 @@
|
|
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 include in fallbacks is never missing
|
27
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
28
|
+
When a data import verifies "Include in fallbacks should never be missing"
|
29
|
+
Then the verification should be successful
|
30
|
+
|
31
|
+
Scenario: Failing to verify that include in fallbacks is never missing
|
32
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
33
|
+
When a data import verifies "Include in fallbacks 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 route inefficiency factor >= 1
|
47
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
48
|
+
When a data import verifies "Route inefficiency factor should be one or more"
|
49
|
+
Then the verification should be successful
|
50
|
+
|
51
|
+
Scenario: Failing to verify that route inefficiency factor >= 1
|
52
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
53
|
+
When a data import verifies "Route inefficiency factor should be one or more"
|
54
|
+
Then the verification should not be successful
|
55
|
+
|
56
|
+
Scenario: Successfully verifying that transport emission factor > 0
|
57
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
58
|
+
When a data import verifies "Transport emission factor should be greater than zero"
|
59
|
+
Then the verification should be successful
|
60
|
+
|
61
|
+
Scenario: Failing to verify that transport emission factor > 0
|
62
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
63
|
+
When a data import verifies "Transport emission factor should be greater than zero"
|
64
|
+
Then the verification should not be successful
|
65
|
+
|
66
|
+
Scenario: Successfully verifying that transport emission factor units is never missing
|
67
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_good"
|
68
|
+
When a data import verifies "Transport emission factor units should never be missing"
|
69
|
+
Then the verification should be successful
|
70
|
+
|
71
|
+
Scenario: Failing to verify that transport emission factor units is never missing
|
72
|
+
Given a "CarrierMode" data import fetches results listed in "carrier_mode_bad"
|
73
|
+
When a data import verifies "Transport emission factor units should never be missing"
|
74
|
+
Then the verification should not be successful
|
@@ -0,0 +1,14 @@
|
|
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
|
+
Scenario: Failing to verify that loss factor is greater than zero and less than one
|
12
|
+
Given a "EgridRegion" data import fetches results listed in "egrid_region_bad"
|
13
|
+
When a data import verifies "Loss factor should be greater than zero and less than one"
|
14
|
+
Then the verification should not be successful
|
@@ -0,0 +1,36 @@
|
|
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
|
+
# FIXME TODO
|
7
|
+
# Scenario: Successfully verifying that eGRID region name appears in egrid_regions
|
8
|
+
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
9
|
+
# When a data import verifies "eGRID region name should appear in egrid_regions"
|
10
|
+
# Then the verification should be successful
|
11
|
+
|
12
|
+
Scenario: Successfully verifying that electricity emission factor is greater than zero
|
13
|
+
Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
14
|
+
When a data import verifies "Electricity emission factor should be greater than zero"
|
15
|
+
Then the verification should be successful
|
16
|
+
|
17
|
+
Scenario: Successfully verifying that electricity emission factor units are kilograms per kilowatt hour
|
18
|
+
Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_good"
|
19
|
+
When a data import verifies "Electricity emission factor units should be kilograms per kilowatt hour"
|
20
|
+
Then the verification should be successful
|
21
|
+
|
22
|
+
# FIXME TODO
|
23
|
+
# Scenario: Failing to verify that eGRID region name appears in egrid_regions
|
24
|
+
# Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
25
|
+
# When a data import verifies "eGRID region name should appear in egrid_regions"
|
26
|
+
# Then the verification should not be successful
|
27
|
+
|
28
|
+
Scenario: Failing to verify that electricity emission factor is greater than zero
|
29
|
+
Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
30
|
+
When a data import verifies "Electricity emission factor should be greater than zero"
|
31
|
+
Then the verification should not be successful
|
32
|
+
|
33
|
+
Scenario: Failing to verify that electricity emission factor units are kilograms per kilowatt hour
|
34
|
+
Given a "EgridSubregion" data import fetches results listed in "egrid_subregion_bad"
|
35
|
+
When a data import verifies "Electricity emission factor units should be kilograms per kilowatt hour"
|
36
|
+
Then the verification should not be successful
|
@@ -0,0 +1,64 @@
|
|
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
|
@@ -0,0 +1,34 @@
|
|
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
|
@@ -0,0 +1,3 @@
|
|
1
|
+
name,annual_distance,fuel_efficiency_city,fuel_efficiency_highway,hybrid_fuel_efficiency_city_multiplier,hybrid_fuel_efficiency_highway_multiplier,conventional_fuel_efficiency_city_multiplier,conventional_fuel_efficiency_highway_multiplier,annual_distance_units,fuel_efficiency_city_units,fuel_efficiency_highway_units
|
2
|
+
small,1000,10.0,15.0,1.1,1.2,0.9,0.95,kilometres,kilometres_per_litre,kilometres_per_litre
|
3
|
+
large,-100,-1,0,0,-1,0,-10
|