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

Simplify detecting test failures #242

Open
captaincoordinates opened this issue Jun 18, 2024 · 2 comments
Open

Simplify detecting test failures #242

captaincoordinates opened this issue Jun 18, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@captaincoordinates
Copy link

Is your feature request related to a problem? Please describe.
It is not clear to me how to properly identify CITE test failures in an automated environment. I believe it's currently necessary to parse the XML results file to identify failures. This GitHub Actions workflow file appears to show how tests can be run as part of a CI pipeline, but does not appear to fail following a negative test result. It also appears that this action has never been run, and I cannot find a file called parsetestresults.py anywhere (even though I'm not sure it would be useful).

Ultimately I would like to run CITE compliance tests as part of a CI test suite so that compliance failures can block an automated deployment.

Describe the solution you'd like
java -jar ets-ogcapi-features10-1.8-SNAPSHOT-aio.jar... should vary its exit code based on test results. If any tests fail it should exit non-zero.

Describe alternatives you've considered
Better documentation of how to identify test failures in an automated environment.

@dstenger dstenger self-assigned this Jun 19, 2024
@dstenger dstenger added the enhancement New feature or request label Jun 19, 2024
@dstenger
Copy link
Contributor

Thank you for the feedback.

Please see chapter "Output formats" of https://opengeospatial.github.io/teamengine/users.html for a description of the different output formats.

In general, there are different ways how to execute the test suite (e.g. REST interface or command line). Using the *aio.jar is one of those options.

My proposal is to parse the EARL output to retrieve the passed and failed tests. As far as I know, there is unfortunately no script provided by the CITE team which is executing the parsing. One reason is that this can be done with any programming language.
If you are writing such a script, we would really appreciate it if you can share your work.

@dstenger dstenger removed their assignment Jun 19, 2024
@captaincoordinates
Copy link
Author

Thanks, I'll post back here if I put a script together for this

@dstenger dstenger added this to CITE Aug 1, 2024
@dstenger dstenger moved this to Waiting in CITE Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Waiting
Development

No branches or pull requests

2 participants