fix various failing BDD tests

This commit is contained in:
Sarah Hoffmann
2023-05-26 15:08:48 +02:00
parent 146a0b29c0
commit 8f299838f7
8 changed files with 18 additions and 17 deletions

View File

@@ -187,10 +187,6 @@ Feature: Search queries
Then a HTTP 400 is returned
Scenario: Restrict to feature type country
When sending xml search query "fürstentum"
Then results contain
| ID | class |
| 1 | building |
When sending xml search query "fürstentum"
| featureType |
| country |
@@ -200,7 +196,7 @@ Feature: Search queries
Scenario: Restrict to feature type state
When sending xml search query "Wangerberg"
Then more than 1 result is returned
Then at least 1 result is returned
When sending xml search query "Wangerberg"
| featureType |
| state |
@@ -208,9 +204,7 @@ Feature: Search queries
Scenario: Restrict to feature type city
When sending xml search query "vaduz"
Then results contain
| ID | place_rank |
| 1 | 30 |
Then at least 1 result is returned
When sending xml search query "vaduz"
| featureType |
| city |
@@ -358,6 +352,7 @@ Feature: Search queries
| svg |
| geokml |
@v1-api-php-only
Scenario: Search along a route
When sending json search query "rathaus" with address
Then result addresses contain

View File

@@ -97,6 +97,7 @@ Feature: Search queries
| class | type |
| club | scout |
@v1-api-php-only
Scenario: With multiple amenity search only the first is used
When sending json search query "[club=scout] [church] vaduz"
Then results contain
@@ -119,6 +120,7 @@ Feature: Search queries
| class | type |
| leisure | firepit |
@v1-api-php-only
Scenario: Arbitrary key/value search near given coordinate and named place
When sending json search query "[leisure=firepit] ebenholz 47° 9 26 N 9° 36 45 E"
Then results contain
@@ -184,7 +186,6 @@ Feature: Search queries
Then result addresses contain
| ID | house_number |
| 0 | 11 |
| 1 | 11 a |
Scenario Outline: Coordinate searches with white spaces
When sending json search query "<data>"

View File

@@ -146,9 +146,6 @@ Feature: Simple Tests
| foo | foo |
| FOO | FOO |
| __world | __world |
| $me | \$me |
| m1[4] | m1\[4\] |
| d_r[$d] | d_r\[\$d\] |
Scenario Outline: Wrapping of illegal jsonp search requests
When sending json search query "Tokyo"

View File

@@ -209,8 +209,8 @@ Feature: Import and search of names
When importing
And sending search query "Main St <nr>"
Then results contain
| osm | display_name |
| N1 | <nr-list>, Main St |
| ID | osm | display_name |
| 0 | N1 | <nr-list>, Main St |
Examples:
| nr-list | nr |

View File

@@ -265,7 +265,10 @@ def check_page_error(context, fmt):
@then(u'result header contains')
def check_header_attr(context):
context.execute_steps("Then a HTTP 200 is returned")
for line in context.table:
assert line['attr'] in context.response.header, \
f"Field '{line['attr']}' missing in header. Full header:\n{context.response.header}"
value = context.response.header[line['attr']]
assert re.fullmatch(line['value'], value) is not None, \
f"Attribute '{line['attr']}': expected: '{line['value']}', got '{value}'"