July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4236) Testing of the HACEP

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4236?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4236: --------------------------------------- Sprint: 2019 Week 26-28 (was: 2019 Week 29-31) > Testing of the HACEP > --------------------- > > Key: DROOLS-4236 > URL: https://issues.jboss.org/browse/DROOLS-4236 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4275) Drools-wb webapp does not start

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4275: ---------------------------------------- Summary: Drools-wb webapp does not start Key: DROOLS-4275 URL: https://issues.jboss.org/browse/DROOLS-4275 Project: Drools Issue Type: Bug Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Drools-wb webapp jboss does not start due to ambiguous dependencies at WELD -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4161: --------------------------------------- [~kkufova] It might be not that simple because we discussed about create a template tight to a decision service (= keep as EXPECT only decision in the decision service and as GIVEN all and only the needed inputs) so if we change the name of the decision service to invoke I expect the template to be updated (or at least it should be nice to have) And what about revert to the full model testing? Should we support this too? Btw we can just change the name in the panel as first step of course > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-805) Add Kiali Operator Cleaning on Downstream

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-805?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-805: ------------------------------------------ Description: Since Kiali Operator was incorporated, it needs to have a clean to properly clean it. > Add Kiali Operator Cleaning on Downstream > ----------------------------------------- > > Key: SWSQE-805 > URL: https://issues.jboss.org/browse/SWSQE-805 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > Since Kiali Operator was incorporated, it needs to have a clean to properly clean it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-805) Add Kiali Operator Cleaning on Downstream

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-805: --------------------------------------------- Summary: Add Kiali Operator Cleaning on Downstream Key: SWSQE-805 URL: https://issues.jboss.org/browse/SWSQE-805 Project: Kiali QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-805) Add Kiali Operator Cleaning on Downstream

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-805?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-805: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo > Add Kiali Operator Cleaning on Downstream > ----------------------------------------- > > Key: SWSQE-805 > URL: https://issues.jboss.org/browse/SWSQE-805 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4555) Randomly fail an add operation on subsystem remoting

by Vratislav Marek (Jira)

Vratislav Marek created WFCORE-4555: --------------------------------------- Summary: Randomly fail an add operation on subsystem remoting Key: WFCORE-4555 URL: https://issues.jboss.org/browse/WFCORE-4555 Project: WildFly Core Issue Type: Bug Components: Remoting Environment: * Any java * RHEL6 & RHEL7 Reporter: Vratislav Marek Assignee: Flavia Rainone Operation add on subsystem remoting randomly fail with the message:: {code} { "outcome" => "failed", "failure-description" => "WFLYCTL0441: Operation has resulted in failed or missing services WFLYCTL0448: 1 additional services are down due to their dependencies being missing or failed", "rolled-back" => true } {code} Used operation: {code} { "operation" => "add", "address" => [("subsystem" => "remoting")], "worker" => "default-remoting", "send-buffer-size" => 1, "receive-buffer-size" => 1, "buffer-region-size" => 1, "transmit-window-size" => 1, "receive-window-size" => 1, "max-outbound-channels" => 1, "max-inbound-channels" => 1, "authorize-id" => "abc", "auth-realm" => "abc", "authentication-retries" => 1, "max-outbound-messages" => 1, "max-inbound-messages" => 1, "heartbeat-interval" => 1, "max-inbound-message-size" => 1L, "max-outbound-message-size" => 1L, "server-name" => "abc", "sasl-protocol" => "abc", "worker-read-threads" => undefined, "worker-task-core-threads" => undefined, "worker-task-keepalive" => undefined, "worker-task-limit" => undefined, "worker-task-max-threads" => undefined, "worker-write-threads" => undefined } {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-4161: -------------------------------------- [~danielezonca], I think this can be a part of the *Settings* panel. Now, you can set the DMN model there. It should be very easy to add a new *Decision Service* option. > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12244) MaximumTimeoutTestCase fails a lot

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/WFLY-12244?page=com.atlassian.jira.plugin... ] Thomas Jenkinson reassigned WFLY-12244: --------------------------------------- Assignee: Ondrej Chaloupka (was: Michael Musgrove) > MaximumTimeoutTestCase fails a lot > ---------------------------------- > > Key: WFLY-12244 > URL: https://issues.jboss.org/browse/WFLY-12244 > Project: WildFly > Issue Type: Bug > Components: Test Suite, Transactions > Reporter: Kabir Khan > Assignee: Ondrej Chaloupka > Priority: Critical > > This is failing a lot on CI for loads of pull requests: https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... > It also happens on master JDK 11 https://ci.wildfly.org/viewLog.html?buildId=156368&buildTypeId=WF_MasterW... > CC [~tomjenkinson] [~ochaloup] [~zhfeng] -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4162) Scenario Test: UX for background data

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4162?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4162: --------------------------------------- [~zhutaojiajia] Sorry but I don't think you are covering the requirement entirely. - How is the user supposed to specify multiple instances? - How specify the mapping? Let me recap the steps: - user creates a new test scenario - user wants to specify some data to be used in every scenario - user needs to defined the mapping for each object - user can specify multiple instances for each object Here is an example: User wants to create multiple scenarios and each of them begin with the same set of data i.e. 4 available people. In the current implementation he needs to create 4 instances (one for each person) and specify the same values for each row but he would like to do it only once. Background concept should allow him to do this mapping and define the data only once and this will be applied to each scenario as additional GIVEN data. > Scenario Test: UX for background data > ------------------------------------- > > Key: DROOLS-4162 > URL: https://issues.jboss.org/browse/DROOLS-4162 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: design1.png, design2.png, design3.png > > > As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. > Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2019