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

Enable test execution using a RESTful API #84

Closed
keshavnangare opened this issue Sep 5, 2018 · 4 comments · Fixed by #86
Closed

Enable test execution using a RESTful API #84

keshavnangare opened this issue Sep 5, 2018 · 4 comments · Fixed by #86

Comments

@keshavnangare
Copy link

Create an interface to execute CTL test-suite using RESTful API.

Reference: opengeospatial/ets-wms13#34

@lgoltz
Copy link
Contributor

lgoltz commented Oct 17, 2018

@keshav-nangare Ist the fix for opengeospatial/teamengine#362 required?

The name of the tes suite listed with http://localhost:8081/teamengine/rest/suites is currently OGC Web Feature Service 1.1.0 Exectutable Test Suite, Web Feature Service 1.1.0 is more readable.

The list of parameters http://localhost:8081/teamengine/rest/suites/wfs/1.33-SNAPSHOT/ described also the parameter wfs-basic which cannot be disabled. I think this can be removed from the list and described in the test.

@keshavnangare
Copy link
Author

@lgoltz

Yes, teamengine fix opengeospatial/teamengine#362 is required for all the CTL based REST interface implementation.

the parameter wfs-basic which cannot be disabled.

This wfs-basic CC is defined in ctl test itself thats why I have added only for information. I will remove from this list. You can see here how wfs-basic is defined:

<xsl:variable name="conformance.class">basic</xsl:variable>

@lgoltz
Copy link
Contributor

lgoltz commented Oct 17, 2018

@keshavnangare
Copy link
Author

@lgoltz

I have updated the test suite name and removed the wfs-basic parameter from the site overview document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants