-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[7.x][DROOLS-6933] Migrate drools-core tests to assertj #4489
Merged
Conversation
This file contains 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
mariofusco
approved these changes
Jun 27, 2022
pibizza
added a commit
to pibizza/drools
that referenced
this pull request
Mar 9, 2023
* [DROOLS-6933] Migrate drools-core tests to assertj (apache#4436) * [DROOLS-6933] Migrate more drools-core tests to assertj
pibizza
added a commit
to pibizza/drools
that referenced
this pull request
Mar 9, 2023
* [DROOLS-6933] Migrate drools-core tests to assertj (apache#4436) * [DROOLS-6933] Migrate more drools-core tests to assertj
pibizza
added a commit
to pibizza/drools
that referenced
this pull request
Mar 9, 2023
* [DROOLS-6933] Migrate drools-core tests to assertj (apache#4436) * [DROOLS-6933] Migrate more drools-core tests to assertj
mariofusco
pushed a commit
that referenced
this pull request
Mar 16, 2023
… 7.67.x (#5079) * [DROOLS-6917] Remove use of hamcrest in drools tests (#4336) * [DROOLS-6930] Migrate assertNotNull to assertj assertions * [7.x][DROOLS-6931] Migrate assertions in kie-pmml-trusty tests to assertj (#4399) * Migrated assertions from junit to assertj * Making tests better use of assertj * Proper conversion for equalsNode * [7.x][DROOLS-6932] Migrate assertions in kie-dmn tests to assertj (#4435) * [DROOLS-6932] Migrate assertions in kie-dmn tests to assertj * [DROOLS-6932] Fixed code smell in test * [DROOLS-6932] Fixed compilation issue * [7.x][DROOLS-6933] Migrate drools-core tests to assertj (#4489) * [DROOLS-6933] Migrate drools-core tests to assertj (#4436) * [DROOLS-6933] Migrate more drools-core tests to assertj * [7.x][DROOLS-6935] Migrate drools-verifier tests to assertj (#4502) * [DROOLS-6935] Migrate drools-verifier tests to assertj * [DROOLS-6935] Missing cleaning in the code * [DROOLS-6934] Migrate drools-model tests to assertj (#4532) * [7.x][DROOLS-7046] Migrate drools-test-coverage tests to assertj (#4538) * [DROOLS-7046] Migrate drools-test-coverage tests to assertj * [DROOLS-7046] Cleaning up remaing tests in drools-test-coverage * [DROOLS-7053] Migrate remaining tests to assertj (#4540)
mariofusco
pushed a commit
that referenced
this pull request
Mar 16, 2023
….x (#5078) * [DROOLS-6917] Remove use of hamcrest in drools tests (#4336) * [DROOLS-6930] Migrate assertNotNull to assertj assertions * [7.x][DROOLS-6931] Migrate assertions in kie-pmml-trusty tests to assertj (#4399) * Migrated assertions from junit to assertj * Making tests better use of assertj * Proper conversion for equalsNode * [7.x][DROOLS-6932] Migrate assertions in kie-dmn tests to assertj (#4435) * [DROOLS-6932] Migrate assertions in kie-dmn tests to assertj * [DROOLS-6932] Fixed code smell in test * [DROOLS-6932] Fixed compilation issue * [7.x][DROOLS-6933] Migrate drools-core tests to assertj (#4489) * [DROOLS-6933] Migrate drools-core tests to assertj (#4436) * [DROOLS-6933] Migrate more drools-core tests to assertj * [7.x][DROOLS-6935] Migrate drools-verifier tests to assertj (#4502) * [DROOLS-6935] Migrate drools-verifier tests to assertj * [DROOLS-6935] Missing cleaning in the code * [DROOLS-6934] Migrate drools-model tests to assertj (#4532) * [7.x][DROOLS-7046] Migrate drools-test-coverage tests to assertj (#4538) * [DROOLS-7046] Migrate drools-test-coverage tests to assertj * [DROOLS-7046] Cleaning up remaing tests in drools-test-coverage * [DROOLS-7053] Migrate remaining tests to assertj (#4540)
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.
This is backport to 7.x of https://github.com/kiegroup/drools/pull/4436
It includes an extra commit to migrate tests that are only in 7.x.
JIRA: DROOLS-6933
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
for pull request checks
Please add comment: Jenkins retest this
for a specific pull request check
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] tests
for a full downstream build
run_fdb
a compile downstream build please add comment: Jenkins run cdb
a full production downstream build please add comment: Jenkins execute product fdb
an upstream build please add comment: Jenkins run upstream
for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch
for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch
for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main
for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch
for native checks
Run native checks
Please add comment: Jenkins run native
for a specific native check
Run native checks
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native
for mandrel checks
Run native checks against Mandrel image
Please add comment: Jenkins run mandrel
for a specific mandrel check
Run native checks against Mandrel image
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] mandrel