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

REST interface responds differently on local installation and Beta environment #40

Closed
dstenger opened this issue Oct 28, 2020 · 5 comments
Assignees
Projects

Comments

@dstenger
Copy link
Contributor

If following request is sent against Beta environment, 12 tests pass and 0 fail the test suite.

https://cite.opengeospatial.org/te2/rest/suites/sos20/run?service-url=http://sensorweb.demo.52north.org/52n-sos-webapp/service?service=SOS&request=GetCapabilities&AcceptVersions=2.0.0

However, if the same request is sent against a local setup (Docker Image) of the master branch, 88 tests pass and 10 fail the test suite (is also executed by integration-tests).

http://localhost:8081/teamengine/rest/suites/sos20/run?service-url=http://sensorweb.demo.52north.org/52n-sos-webapp/service?service=SOS&request=GetCapabilities&AcceptVersions=2.0.0

Why are both environments behaving differently, although they should return the same result?

@dstenger dstenger added this to To do in CITE via automation Oct 28, 2020
@dstenger dstenger moved this from To do to In progress in CITE Oct 28, 2020
@dstenger dstenger changed the title REST interface responds diffently on local installation and Beta environment REST interface responds differently on local installation and Beta environment Oct 28, 2020
@dstenger
Copy link
Contributor Author

dstenger commented Dec 9, 2020

@dstenger will provide all libraries which are installed on Beta environment to @keshav-nangare so that he can do further analysis.

@dstenger dstenger self-assigned this Dec 9, 2020
@dstenger dstenger removed their assignment Jan 6, 2021
@keshavnangare
Copy link

keshavnangare commented Jan 7, 2021

@dstenger

Following is the workaround:

  1. When the test suite executed on beta environment containing jar of all test suites, the xsd's are mentioned in tests are picked from the sensorml20 jar. The loading path and thrown exception are in error log.txt file.
  2. When the test suite executed on docker environment, there is only sos20 jar is present so it runs all tests.

Possible Solution

  1. The xsd loading from sensorml20 jar is having encoding UTF-16, can be changed to UTF-8.(Fix can be added to ets-sensorml20)

OR

  1. Changed the directory of xsd file in sos20 test suite and its references in the tests(Fix can be added to ets-sos20).

@dstenger
Copy link
Contributor Author

@keshav-nangare Please implement solution 1: Updating of the encoding of the XSD.

@keshavnangare
Copy link

I have created an issue and fixed it by updating the encoding of file in the sensorml20 test suite.

@keshavnangare keshavnangare moved this from In progress to To verify in CITE Jan 12, 2021
@dstenger dstenger assigned dstenger and lgoltz and unassigned keshavnangare Jan 13, 2021
@dstenger
Copy link
Contributor Author

Associated pull request was merged.

CITE automation moved this from To verify to Done Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
CITE
  
Done
Development

No branches or pull requests

3 participants