[JBoss JIRA] (WFLY-10127) DatasourceMaxPoolAttributeTestCase and DatasourceMinPoolAttributeTestCase fails with security manager
by Martin Stefanko (JIRA)
[ https://issues.jboss.org/browse/WFLY-10127?page=com.atlassian.jira.plugin... ]
Martin Stefanko reassigned WFLY-10127:
--------------------------------------
Assignee: Martin Stefanko
> DatasourceMaxPoolAttributeTestCase and DatasourceMinPoolAttributeTestCase fails with security manager
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-10127
> URL: https://issues.jboss.org/browse/WFLY-10127
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Ondrej Lukas
> Assignee: Martin Stefanko
>
> {{DatasourceMaxPoolAttributeTestCase}} and {{DatasourceMinPoolAttributeTestCase}} fails with security manager because of missing permission {{"java.lang.RuntimePermission" "accessDeclaredMembers"}}:
> {code}
> java.lang.AssertionError: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "accessDeclaredMembers")" in code source "(vfs:/content/deployment.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.deployment.jar" from Service Module Loader")
> at org.junit.Assert.fail(Assert.java:88)
> at org.jboss.as.test.integration.jca.JcaTestsUtil.extractWrapperDatasource(JcaTestsUtil.java:179)
> at org.jboss.as.test.integration.jca.poolattributes.DatasourceMaxPoolAttributeTestCase.testModifyMinPoolAttribute(DatasourceMaxPoolAttributeTestCase.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
> at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:372)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:246)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:260)
> at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:324)
> at org.jboss.arquillian.container.test.impl.execution.BeforeLifecycleEventExecuter.on(BeforeLifecycleEventExecuter.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
> at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:317)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:200)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
> at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724)
> at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168)
> at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10173?page=com.atlassian.jira.plugin... ]
Jan Kalina updated WFLY-10173:
------------------------------
Description:
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}
was:
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)
{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}
> EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
> -------------------------------------------------------------
>
> Key: WFLY-10173
> URL: https://issues.jboss.org/browse/WFLY-10173
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Jan Kalina
>
> 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.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (/)
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected (/)
# Rebuild connections, change should appear in navigator (/)
## connections have no impact on structure in navigator
# Check multiple connections, input node connected to multiple decisions ... (/)
## connections have no impact on structure in navigator
# Long node names (/) perfect
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
## DROOLS-2435
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (/)
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected (/)
# Rebuild connections, change should appear in navigator (?)
## not checked, because not able to connect DRG nodes
# Check multiple connections, input node connected to multiple decisions ... (?)
## not checked, because not able to connect DRG nodes
# Long node names (/) perfect
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
## DROOLS-2435
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons (/)
> ## expression types distinguished
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
> # check situation when multiple nodes has the same name, empty name (/)
> ## same names no problem, empty name replace with node type, nice
> # Check case when DRG contains a lot of nodes , if possible to view all of them (/)
> ## scrollbar appears, and disappear according to count of nodes, nice
> # Check case when some decision has a lot of inputs - all of them visible (/)
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - does not prevent from merge
> # Check if navigator dock can be resized (/)
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name (/)
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node (/)
> ## opened DRG, clicked DRD (x)
> ### DROOLS-2432 does not prevent from merge
> ## opened DRD, clicked other DRD (/)
> ## opened DRD, clicked DRG node (/)
> # Check behavior if user tries to select multiple entries in navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to invoke context menu from navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to drag some elements in navigator (/)
> ## not implemented, but fine, no exception
> h3. Sorting
> # nodes sorted asc, changes in node names reflected in order (/)
> # rename some DRG nodes, check navigator keeps selected sorting (/)
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo (x)
> ## DROOLS-2433
> # rename some DRG nodes, undo redo, check changes reflected in navigator (/)
> # delete DRG node, undo redo, check changes reflected in navigator (/)
> # clear DRD node, undo redo, check changes reflected in navigator (x)
> ## DROOLS-2434
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator (/)
> # clear DRD node, check changes reflected in navigator (x)
> ## DROOLS-2434
> # Drag DRG elements, no effect to expected (/)
> # Rebuild connections, change should appear in navigator (/)
> ## connections have no impact on structure in navigator
> # Check multiple connections, input node connected to multiple decisions ... (/)
> ## connections have no impact on structure in navigator
> # Long node names (/) perfect
> # Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
> ## DROOLS-2435
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (/)
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected (/)
# Rebuild connections, change should appear in navigator (?)
## not checked, because not able to connect DRG nodes
# Check multiple connections, input node connected to multiple decisions ... (?)
## not checked, because not able to connect DRG nodes
# Long node names (/) perfect
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
## DROOLS-2435
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (?)
## not checked, because not able to connect DRG nodes
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected (/)
# Rebuild connections, change should appear in navigator (?)
## not checked, because not able to connect DRG nodes
# Check multiple connections, input node connected to multiple decisions ... (?)
## not checked, because not able to connect DRG nodes
# Long node names (/) perfect
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
## DROOLS-2435
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons (/)
> ## expression types distinguished
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
> # check situation when multiple nodes has the same name, empty name (/)
> ## same names no problem, empty name replace with node type, nice
> # Check case when DRG contains a lot of nodes , if possible to view all of them (/)
> ## scrollbar appears, and disappear according to count of nodes, nice
> # Check case when some decision has a lot of inputs - all of them visible (/)
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - does not prevent from merge
> # Check if navigator dock can be resized (/)
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name (/)
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node (/)
> ## opened DRG, clicked DRD (x)
> ### DROOLS-2432 does not prevent from merge
> ## opened DRD, clicked other DRD (/)
> ## opened DRD, clicked DRG node (/)
> # Check behavior if user tries to select multiple entries in navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to invoke context menu from navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to drag some elements in navigator (/)
> ## not implemented, but fine, no exception
> h3. Sorting
> # nodes sorted asc, changes in node names reflected in order (/)
> # rename some DRG nodes, check navigator keeps selected sorting (/)
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo (x)
> ## DROOLS-2433
> # rename some DRG nodes, undo redo, check changes reflected in navigator (/)
> # delete DRG node, undo redo, check changes reflected in navigator (/)
> # clear DRD node, undo redo, check changes reflected in navigator (x)
> ## DROOLS-2434
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator (/)
> # clear DRD node, check changes reflected in navigator (x)
> ## DROOLS-2434
> # Drag DRG elements, no effect to expected (/)
> # Rebuild connections, change should appear in navigator (?)
> ## not checked, because not able to connect DRG nodes
> # Check multiple connections, input node connected to multiple decisions ... (?)
> ## not checked, because not able to connect DRG nodes
> # Long node names (/) perfect
> # Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
> ## DROOLS-2435
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10173?page=com.atlassian.jira.plugin... ]
Jan Kalina updated WFLY-10173:
------------------------------
Description:
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)
{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}
was:
Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0.
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)
{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}
> EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
> -------------------------------------------------------------
>
> Key: WFLY-10173
> URL: https://issues.jboss.org/browse/WFLY-10173
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Jan Kalina
>
> 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)
> {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.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
by Jan Kalina (JIRA)
Jan Kalina created WFLY-10173:
---------------------------------
Summary: EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
Key: WFLY-10173
URL: https://issues.jboss.org/browse/WFLY-10173
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 12.0.0.Final
Reporter: Jan Kalina
Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0.
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)
{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.5.0#75005)
8 years, 3 months