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
[incubator-kie-issues#1104] Migrate Junit inside DMN #5883
Conversation
…1104 # Conflicts: # kie-dmn/kie-dmn-core/src/test/java/org/kie/dmn/core/DMNCompilerTest.java # kie-dmn/kie-dmn-core/src/test/java/org/kie/dmn/core/DMNTypeTest.java
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of the changes on the POM are not well formatted. Aside from that, LGTM!
PS. There are a couple of conflicts
testRoundTrip("org/kie/dmn/backend/marshalling/v1_1/", "dish-decision.xml"); | ||
} | ||
|
||
@Ignore("failing to compare over a xsi:type=\"tImport\" attribute, but why content generated 'control' need to explicit it ?") | ||
@Disabled("failing to compare over a xsi:type=\"tImport\" attribute, but why content generated 'control' need to explicit it ?") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated to this change...But I'm wondering if makes sense to create a new ticket that requires to review of all the disabled tests we have and decide if they deserve a fix or if they should be removed, WDYT?
@Test | ||
public void testTest() throws ScriptException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
xD
* [incubator-kie-issues#1104] Moved to junit 6 /jupiter * [incubator-kie-issues#1104] Fix formatting * [incubator-kie-issues#1104] Fix formatting * [incubator-kie-issues#1104] Fix merge. BAn junit 4 from kie-dmn modules * [incubator-kie-issues#1104] Fix format - attempt * [incubator-kie-issues#1104] Fix xml format --------- Co-authored-by: Gabriele-Cardosi <gabriele.cardosi@ibm.com>
Fixes apache/incubator-kie-issues#1104
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 and downstream checks
for a full downstream build
run_fdb
for Jenkins PR check only
Build Now
button.