RouteWayCostUnitConverter: Snap values between 0–1 to 16404-way-costs--snap-distance-and-time-to-1-when-between-0-a

We use integer values for distance (kilometres) and time (minutes). If
the values aren't very big, like bus stops inside a city for example,
the integer conversion will put distance and time at `0`, which isn't
correct.

To continue to use our chosen measurement units while still displaying
something that makes sense to users, snap any values >0 and <=1 to `1`.

Refs #6404

1 files changed, 28 insertions, 0 deletions

diff --git a/spec/lib/route_way_cost_unit_converter_spec.rb b/spec/lib/route_way_cost_unit_converter_spec.rb
index 3c5e51710..aa25d57d2 100644
--- a/spec/lib/route_way_cost_unit_converter_spec.rb
+++ b/spec/lib/route_way_cost_unit_converter_spec.rb
@@ -35,4 +35,32 @@ RSpec.describe RouteWayCostUnitConverter do
       })
     end
   end
+
+  describe ".meters_to_kilometers" do
+    it "converts meters to integer kilometres" do
+      expect(
+        RouteWayCostUnitConverter.meters_to_kilometers(6350)
+      ).to eq(6)
+    end
+
+    it "snaps values between 0 and 1 to 1" do
+      expect(
+        RouteWayCostUnitConverter.meters_to_kilometers(50)
+      ).to eq(1)
+    end
+  end
+
+  describe ".seconds_to_minutes" do
+    it "converts seconds to minutes" do
+      expect(
+        RouteWayCostUnitConverter.seconds_to_minutes(300)
+      ).to eq(5)
+    end
+
+    it "snaps values between 0 and 1 to 1" do
+      expect(
+        RouteWayCostUnitConverter.seconds_to_minutes(3)
+      ).to eq(1)
+    end
+  end
 end