April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-694) Kiali - Check/Modify existing test cases for test types(Functional/Non-Functional

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-694?page=com.atlassian.jira.plugin.... ] Sunil Kondkar resolved SWSQE-694. --------------------------------- Resolution: Done Done > Kiali - Check/Modify existing test cases for test types(Functional/Non-Functional > --------------------------------------------------------------------------------- > > Key: SWSQE-694 > URL: https://issues.jboss.org/browse/SWSQE-694 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > In Kiali, there is only one test case which is non-functional test type. > This task is to check existing test cases if any which can be modified for differenr test types -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-694) Kiali - Check/Modify existing test cases for test types(Functional/Non-Functional

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-694?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-694: ------------------------------------- Done for existing test cases. Modified test cases for non-functional->Security, non-functional->Installability, non-functional->Usability. > Kiali - Check/Modify existing test cases for test types(Functional/Non-Functional > --------------------------------------------------------------------------------- > > Key: SWSQE-694 > URL: https://issues.jboss.org/browse/SWSQE-694 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > In Kiali, there is only one test case which is non-functional test type. > This task is to check existing test cases if any which can be modified for differenr test types -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3871) [DMN Designer] Add support for read-only boxed expressions

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3871: -------------------------------------- Summary: [DMN Designer] Add support for read-only boxed expressions Key: DROOLS-3871 URL: https://issues.jboss.org/browse/DROOLS-3871 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Michael Anstis Assignee: Michael Anstis Imported models are read-only. Therefore we need support for read-only Boxed Expressions. Mouse and keyboard interactions need covering. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-666) Test case coverage for Jaeger

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-666?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-666. ----------------------------------- Resolution: Done > Test case coverage for Jaeger > ----------------------------- > > Key: SWSQE-666 > URL: https://issues.jboss.org/browse/SWSQE-666 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > > Need to focus on different type of testing as well other than functional. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-666) Test case coverage for Jaeger

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-666?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy commented on SWSQE-666: --------------------------------------- Updated test type and sub type > Test case coverage for Jaeger > ----------------------------- > > Key: SWSQE-666 > URL: https://issues.jboss.org/browse/SWSQE-666 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Jeeva Kandasamy > Priority: Major > Labels: pqi > > Need to focus on different type of testing as well other than functional. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1918) Guided rule editor: "from accumulate" should support multiple pattern definitions

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1918?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1918. ------------------------------- Resolution: Rejected Closing as workaround was described and the component is not actively developed anymore. > Guided rule editor: "from accumulate" should support multiple pattern definitions > --------------------------------------------------------------------------------- > > Key: DROOLS-1918 > URL: https://issues.jboss.org/browse/DROOLS-1918 > Project: Drools > Issue Type: Feature Request > Components: Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > This was reported:- > On 27/07/12 03:34, Udaypal Aarkoti wrote: > > Michael, > > > > I was talking to Edson about what's the best way to build a PoC for a customer that I am working with and Edson gave a few suggestions. Those more mostly using DRL but I wanted to convert them into a Rule Template that customer can simply use to fill in values but looks like I hit a limitation here and wanted to check if there any way around it. > > > > Here is the psuedo code and the rule I am trying to implement > > > > Class Partner {} > > Class Representation{ Partner partner } > > Class Training {Representative rep} > > > > The main problem I am facing is that I cannot seem to have a compound condition using "from accumulate" as show below in guided editor. I am able to use either a "Representative" Object or "Training" object as a condition but NOT both using the guided editor. > > > > Is that true? Is there a way around it? I don't want to use DSL because there are some key bindings that needs to be passed to the condition (i.e user will enter value in the template that need to be passed down to the DSL, which I believe is not currently supported). > > > > > > rule "Accumulate partner Trainings for RPPOS100" > > > > when > > $p : Partner() > > $count : Number() from accumulate( $r : Representative( partner == $p ) and Training( representative == $r, name == "RPPOS100" ), count( 1 ) ) > > then > > System.out.println("Testing : " + $count); > > end -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2065) XLS Decision table: Add support for a boolean column indicating that the row (rule) should be negated

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2065?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2065. ------------------------------- Resolution: Rejected Closing a the component is not actively developed anymore and the issue is not reproted by the customer. > XLS Decision table: Add support for a boolean column indicating that the row (rule) should be negated > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-2065 > URL: https://issues.jboss.org/browse/DROOLS-2065 > Project: Drools > Issue Type: Feature Request > Components: XLS Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > Add a boolean column to the XLS decision table parser to allow rules to be negated:- > When "turned on" for a rule:- > when > not ( > pattern1.. > pattern2.. > ) > then > ... > end > When "turned off" for a rule:- > when > pattern1.. > pattern2.. > then > ... > end -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3470) [GDT] Limited Entry Table, checkboxes are not rendered when enter is pressed

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3470?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-3470. ------------------------------- Resolution: Rejected Closing as it is minor issue not reported by customer and the component is not actively developed anymore. The reproducer test updated by [PR|https://github.com/jboss-integration/bxms-qe-tests/pull/2426/files] > [GDT] Limited Entry Table, checkboxes are not rendered when enter is pressed > ---------------------------------------------------------------------------- > > Key: DROOLS-3470 > URL: https://issues.jboss.org/browse/DROOLS-3470 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools, regression > Attachments: Screenshot from 2019-01-04 08-55-58.png, Screenshot from 2019-01-04 08-56-05.png > > > Two attachments show the problem. One picture shows all checkboxes of limited entry decision table are shown correctly. The second picture shows checkboxes are not visible when description is in edit mode. See steps to reproduce. > This issue occurs just for limited entry decision table. Extended entry decision table works fine. Next this problem occurs just if the description column edit mode is started by pressing enter. Double click by mouse doesn't cause this issue. > h2. Acceptance criteria > There exists [selenium test|https://github.com/jboss-integration/bxms-qe-tests/blob/master/test-...] for limited entry tables, however due to this DROOLS-3470 issue it has to be ignored, see [PR|https://github.com/jboss-integration/bxms-qe-tests/pull/2150]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11966) Capability requirements declared twice in JCA root resource definition

by Yeray Borges (Jira)

Yeray Borges created WFLY-11966: ----------------------------------- Summary: Capability requirements declared twice in JCA root resource definition Key: WFLY-11966 URL: https://issues.jboss.org/browse/WFLY-11966 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 17.0.0.Beta1 Reporter: Yeray Borges Assignee: Yeray Borges This is a consequence of a bug introduced in WFLY-11747 JCA root definition is using the setCapabilities method twice: {code:java} private JcaSubsystemRootDefinition(final boolean registerRuntimeOnly) { super(new Parameters(PATH_SUBSYSTEM, JcaExtension.getResourceDescriptionResolver()) .setAddHandler(JcaSubsystemAdd.INSTANCE) .setRemoveHandler(JcaSubSystemRemove.INSTANCE) .setCapabilities(JCA_NAMING_CAPABILITY) .setCapabilities(TRANSACTION_INTEGRATION_CAPABILITY) ); this.registerRuntimeOnly = registerRuntimeOnly; } {code} That means JCA_NAMING_CAPABILITY is being overwritten by TRANSACTION_INTEGRATION_CAPABILITY , so this requirement is lost. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10607) Fix intermittent failures in *EJBForwardingTestCase

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10607?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10607: ---------------------------------- Summary: Fix intermittent failures in *EJBForwardingTestCase (was: Fix intermittent failures in *EJBForwardingTestCases) > Fix intermittent failures in *EJBForwardingTestCase > --------------------------------------------------- > > Key: WFLY-10607 > URL: https://issues.jboss.org/browse/WFLY-10607 > Project: WildFly > Issue Type: Bug > Components: EJB, Test Suite > Affects Versions: 16.0.0.Final > Reporter: Petr Kremensky > Assignee: Richard Achmatowicz > Priority: Major > > The tests were ignored by https://github.com/wildfly/wildfly/pull/10563 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019