bdd: remove special case for osm_type field

The fuzzy field check hide cover formatting errors. Use 'osm' when
only caring about the conent.
This commit is contained in:
Sarah Hoffmann
2023-03-09 17:44:34 +01:00
parent da0a7a765e
commit 01010e443f
6 changed files with 48 additions and 50 deletions

View File

@@ -273,12 +273,12 @@ Feature: Import of address interpolations
| W3 | 14 | 14 |
When sending search query "16 Cloud Street"
Then results contain
| ID | osm_type | osm_id |
| 0 | N | 4 |
| ID | osm |
| 0 | N4 |
When sending search query "14 Cloud Street"
Then results contain
| ID | osm_type | osm_id |
| 0 | W | 11 |
| ID | osm |
| 0 | W11 |
Scenario: addr:street on housenumber way
Given the grid
@@ -318,12 +318,12 @@ Feature: Import of address interpolations
| W3 | 14 | 14 |
When sending search query "16 Cloud Street"
Then results contain
| ID | osm_type | osm_id |
| 0 | N | 4 |
| ID | osm |
| 0 | N4 |
When sending search query "14 Cloud Street"
Then results contain
| ID | osm_type | osm_id |
| 0 | W | 11 |
| ID | osm |
| 0 | W11 |
Scenario: Geometry of points and way don't match (github #253)
Given the places
@@ -401,8 +401,8 @@ Feature: Import of address interpolations
| 2 | 8 | 10,11 |
When sending jsonv2 reverse coordinates 1,1
Then results contain
| ID | osm_type | osm_id | type | display_name |
| 0 | node | 1 | house | 0 |
| ID | osm | type | display_name |
| 0 | N1 | house | 0 |
Scenario: Parenting of interpolation with additional tags
Given the grid

View File

@@ -55,8 +55,8 @@ Feature: Linking of places
| R23 | - |
When sending search query "rhein"
Then results contain
| osm_type |
| R |
| osm |
| R13 |
Scenario: Relations are not linked when in waterway relations
Given the grid
@@ -81,9 +81,9 @@ Feature: Linking of places
| R2 | - |
When sending search query "rhein"
Then results contain
| ID | osm_type |
| 0 | R |
| 1 | W |
| ID | osm |
| 0 | R1 |
| 1 | W2 |
Scenario: Empty waterway relations are handled correctly
@@ -138,8 +138,8 @@ Feature: Linking of places
| W2 | R1 |
When sending search query "rhein2"
Then results contain
| osm_type |
| W |
| osm |
| W1 |
# github #573
Scenario: Boundaries should only be linked to places
@@ -205,14 +205,14 @@ Feature: Linking of places
| city |
| Berlin |
Then results contain
| ID | osm_type | osm_id |
| 0 | R | 13 |
| ID | osm |
| 0 | R13 |
When sending search query ""
| state |
| Berlin |
Then results contain
| ID | osm_type | osm_id |
| 0 | R | 13 |
| ID | osm |
| 0 | R13 |
Scenario: Boundaries without place tags only link against same admin level
@@ -237,14 +237,14 @@ Feature: Linking of places
| state |
| Berlin |
Then results contain
| ID | osm_type | osm_id |
| 0 | R | 13 |
| ID | osm |
| 0 | R13 |
When sending search query ""
| city |
| Berlin |
Then results contain
| ID | osm_type | osm_id |
| 0 | N | 2 |
| ID | osm |
| 0 | N2 |
# github #1352
Scenario: Do not use linked centroid when it is outside the area

View File

@@ -23,12 +23,12 @@ Feature: Parenting of objects
| N2 | W1 |
When sending search query "4 galoo"
Then results contain
| ID | osm_type | osm_id | display_name |
| 0 | N | 1 | 4, galoo, 12345, Deutschland |
| ID | osm | display_name |
| 0 | N1 | 4, galoo, 12345, Deutschland |
When sending search query "5 galoo"
Then results contain
| ID | osm_type | osm_id | display_name |
| 0 | N | 2 | 5, galoo, 99999, Deutschland |
| ID | osm | display_name |
| 0 | N2 | 5, galoo, 99999, Deutschland |
Scenario: Address without tags, closest street
Given the grid