Disabled python tests that require python3
Merged
WI
9h ago+2+2+0123456789-2-2-0123456789
@khayashi4337 please move the tests to github workflow instead, e.g. create a new one for your tests based on https://github.com/OpenAPITools/openapi-generator/blob/master/.github/workflows/samples-python-fastapi-server.yaml
as unlikely every openapi generator users have python3 installed.
PR checklist
- Read the contribution guidelines.
- Run the following to build the project and update samples:
(For Windows users, please run the script in WSL)./mvnw clean package || exit ./bin/generate-samples.sh ./bin/configs/*.yaml || exit ./bin/utils/export_docs_generators.sh || exit
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./bin/generate-samples.sh bin/configs/java*.
IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed. - If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
Summary by cubic
Disables two Python codegen tests that require a python3 toolchain, so the test suite no longer fails on environments without it.
- The tests are annotated with
enabled = falseand are skipped during CI runs. - Coverage for the underlying behavior (JSON header params and
info.titleembedding) is retained by the test specs themselves; only the compile-time validation is skipped.