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

Test get-kvp-core-req41 is failing on Beta environment #113

Closed
dstenger opened this issue Sep 1, 2022 · 3 comments · Fixed by #114
Closed

Test get-kvp-core-req41 is failing on Beta environment #113

dstenger opened this issue Sep 1, 2022 · 3 comments · Fixed by #114
Assignees
Labels
Projects
Milestone

Comments

@dstenger
Copy link
Contributor

dstenger commented Sep 1, 2022

Describe the bug
Test get-kvp-core-req41 is failing on Beta environment. No error message is printed and all sub-tests are passing.

This failure is not occurring on Production environment although on both environments test suite version 1.17 is running.

So, the failure might be related to the update of the TEAM Engine version (5.5.2) on Beta.

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://cite.ogc.org/te2/.
  2. Execute WFS 2.0 test suite with endpoint http://ows.eox.at/cite/mapserver?service=WCS&version=2.0.1&request=GetCapabilities.
  3. View result of test get-kvp-core-req41.

Expected behavior
It is expected that get-kvp-core-req41 is passing on Beta environment as well (or at least an error message shall be printed).

@dstenger dstenger added the bug label Sep 1, 2022
@dstenger dstenger added this to To do in CITE via automation Sep 1, 2022
@bpross-52n
Copy link
Contributor

This is what I found out:
Actually, the test should also fail on production. At least one of the subtests fails.
This request for example should return an exception containing 'InvalidAxisLabel', which it does not.
So it is an inheritance issue. The behavior of the current beta is at least more correct, imho. The problem is, that each subtest calls another test first (see here, and here) checking for the correct status code. This test passes and the following checks for the exception text (see here) are somehow not taken into account. One quick solution would be to put both checks (statuscode and exception text) in one test. But we should probably have another look at the inheritance, especially with nested tests.

@dstenger dstenger moved this from To do to To verify in CITE Oct 10, 2022
@dstenger dstenger moved this from To verify to In progress in CITE Oct 13, 2022
@dstenger
Copy link
Contributor Author

Next steps:

  • Create unit tests in TEAM Engine to reproduce the failure.
  • Fix the problem either in TEAM Engine or by refactoring the test suite.

@dstenger
Copy link
Contributor Author

dstenger commented Nov 3, 2022

An issue was created for TEAM Engine: opengeospatial/teamengine#560

dstenger added a commit that referenced this issue Nov 14, 2022
CITE automation moved this from To verify to Done Nov 14, 2022
@dstenger dstenger added this to the 1.18 milestone Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
CITE
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants