Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abstract Test 136 seemingly incorrect #138

Open
tiaanwessels opened this issue Oct 23, 2024 · 2 comments · May be fixed by #144
Open

Abstract Test 136 seemingly incorrect #138

tiaanwessels opened this issue Oct 23, 2024 · 2 comments · May be fixed by #144
Assignees

Comments

@tiaanwessels
Copy link

Describe the bug
Abstract Test 136 expects 400 in the response but the OGC EDR specification states under /conf/locations/no-query-params:
Validate that a GeoJSON document was returned with a status code 200 containing at least a list of features one for each location supported by the collection

To Reproduce
Steps to reproduce the behavior:

  1. Run the test case against an implementation with a locations query for a collection that responds with a GeoJSON document and code 200 to see the problem

Expected behavior
I expected a PASS when the service responds with GeoJSON and code 200

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
This is the returned GeoJSON
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"geometry": {
"coordinates": [
21,
52.25
],
"type": "Point"
},
"properties": {
"locationId": "EPWW",
"locationName": "ACC"
}
}
]
}
and this the headers
Request URL:
http://swim:12373/edr/collections/airmet/locations
Request Method:
GET
Status Code:
200 OK
Remote Address:
192.168.51.118:12373
Referrer Policy:
strict-origin-when-cross-origin

and the test result (truncated) looks like

...
@dstenger
Copy link
Collaborator

Thank you for reporting.
I understand your problem and we will check the implementation of the test suite.
Is it possible to provide a public API we can use to reproduce the problem?

@tiaanwessels
Copy link
Author

tiaanwessels commented Oct 23, 2024 via email

@bpross-52n bpross-52n linked a pull request Oct 31, 2024 that will close this issue
@dstenger dstenger assigned dstenger and unassigned bpross-52n Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To verify
Development

Successfully merging a pull request may close this issue.

3 participants