March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-536) [RS] Prototype Automation Test Runs Into Polarion

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-536?page=com.atlassian.jira.plugin.... ] Prachi Yadav commented on SWSQE-536: ------------------------------------ ----- Original Message ----- From: "Prachi Yadav" <pyadav(a)redhat.com> To: "Greg Allen" <gallen(a)redhat.com>, "Brian Murray" <bmurray(a)redhat.com> Cc: "Michael Foley" <mfoley(a)redhat.com>, "Matthew Mahoney" <mmahoney(a)redhat.com> Sent: Tuesday, March 12, 2019 7:45:01 PM Subject: Re: Regarding importing Automation test results into Polarion Hello, We need both import test cases as well as test case results. Regards, Prachi ----- Original Message ----- From: "Greg Allen" <gallen(a)redhat.com> To: "Brian Murray" <bmurray(a)redhat.com> Cc: "Prachi Yadav" <pyadav(a)redhat.com>, "Michael Foley" <mfoley(a)redhat.com> Sent: Tuesday, March 12, 2019 6:32:41 PM Subject: Re: Regarding importing Automation test results into Polarion Prachi, Here are both Brian and my responses. Did you not get them? -- GReg On 02/26/2019 09:19 AM, Brian Murray wrote: > Hi Prachi, > > I would be glad to help. It is not clear from your email whether you > are trying to import test cases or test case results. Please > clarify. Also, here are links to relevant documents on using the > Importers: > > https://mojo.redhat.com/docs/DOC-1075945 > https://mojo.redhat.com/docs/DOC-1073077 > > > On Tue, Feb 26, 2019 at 8:40 AM Greg Allen <gallen(a)redhat.com > <mailto:gallen@redhat.com>> wrote: > > Hi Prachi, > > I think what you are trying to do can be done. > > However, Brian Murray is a better person to answer your > questions. And > I suspect he'll need some more information from you so he can help. > I've included him on this email. > > -- Greg > [RS] Prototype Automation Test Runs Into Polarion > ------------------------------------------------- > > Key: SWSQE-536 > URL: https://issues.jboss.org/browse/SWSQE-536 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Prachi Yadav > Priority: Major > > What is the mechanism to import automation runs into Polarion. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ] Klara Kufova reassigned DROOLS-3420: ------------------------------------ Assignee: Daniele Zonca (was: Gabriele Cardosi) > Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget > ------------------------------------------------------------------- > > Key: DROOLS-3420 > URL: https://issues.jboss.org/browse/DROOLS-3420 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Daniele Zonca > Priority: Minor > > SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget". > Later, ask [~Rikkola] to move it on upper framework. > *ADDITIONAL IMPROVEMENTS:* > # -When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. > # Change *Choose DMN asset* to *Choose a DMN asset*. > # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down). > # -The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. > # -The field *Choose DMN asset* should be marked with *{color:red}*{color}* (required field).- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3420: --------------------------------- Sprint: 2019 Week 11-13 > Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget > ------------------------------------------------------------------- > > Key: DROOLS-3420 > URL: https://issues.jboss.org/browse/DROOLS-3420 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Minor > > SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget". > Later, ask [~Rikkola] to move it on upper framework. > *ADDITIONAL IMPROVEMENTS:* > # -When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. > # Change *Choose DMN asset* to *Choose a DMN asset*. > # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down). > # -The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. > # -The field *Choose DMN asset* should be marked with *{color:red}*{color}* (required field).- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3675) Create HTML/CSS for global setting dock + Test Scenario creation popup

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3675?page=com.atlassian.jira.plugi... ] Klara Kufova resolved DROOLS-3675. ---------------------------------- Resolution: Done > Create HTML/CSS for global setting dock + Test Scenario creation popup > ---------------------------------------------------------------------- > > Key: DROOLS-3675 > URL: https://issues.jboss.org/browse/DROOLS-3675 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Sarah Rambacher > Priority: Major > Labels: ScenarioSimulation > > Please refer to for the mockup > https://issues.jboss.org/browse/DROOLS-3492 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3387) Update interaction behavior to align with DMN/Stunner.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3387?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3387: ------------------------------------- [~danielezonca][~zhutaojiajia] For future consideration, I believe that [~tirelli] is interested in Scenario using pop-overs for reporting, similar to what we're working on for DMN: https://issues.jboss.org/browse/DROOLS-3731. > Update interaction behavior to align with DMN/Stunner. > ------------------------------------------------------- > > Key: DROOLS-3387 > URL: https://issues.jboss.org/browse/DROOLS-3387 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Daniele Zonca > Priority: Major > Labels: UX, UXTeam > > Align grid interactions to be consistent with DMN updates: > - Single-click to select a cell > - double-click to edit a cell inline. > - single click to launch a pop-over menu. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3438) Cancel Scenario Simulation edit mode

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3438?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3438: --------------------------------- Sprint: 2019 Week 05-07, 2019 Week 08-10 (was: 2019 Week 05-07, 2019 Week 08-10, 2019 Week 11-13) > Cancel Scenario Simulation edit mode > ------------------------------------ > > Key: DROOLS-3438 > URL: https://issues.jboss.org/browse/DROOLS-3438 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > User is able to edit grid cell by pressing an enter. Currently the edit mode is cancelled by *Shift + Tab* combination. We have to change this to: > - *Tab* for cancel edit mode and *store* the value > - *Esc* for cancel edit mode and *discard* the value > This defect is caused by keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11825) CXF-7984 - UsernameTokenInterceptor doesn't respect contextual property "allowNamespaceQualifiedPasswordTypes"

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-11825?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-11825: --------------------------------- Git Pull Request: https://github.com/apache/cxf/commit/c75bc5d388ef748854a6bdcca594711dafd0..., https://github.com/apache/cxf/commit/34da361394b5ec63d1c63246b2a735a7148d... (was: https://github.com/apache/cxf/commit/c75bc5d388ef748854a6bdcca594711dafd0...) > CXF-7984 - UsernameTokenInterceptor doesn't respect contextual property "allowNamespaceQualifiedPasswordTypes" > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11825 > URL: https://issues.jboss.org/browse/WFLY-11825 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 16.0.0.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > allowNamespaceQualifiedPasswordTypes is not read from contextual properties before create wss4j UsernameToken. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4368) Remove the org.apache.commons:commons-lang3 exclusion from elytron-tool

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFCORE-4368?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-4368: ------------------------------- Component/s: Security > Remove the org.apache.commons:commons-lang3 exclusion from elytron-tool > ----------------------------------------------------------------------- > > Key: WFCORE-4368 > URL: https://issues.jboss.org/browse/WFCORE-4368 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Kabir Khan > Priority: Major > > See https://issues.jboss.org/browse/WFCORE-4366 for details of why it is needed. Since the Elytron tool shades all its dependencies, can they have a scope which does not get exported again? Perhaps provided, although I don't know if those work with the shade plugin. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11839) Missing transformer for default protocol version change of remote-cache-container

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11839: ----------------------------------- Summary: Missing transformer for default protocol version change of remote-cache-container Key: WFLY-11839 URL: https://issues.jboss.org/browse/WFLY-11839 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 16.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-635) Kiali installation failed on OCP4 - But job is success

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-635?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-635. ---------------------------------- Assignee: Hayk Hovsepyan Resolution: Done New job created: https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/Productized-Kia... > Kiali installation failed on OCP4 - But job is success > ------------------------------------------------------ > > Key: SWSQE-635 > URL: https://issues.jboss.org/browse/SWSQE-635 > Project: Kiali QE > Issue Type: Bug > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/Kiali-on-Opensh... > Using Docker tag v0.15.0 from Docker Repo docker.io/kiali/kiali > Error from server (NotFound): routes.route.openshift.io "istio-ingressgateway" not found > Kiali Core Prepared > Deploy Kiali on Openshift > Fri Mar 8 10:11:08 UTC 2019 > Kiali Deployed > Regular expression run condition: Expression=[true], Label=[true] > Run condition [Regular expression match] enabling perform for step [Trigger/call builds on other projects] > Waiting for the completion of Kiali-Istio-Checker > Kiali-Istio-Checker #5182 completed. Result was SUCCESS > Build step 'Conditional step (single)' changed build result to SUCCESS > Regular expression run condition: Expression=[true], Label=[true] > Run condition [Regular expression match] enabling perform for step [Builder to mark whether executed] > Finished: SUCCESS -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019