[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] Wrong test result status if rules have not been fired
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Steps to Reproduce:
# Import [^MySpace_List.zip] project
# Open Test scenario "ErrorMessageTest" and run it
Expect : !Screenshot from 2020-04-21 17-28-31.png|thumbnail!
1. Test Run status is FAIL
Actual: 0% coverage test is passing
was:
# Import [^MySpace_List.zip] project
# Open Test scenario "ErrorMessageTest" and run it
Expect : Coverage report got 100% rules covered (rules have been fired)
If rules are not fired then the test should fail
Actual: 0% coverage test is passing
> [Test Scenario Editor] Wrong test result status if rules have not been fired
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, Screenshot from 2020-04-21 17-28-31.png, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] Wrong test result status if rules have not been fired
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Attachment: Screenshot from 2020-04-21 17-28-31.png
> [Test Scenario Editor] Wrong test result status if rules have not been fired
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, Screenshot from 2020-04-21 17-28-31.png, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] Wrong test result status if rules have not been fired
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak edited comment on DROOLS-5263 at 4/22/20 2:46 AM:
---------------------------------------------------------------
So after short discussion with [~yamer]
The expect test run state should be "FAILED"
And the cell should be marked red with the error popup :"There is no instance that satisfied the condition"
!Screenshot from 2020-04-21 17-28-31.png|thumbnail!
was (Author: adupliak):
So after short discussion with [~yamer]
The expect test run state should be "FAILED"
And the cell should be marked red with the error popup :"There is no instance that satisfied the condition"
!screenshot-4.png|thumbnail!
> [Test Scenario Editor] Wrong test result status if rules have not been fired
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, Screenshot from 2020-04-21 17-28-31.png, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] Wrong test result status if rules have not been fired
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak commented on DROOLS-5263:
--------------------------------------
So after short discussion with [~yamer]
The expect test run state should be "FAILED"
And the cell should be marked red with the error popup :"There is no instance that satisfied the condition"
!screenshot-4.png|thumbnail!
> [Test Scenario Editor] Wrong test result status if rules have not been fired
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] Wrong test result status if rules have not been fired
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Attachment: screenshot-4.png
> [Test Scenario Editor] Wrong test result status if rules have not been fired
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5263) [Test Scenario Editor] Wrong test result status if rules have not been fired
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5263?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5263:
---------------------------------
Attachment: (was: screenshot-4.png)
> [Test Scenario Editor] Wrong test result status if rules have not been fired
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5263
> URL: https://issues.redhat.com/browse/DROOLS-5263
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Legacy works with Lists.docx, MySpace_List.zip, PAM Issue with New Test Scenarios and lists.docx, medPartBDate-NotOnRequest-MarketingNo.rdrl, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Defect: If user create a list - typed fact and puts it to the Test Scenario, and use it in guided rule see [^PAM Issue with New Test Scenarios and lists.docx]
> Then test passes but rules are not getting fired.
> This feature implemented other way in legacy test scenario see the example: [^Legacy works with Lists.docx]
> Root case :
> We removed initialization of the list by default .
> Previously when you have been adding a fact to legacy test scenario - it was automatically initializing so in the end you got in GIVEN list with one empty element
> Now If you add a list fact you are free to left it empty or initialize it with at least one element.
> Workaround: put in GIVEN section for the list at least one empty element
> Customer case details:
> https://gss.my.salesforce.com/5002K00000mr7eFQAQ#comment_a0a2K00000UQOQ2QAP
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFCORE-4901) TCCL not set to application classloader when MBean Notification is invoked
by Moulali Shikalwadi (Jira)
[ https://issues.redhat.com/browse/WFCORE-4901?page=com.atlassian.jira.plug... ]
Moulali Shikalwadi updated WFCORE-4901:
---------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4175 (was: https://github.com/wildfly/wildfly-core/pull/4126)
> TCCL not set to application classloader when MBean Notification is invoked
> --------------------------------------------------------------------------
>
> Key: WFCORE-4901
> URL: https://issues.redhat.com/browse/WFCORE-4901
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Moulali Shikalwadi
> Assignee: Moulali Shikalwadi
> Priority: Major
>
> TCCL not set to application classloader when MBean Notification is invoked
> If an application registers an MBean notification and it receives a notification, the Thread Context ClassLoader is not set to the application, this causes ClassNotFound exceptions on classes that are in the application's classpath.
> javax.naming.NamingException: WFLYNAM0027: Failed instantiate InitialContextFactory org.wildfly.naming.client.WildFlyInitialContextFactory from classloader ModuleClassLoader for Module "org.jboss.as.server" version 6.0.21.Final-redhat-00001 from local module loader @dfd3711 (finder: local module finder @42d3bd8b (roots: /tmp/jboss-eap-7.2/modules,/tmp/jboss-eap-7.2/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: org.wildfly.naming.client.WildFlyInitialContextFactory from [Module "org.jboss.as.server" version 6.0.21.Final-redhat-00001 from local module loader @dfd3711 (finder: local module finder @42d3bd8b (roots: /tmp/jboss-eap-7.2/modules,/tmp/jboss-eap-7.2/modules/system/layers/base))]]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:120)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:101)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:91)
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
> at javax.naming.InitialContext.init(InitialContext.java:244)
> at javax.naming.InitialContext.<init>(InitialContext.java:216)
> at test.Client.getInitialContext(Client.java:66)
> at test.Client.invoke(Client.java:44)
> at test.Client.handleNotification(Client.java:117)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1754)
> at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:275)
> at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:352)
> at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:337)
> at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:248)
> at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:209)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin$ResourceRegistrationNotificationHandler.handleNotification(ModelControllerMBeanServerPlugin.java:431)
> at org.jboss.as.controller.notification.NotificationSupports.fireNotifications(NotificationSupports.java:126)
> at org.jboss.as.controller.notification.NotificationSupports.access$000(NotificationSupports.java:47)
> at org.jboss.as.controller.notification.NotificationSupports$NonBlockingNotificationSupport$1.run(NotificationSupports.java:105)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.ClassNotFoundException: org.wildfly.naming.client.WildFlyInitialContextFactory from [Module "org.jboss.as.server" version 6.0.21.Final-redhat-00001 from local module loader @dfd3711 (finder: local module finder @42d3bd8b (roots: /tmp/jboss-eap-7.2/modules,/tmp/jboss-eap-7.2/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:115)
> ... 27 more
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ]
Lukas Vydra reassigned WFLY-10173:
----------------------------------
Assignee: Lukas Vydra
> EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
> -------------------------------------------------------------
>
> Key: WFLY-10173
> URL: https://issues.redhat.com/browse/WFLY-10173
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Jan Kalina
> Assignee: Lukas Vydra
> Priority: Major
>
> Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message).
> For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases.
> I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test)
> {code}
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase
> [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179)
> at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379)
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months