This project contains tests extracted from Quarkus main project using the Quarkus Test Extractor tool. Tests extracted for Quarkus 3.15.3.1 based on its tag must pass when run with Quarkus artifacts of the same version. In other words, if you need to run these tests with different build of Quarkus than is found in Maven central, like with artifacts delivered as Maven repository zip file, you can.
This project has Git branches that matches Quarkus releases. For example Quarkus release https://github.com/quarkusio/quarkus/releases/tag/3.15.3.1 matches Git branch 3.15.3.1. You should expect that existing branches has a counterpart among Quarkus releases. We may and will delete some branches when we don't need them anymore.
There are 3 ways to extract tests:
- Daily build runs a GitHub workflow that detects new releases and extract tests automatically.
- You can trigger the Extract Quarkus tests for given release tag workflow manually for any Quarkus release tag
- Use the Quarkus Test Extractor tool from your workstation and push tests yourselves.
Don't push extracted tests to the main branch because it is next to impossible to keep it up to date with the Quarkus main branch (and there is no point to it).
If you adjusted the Quarkus Test Extractor tool and need to update tests in certain branch, just delete the branch you need to regenerate and trigger the daily.yaml workflow manually.
It should be possible to use the Extract Quarkus tests for given release tag workflow without deleting respective branch and/or tag.
The previous tests will be completely replaced by the new ones.