Abhitocode opened a new pull request, #3635:
URL: https://github.com/apache/incubator-kie-kogito-runtimes/pull/3635

   Issue's with **testEventBasedSplit3** and **testEventBaedSplit5** tests 
within IntermediateEventTest.java
   
   The test can be identified by referring to IntermediateEventTest.java:
   
https://github.com/apache/incubator-kie-kogito-runtimes/blob/main/jbpm/jbpm-tests/src/test/java/org/jbpm/bpmn2/IntermediateEventTest.java
   
   Closes https://github.com/apache/incubator-kie-issues/issues/1131.
   
   **Issue 1:** 
   
   `testEventBasedSplit3`
   
   Error: java.lang.NullPointerException: Cannot invoke 
"org.drools.core.common.InternalAgenda.isRuleActiveInRuleFlowGroup(String, 
String, String)" because the return value of 
"org.drools.core.common.InternalKnowledgeRuntime.getAgenda()" is null
   at 
org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit3(IntermediateEventTest.java:479)
   
   org.opentest4j.AssertionFailedError: 
   expected: 1
    but was: 5
    
   In the current implementation which is version 7, we use:
   
   `kruntime.getKieSession().insert(jack);`     
   
   But there appears to be an issue because the jack variable  doesn't exist in 
our data model. Could you please guide on how we should handle this.
   
   **Issue 2:**
   
   `testEventBasedSplit5`
   
    The receive task handler needs a kruntime object. Need guidance on how to 
create this handler in v9 as we don't have the kruntime object.
    
    ` ReceiveTaskHandler receiveTaskHandler = new ReceiveTaskHandler(null);
           ProcessTestHelper.registerHandler(app, "Receive Task", 
receiveTaskHandler);`
    
    
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to