Open-Harbor/osrm-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

clean cucumber comments, fixes 'file to long' problem with latest version of cucumber

Browse Source
This commit is contained in:
Emil Tin 2014-03-27 21:46:53 +01:00
parent 65e020a627
commit 5f7065848e
26 changed files with 52 additions and 54 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
features/bicycle/access.feature
View File

@ -1,6 +1,6 @@
@routing @bicycle @access
Feature: Bike - Access tags on ways
Reference: http://wiki.openstreetmap.org/wiki/Key:access
# Reference: http://wiki.openstreetmap.org/wiki/Key:access
Background:
Given the profile "bicycle"

2
features/bicycle/access_node.feature
View File

@ -1,6 +1,6 @@
@routing @bicycle @access
Feature: Bike - Access tags on nodes
Reference: http://wiki.openstreetmap.org/wiki/Key:access
# Reference: http://wiki.openstreetmap.org/wiki/Key:access
Background:
Given the profile "bicycle"

2
features/bicycle/cycleway.feature
View File

@ -1,6 +1,6 @@
@routing @bicycle @cycleway
Feature: Bike - Cycle tracks/lanes
Reference: http://wiki.openstreetmap.org/wiki/Key:cycleway
# Reference: http://wiki.openstreetmap.org/wiki/Key:cycleway
Background:
Given the profile "bicycle"

4
features/bicycle/oneway.feature
View File

@ -1,7 +1,7 @@
@routing @bicycle @oneway
Feature: Bike - Oneway streets
Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
Usually we can push bikes against oneways, but we use foot=no to prevent this in these tests
# Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
# Usually we can push bikes against oneways, but we use foot=no to prevent this in these tests
Background:
Given the profile "bicycle"

4
features/bicycle/restrictions.feature
View File

@ -1,7 +1,7 @@
@routing @bicycle @restrictions
Feature: Bike - Turn restrictions
Ignore turn restrictions on bicycle, since you always become a temporary pedestrian.
Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
# Ignore turn restrictions on bicycle, since you always become a temporary pedestrian.
# Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
Background:
Given the profile "bicycle"

4
features/bicycle/stop_area.feature
View File

@ -1,7 +1,7 @@
@routing @bicycle @stop_area @todo
Feature: Bike - Stop areas for public transport
Platforms and railway/bus lines are connected using a relation rather that a way, as specified in:
http://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_area
# Platforms and railway/bus lines are connected using a relation rather that a way, as specified in:
# http://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_area
Background:
Given the profile "bicycle"

2
features/bicycle/train.feature
View File

@ -1,6 +1,6 @@
@routing @bicycle @train
Feature: Bike - Handle ferry routes
Bringing bikes on trains and subways
# Bringing bikes on trains and subways
Background:
Given the profile "bicycle"

4
features/bicycle/way.feature
View File

@ -5,8 +5,8 @@ Feature: Bike - Accessability of different way types
Given the profile "bicycle"
Scenario: Bike - Routability of way types
Bikes are allowed on footways etc because you can pull your bike at a lower speed.
Pier is not allowed, since it's tagged using man_made=pier.
# Bikes are allowed on footways etc because you can pull your bike at a lower speed.
# Pier is not allowed, since it's tagged using man_made=pier.
Then routability should be
| highway | bothw |

2
features/car/access.feature
View File

@ -1,6 +1,6 @@
@routing @car @access
Feature: Car - Restricted access
Reference: http://wiki.openstreetmap.org/wiki/Key:access
# Reference: http://wiki.openstreetmap.org/wiki/Key:access
Background:
Given the profile "car"

2
features/car/oneway.feature
View File

@ -1,6 +1,6 @@
@routing @car @oneway
Feature: Car - Oneway streets
Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
# Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
Background:
Given the profile "car"

4
features/car/restrictions.feature
View File

@ -1,7 +1,7 @@
@routing @car @restrictions
Feature: Car - Turn restrictions
Handle turn restrictions as defined by http://wiki.openstreetmap.org/wiki/Relation:restriction
Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
# Handle turn restrictions as defined by http://wiki.openstreetmap.org/wiki/Relation:restriction
# Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
Background: Use car routing
Given the profile "car"

2
features/foot/access.feature
View File

@ -1,6 +1,6 @@
@routing @foot @access
Feature: Foot - Access tags on ways
Reference: http://wiki.openstreetmap.org/wiki/Key:access
# Reference: http://wiki.openstreetmap.org/wiki/Key:access
Background:
Given the profile "foot"

2
features/foot/access_node.feature
View File

@ -1,6 +1,6 @@
@routing @foot @access
Feature: Foot - Access tags on nodes
Reference: http://wiki.openstreetmap.org/wiki/Key:access
# Reference: http://wiki.openstreetmap.org/wiki/Key:access
Background:
Given the profile "foot"

2
features/foot/oneway.feature
View File

@ -1,6 +1,6 @@
@routing @foot @oneway
Feature: Foot - Oneway streets
Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
# Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
Background:
Given the profile "foot"

2
features/foot/restrictions.feature
View File

@ -1,6 +1,6 @@
@routing @foot @restrictions
Feature: Foot - Turn restrictions
Ignore turn restrictions on foot.
# Ignore turn restrictions on foot.
Background:
Given the profile "foot"

4
features/foot/roundabout.feature
View File

@ -6,8 +6,8 @@ Feature: Roundabout Instructions
@todo
Scenario: Foot - Roundabout instructions
You can walk in both directions on a roundabout, bu the normal roundabout instructions don't
make sense when you're going the opposite way around the roundabout.
# You can walk in both directions on a roundabout, bu the normal roundabout instructions don't
# make sense when you're going the opposite way around the roundabout.
Given the node map
| | | v | | |

12
features/options/files.feature
View File

@ -1,11 +1,11 @@
@routing @options @files
Feature: Command line options: files
Normally when launching osrm-routed, it will keep running as a server until it's shut down.
For testing program options, the --trial option is used, which causes osrm-routed to quit
immediately after initialization. This makes testing easier and faster.
The {base} part of the options to osrm-routed will be expanded to the actual base path of
the preprocessed file.
# Normally when launching osrm-routed, it will keep running as a server until it's shut down.
# For testing program options, the --trial option is used, which causes osrm-routed to quit
# immediately after initialization. This makes testing easier and faster.
#
# The {base} part of the options to osrm-routed will be expanded to the actual base path of
# the preprocessed file.
Background:
Given the profile "testbot"

4
features/testbot/bad.feature
View File

@ -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 |

8
features/testbot/bearing.feature
View File

@ -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
features/testbot/example.feature
View File

@ -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

11
features/testbot/impedance.feature
View File

@ -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 |

2
features/testbot/penalty.feature
View File

@ -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"

12
features/testbot/projection.feature
View File

@ -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

2
features/testbot/routes.feature
View File

@ -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 | | | |

8
features/testbot/time.feature
View File

@ -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"

2
features/testbot/turns.feature
View File

@ -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 |