build: register all CI hapi test task as real Test task - #27011
Draft
jjohannes wants to merge 1 commit into
Draft
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Do no longer have logic based on 'gradle.startParameter.taskNames' checks. Instead, all tasks are registered as 'Test' tasks with the corresponding custom configuration. This has the advantage that (failing) test are associated with the task that runs them. In general, it makes the setup more straight-forward and idiomatic. Signed-off-by: Jendrik Johannes <jendrik@onepiece.software>
jjohannes
force-pushed
the
hapi-tests-build-gradle-refactor-2
branch
from
August 28, 2026 08:42
fc62fef to
73db260
Compare
✅ All tests passed ✅Test Summary600: [FLOW] PR Checks / MATS / HAPI Tests / hapi-tests-misc / HAPI Tests (Misc) > :test-clients:hapiTestMisc
600: [FLOW] PR Checks / MATS / HAPI Tests / hapi-tests-misc-records-crypto-and-serial / HAPI Tests (Misc Records, Crypto & Misc Serial) > :test-clients:hapiTestCrypto
🏷️ Commit: 73db260 Learn more about TestLens at testlens.app/docs. |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #27011 +/- ##
============================================
- Coverage 70.54% 70.54% -0.01%
Complexity 11691 11691
============================================
Files 2586 2586
Lines 108553 108553
Branches 12166 12166
============================================
- Hits 76584 76581 -3
- Misses 27971 27973 +2
- Partials 3998 3999 +1 see 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Do no longer have logic based on
gradle.startParameter.taskNames. Instead, all tasks are registered asTesttasks with the corresponding custom configuration. This has the advantage that (failing) tests are associated with the task that runs them. In general, it makes the setup more straight-forward and idiomatic.The following beahviour changes compared to
main, which does not change how tasks are called from CI:hapiTestCryptois called it runs the tests directly instead of doing an ad-hoc reconfiguration oftestSubprocessand running that../gradlew hapiTestAdhoc hapiTestCryptoboth tasks run and execute their tests. Instead of onetestSubprocesstask that combines the two.Related issue(s):
Follow up to #26945
Notes for reviewer:
Checklist