clean cucumber comments, fixes 'file to long' problem with latest version of cucumber
This commit is contained in:
Emil Tin
@@ -45,8 +45,8 @@ Feature: Handle bad data in a graceful manner
|
||||
|
||||
@poles
|
||||
Scenario: Routing close to the north/south pole
|
||||
Mercator is undefined close to the poles.
|
||||
All nodes and request with latitude to close to either of the poles should therefore be ignored.
|
||||
# Mercator is undefined close to the poles.
|
||||
# All nodes and request with latitude to close to either of the poles should therefore be ignored.
|
||||
|
||||
Given the node locations
|
||||
| node | lat | lon |
|
||||
|
||||
@@ -141,8 +141,8 @@ Feature: Compass bearing
|
||||
| f | e | abcdef | W | 270 |
|
||||
|
||||
Scenario: Bearings at high latitudes
|
||||
The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
|
||||
to form square with sides of 1 km.
|
||||
# The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
|
||||
# to form square with sides of 1 km.
|
||||
|
||||
Given the node locations
|
||||
| node | lat | lon |
|
||||
@@ -176,8 +176,8 @@ Feature: Compass bearing
|
||||
| d | b | bd | NW | 315 |
|
||||
|
||||
Scenario: Bearings at high negative latitudes
|
||||
The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
|
||||
to form square with sides of 1 km.
|
||||
# The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
|
||||
# to form square with sides of 1 km.
|
||||
|
||||
Given the node locations
|
||||
| node | lat | lon |
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
@routing @testbot @example
|
||||
Feature: Testbot - Walkthrough
|
||||
|
||||
# A complete walk-through of how this data is processed can be found at:
|
||||
# https://github.com/DennisOSRM/Project-OSRM/wiki/Processing-Flow
|
||||
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
@routing @testbot @impedance @todo
|
||||
Feature: Setting impedance and speed separately
|
||||
These tests assume that the speed is not factored into the impedance by OSRM internally.
|
||||
Instead the speed can optionally be factored into the weiht in the lua profile.
|
||||
|
||||
Note: With the default grid size of 100m, the diagonals has a length if 141.42m
|
||||
# These tests assume that the speed is not factored into the impedance by OSRM internally.
|
||||
# Instead the speed can optionally be factored into the weiht in the lua profile.
|
||||
# Note: With the default grid size of 100m, the diagonals has a length if 141.42m
|
||||
|
||||
Background:
|
||||
Given the profile "testbot"
|
||||
@@ -55,8 +54,8 @@ Note: With the default grid size of 100m, the diagonals has a length if 141.42m
|
||||
| c | b | btc |
|
||||
|
||||
Scenario: Use both impedance and speed (multiplied) when picking route
|
||||
OSRM should not factor speed into impedance internally. However, the profile can choose to do so,
|
||||
and this test expect the testbot profile to do it.
|
||||
# OSRM should not factor speed into impedance internally. However, the profile can choose to do so,
|
||||
# and this test expect the testbot profile to do it.
|
||||
Given the node map
|
||||
| | s | | t | |
|
||||
| a | | b | | c |
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
@routing @penalty @signal
|
||||
Feature: Penalties
|
||||
Testbot uses a signal penalty of 7s.
|
||||
# Testbot uses a signal penalty of 7s.
|
||||
|
||||
Background:
|
||||
Given the profile "testbot"
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
@routing @projection
|
||||
Feature: Projection to nearest point on road
|
||||
Waypoints are projected perpendiculary onto the closest road
|
||||
# Waypoints are projected perpendiculary onto the closest road
|
||||
|
||||
Background:
|
||||
The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html
|
||||
The nodes are placed as follows, with ab, bc and bd all being 1 km in length each:
|
||||
| | | c |
|
||||
| | b | | (this is sketch only, real data is in the table below)
|
||||
| a | | d |
|
||||
# The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html
|
||||
# The nodes are placed as follows, with ab, bc and bd all being 1 km in length each:
|
||||
# | | | c |
|
||||
# | | b | | (this is sketch only, real data is in the table below)
|
||||
# | a | | d |
|
||||
|
||||
Given the profile "testbot"
|
||||
Given the node locations
|
||||
|
||||
@@ -5,7 +5,7 @@ Feature: OSM Route Relation
|
||||
Given the profile "testbot"
|
||||
|
||||
Scenario: Prioritize ways that are part of route relations
|
||||
This scenario assumes that the testbot uses an impedance of 0.5 for ways that are part of 'testbot' routes.
|
||||
# This scenario assumes that the testbot uses an impedance of 0.5 for ways that are part of 'testbot' routes.
|
||||
|
||||
Given the node map
|
||||
| s | | | t | | | |
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
@routing @time
|
||||
Feature: Estimation of travel time
|
||||
Testbot speeds:
|
||||
Primary road: 36km/h = 36000m/3600s = 100m/10s
|
||||
Secondary road: 18km/h = 18000m/3600s = 100m/20s
|
||||
Tertiary road: 12km/h = 12000m/3600s = 100m/30s
|
||||
# Testbot speeds:
|
||||
# Primary road: 36km/h = 36000m/3600s = 100m/10s
|
||||
# Secondary road: 18km/h = 18000m/3600s = 100m/20s
|
||||
# Tertiary road: 12km/h = 12000m/3600s = 100m/30s
|
||||
|
||||
Background: Use specific speeds
|
||||
Given the profile "testbot"
|
||||
|
||||
@@ -98,7 +98,7 @@ Feature: Turn directions/codes
|
||||
| g | e | xg,xe | head,sharp_right,destination |
|
||||
|
||||
Scenario: Turn instructions at high latitude
|
||||
https://github.com/DennisOSRM/Project-OSRM/issues/532
|
||||
# https://github.com/DennisOSRM/Project-OSRM/issues/532
|
||||
Given the node locations
|
||||
| node | lat | lon |
|
||||
| a | 55.68740 | 12.52430 |
|
||||
|
||||
Reference in New Issue
Block a user