remove special casing for legacy tokenizer from BDD tests

[nominatim.git] / test / bdd / db / query / postcodes.feature

diff --git a/test/bdd/db/query/postcodes.feature b/test/bdd/db/query/postcodes.feature
index 9f0249594a03ce50c0ac7d266479155ef307b9f0..e8a2ccc2bb8fde4b24ebfeaf9c73ce69f7256e89 100644 (file)
--- a/test/bdd/db/query/postcodes.feature
+++ b/test/bdd/db/query/postcodes.feature
@@ -14,7 +14,6 @@ Feature: Querying fo postcode variants
             | 0  | postcode | 399174, Singapore |
 
 
-    @fail-legacy
     Scenario Outline: Postcodes in the Netherlands (mixed postcode with spaces)
         Given the grid with origin NL
             | 10 |   |   |   | 11 |
@@ -38,7 +37,6 @@ Feature: Querying fo postcode variants
             | 3993 dx  |
 
 
-    @fail-legacy
     Scenario: Postcodes in Singapore (6-digit postcode)
         Given the grid with origin SG
             | 10 |   |   |   | 11 |
@@ -52,7 +50,6 @@ Feature: Querying fo postcode variants
             | 0  | postcode | 399174, Singapore       |
 
 
-    @fail-legacy
     Scenario Outline: Postcodes in Andorra (with country code)
         Given the grid with origin AD
             | 10 |   |   |   | 11 |
@@ -96,8 +93,6 @@ Feature: Querying fo postcode variants
            | postcode | E4 7EA, United Kingdom |
 
 
-    @fail-legacy
-    @v1-api-python-only
     Scenario: Postcode areas are preferred over postcode points
         Given the grid with origin DE
             | 1 | 2 |