TestSuite version on API

[carlospzurita]

As part of the ETF testing framework, that we are using in the INSPIRE Reference Validator, a dependency on the TEAM engine WFS 2.0 TestSuite is used on its own Download Service ExecutableTestSuite. This dependency is managed using the endpoint https://cite.opengeospatial.org/teamengine/rest/suites, and the ETS is assigned the version of the current TestSuite.

We were previously able to obtain the version number directly from the URL of the TestSuite (for example https://cite.opengeospatial.org/teamengine/rest/suites/wfs20/1.34/run). But now the version is gone from this endpoint, and we encountered some errors in the initialization of the TestDriver for this ETS.

What is the easiest way to get the version number for the TestSuite now, using only the REST API?

[dstenger]

The easiest way to get the version number of the test suites is to check following site: https://cite.opengeospatial.org/teamengine/

However, we could think of providing the version numbers of the test suites via the REST interface itself. Would that help you?

CC @ghobona

[carlospzurita]

We are aware of the versioning present in the landing page on https://cite.opengeospatial.org/teamengine/, and we have used it to temporarily set it as a static value on the ETF. However, it would very useful is this could be obtained directly from the REST API, to set it automatically.

[dstenger]

I agree that it could be useful to provide this information directly via the REST API.

We will discuss this in the CITE TEAM.

[keshavnangare]

@dstenger

I think we have covered this in the issue #397 (comment). The PR for the above issue will be used to get the Available test suites information in the XML/JSON format which contains information about the version of the test suite.

[ghobona]

@dstenger Can we add PR #434 , which fixes Issue #397 (comment) , to the Team Engine 5.5 milestone or even a sooner milestone?

[dstenger]

Sure, #397 was added to 5.5 milestone. This will be the next release of TEAM Engine.

[dstenger]

@carlospzurita Does the solution of #397 cover your requirements? If that is the case, I propose to close this issue.

[carlospzurita]

Dear @dstenger

Thank you for your response. I think that this change can be useful for us, we can retrieve the TestSuite info when setting up the validator.

This PR can close this issue, but we would like to be able to test it in the staging instance. Are you planning to merge the PR soon? And do you have an approximate date for the inclusion in production?

Thank you very much.

[dstenger]

We will update TEAM Engine on Production in summer 2021.

[ghobona]

2021-01-13 discussion

We are planning to add this to a v5.4.1 release of TEAM Engine on Beta. This will likely be in Q1 of 2021.

Cc: @dstenger