April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Gabriele Cardosi edited comment on DROOLS-3674 at 4/9/19 11:50 AM: ------------------------------------------------------------------- [~danielezonca] [~zhutaojiajia] [~manstis] Hi, working on that. Just realized that it is basically impossible to map a click on that small icon, since actually it is a "canvas" and at most we can know (with given the x/y coords) the "cell" clicked. Beside that, we are back to the issue of having both click and double click mapped to the same element, that in turn means whenever a user double click (to edit) a cell with an error, the single click is also managed, and the error popover appear. [~manstis] WDYT ? was (Author: gabriolo): [~danielezonca] [~zhutaojiajia] [~manstis] Hi, working on that. Just realized that it is basically impossible to map a click on that small icon, since actually it is a "canvas" and at most we can know (with given the x/y coords) the "cell" clicked. Beside that, we are back top the issue of having both click and double click mapped to the same element, that in turns mean whenever a user double click (to edit) a cell with an error, the single click is also managed, and the error popover appear. [~manstis] WDYT ? > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-706) Update jenkins docker slave image

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-706?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-706. --------------------------------- Resolution: Done > Update jenkins docker slave image > --------------------------------- > > Key: SWSQE-706 > URL: https://issues.jboss.org/browse/SWSQE-706 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > We will need new requirements so it's necessary to update jenkins slave image -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3674: ------------------------------------------ [~danielezonca] [~zhutaojiajia] [~manstis] Hi, working on that. Just realized that it is basically impossible to map a click on that small icon, since actually it is a "canvas" and at most we can know (with given the x/y coords) the "cell" clicked. Beside that, we are back top the issue of having both click and double click mapped to the same element, that in turns mean whenever a user double click (to edit) a cell with an error, the single click is also managed, and the error popover appear. [~manstis] WDYT ? > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10996) [Postgres] Database queries result in NoClassDefFound for org/wildfly/transaction/client/ContextTransactionManager

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-10996?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFLY-10996. ------------------------------- > [Postgres] Database queries result in NoClassDefFound for org/wildfly/transaction/client/ContextTransactionManager > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-10996 > URL: https://issues.jboss.org/browse/WFLY-10996 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.1.Final, 14.0.0.Final > Environment: CentOS 7/Mac OS > WildFly 14.0.0 / WildFly 14.0.1 > Reporter: Rakesh Cherukuri > Assignee: Scott Marlow > Priority: Blocker > Fix For: 15.0.0.Final > > Attachments: error.log, jpa-war.tar.gz, pgsql.driver.tar.gz, standalone-full.diff > > > Basically WildFly is unable to either build the persistence context or it fails to query postgres db. > The changes are so minimal that it should basically work. > Attached: > # error.log - exception in the server log > # jpa-war.tar.gz - maven module that can be used to reproduce the issue > # pgsql.module.tar.gz - postgres driver module that can be unpacked under modules/system/layers/base/org/postgresql > # standalone-full.diff - diff that can be applied to standalone-full.xml to define required datasource > Note: > - Tested same steps with wildfly 13 and there its woking fine. > - Tested with latest postgres driver and issue exists with v14.0.0 (and v14.0.1). Postgres driver is thus ruled out. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11964) "cluster" attribute of /subsystem=ejb3/service=remote is no longer appropriately descriptive

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11964?page=com.atlassian.jira.plugin... ] Paul Ferraro moved JBEAP-13365 to WFLY-11964: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11964 (was: JBEAP-13365) Issue Type: Task (was: Bug) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering EJB (was: Clustering) (was: EJB) Target Release: (was: 7.backlog.GA) Affects Version/s: 16.0.0.Final (was: 7.1.0.CR2) > "cluster" attribute of /subsystem=ejb3/service=remote is no longer appropriately descriptive > -------------------------------------------------------------------------------------------- > > Key: WFLY-11964 > URL: https://issues.jboss.org/browse/WFLY-11964 > Project: WildFly > Issue Type: Task > Components: Clustering, EJB > Affects Versions: 16.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > The "cluster" attribute is a capability reference to a Registry/Group service and is no longer treated as an explicit "cluster name". The cluster name is, in fact, returned by Group.getName() of the associated Registry/Group. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-687) UI Automation - mTLS Icon on top-right page

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-687?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-687: -------------------------------------- PR https://github.com/Kiali-QE/kiali-qe-python/pull/158 > UI Automation - mTLS Icon on top-right page > ------------------------------------------- > > Key: SWSQE-687 > URL: https://issues.jboss.org/browse/SWSQE-687 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Verify mTLS enable, disable, partly enabled cases on top right side of Kiali page. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-687) UI Automation - mTLS Icon on top-right page

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-687?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-687. ---------------------------------- Resolution: Done > UI Automation - mTLS Icon on top-right page > ------------------------------------------- > > Key: SWSQE-687 > URL: https://issues.jboss.org/browse/SWSQE-687 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Verify mTLS enable, disable, partly enabled cases on top right side of Kiali page. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-691) UI Automation - mTLS on Overview page

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-691?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-691. ---------------------------------- Resolution: Done PR merged > UI Automation - mTLS on Overview page > ------------------------------------- > > Key: SWSQE-691 > URL: https://issues.jboss.org/browse/SWSQE-691 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-691) UI Automation - mTLS on Overview page

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-691?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-691: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/158 > UI Automation - mTLS on Overview page > ------------------------------------- > > Key: SWSQE-691 > URL: https://issues.jboss.org/browse/SWSQE-691 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11959) AbstractSimpleApplicationClientTestCase pollutes the build/target/ installation

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11959?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11959: ------------------------------------ Description: AbstractSimpleApplicationClientTestCase uses AppClientWrapper which ends up writing a log file in the WildFly installation in build/target. That's not ideal as that's not a test installation and its content shouldn't be polluted. It's not critical as by the time the testsuite has run the build module has already created a zip of its installation, and that zip is what would get deployed if a release was being done. was: AbstractSimpleApplicationClientTestCase uses AppClientWrapper which ends up writing a log file in the WildFly installation in build/target. That's not ideal as that's not a test installation and its content shouldn't be polluted. It's not critical as by the time the testsuite has run the build module has already created a zip of its installation, and that zip is what would get deployed if a release. > AbstractSimpleApplicationClientTestCase pollutes the build/target/ installation > ------------------------------------------------------------------------------- > > Key: WFLY-11959 > URL: https://issues.jboss.org/browse/WFLY-11959 > Project: WildFly > Issue Type: Bug > Components: Application Client, Test Suite > Reporter: Brian Stansberry > Priority: Minor > > AbstractSimpleApplicationClientTestCase uses AppClientWrapper which ends up writing a log file in the WildFly installation in build/target. That's not ideal as that's not a test installation and its content shouldn't be polluted. > It's not critical as by the time the testsuite has run the build module has already created a zip of its installation, and that zip is what would get deployed if a release was being done. -- 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