cucumber cleanup, removed unused code

This commit is contained in:
Emil Tin
2012-12-16 13:36:47 +01:00
parent 7e9614b9ec
commit ec56478a3c
51 changed files with 187 additions and 349 deletions
+1 -1
View File
@@ -3,7 +3,7 @@ Feature: Bike - Restricted access
Reference: http://wiki.openstreetmap.org/wiki/Key:access
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Access tag hierachy on ways
Then routability should be
+1 -1
View File
@@ -2,7 +2,7 @@
Feature: Bike - Squares and other areas
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
@square
Scenario: Bike - Route along edge of a squares
+1 -1
View File
@@ -2,7 +2,7 @@
Feature: Barriers
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Barriers
Then routability should be
+1 -1
View File
@@ -3,7 +3,7 @@ Feature: Bike - Cycle tracks/lanes
Reference: http://wiki.openstreetmap.org/wiki/Key:cycleway
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Cycle tracks/lanes should enable biking
Then routability should be
+1 -1
View File
@@ -2,7 +2,7 @@
Feature: Bike - Destination only, no passing through
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Destination only street
Given the node map
+1 -1
View File
@@ -2,7 +2,7 @@
Feature: Bike - Handle ferry routes
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Ferry route
Given the node map
+1 -1
View File
@@ -2,7 +2,7 @@
Feature: Bike - Max speed restrictions
Background: Use specific speeds
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Respect maxspeeds when lower that way type speed
Given the node map
+1 -1
View File
@@ -2,7 +2,7 @@
Feature: Bike - Street names in instructions
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - A named street
Given the node map
+1 -1
View File
@@ -3,7 +3,7 @@ Feature: Bike - Oneway streets
Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Simple oneway
Then routability should be
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: Bike - Turn restrictions
Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
Background: Use car routing
Given the speedprofile "bicycle"
Given the profile "bicycle"
@no_turning
Scenario: Bike - No left turn
+1 -1
View File
@@ -4,7 +4,7 @@ Platforms and railway/bus lines are connected using a relation rather that a way
http://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_area
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Platforms tagged using public_transport
Then routability should be
+1 -1
View File
@@ -3,7 +3,7 @@ Feature: Bike - Handle ferry routes
Bringing bikes on trains and subways
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Bringing bikes on trains
Then routability should be
+2 -2
View File
@@ -2,11 +2,11 @@
Feature: Bike - Accessability of different way types
Background:
Given the speedprofile "bicycle"
Given the profile "bicycle"
Scenario: Bike - Basic access
Bikes are allowed on footways etc because you can pull your bike at a lower speed.
Given the speedprofile "bicycle"
Given the profile "bicycle"
Then routability should be
| highway | forw |
| (nil) | |