February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1076) Automate Codes: https://github.com/kiali/kiali/pull/2275/

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1076?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1076. ----------------------------------- Resolution: Done > Automate Codes: https://github.com/kiali/kiali/pull/2275/ > --------------------------------------------------------- > > Key: SWSQE-1076 > URL: https://issues.redhat.com/browse/SWSQE-1076 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Also automate: > "No matching workload found for authorization policy selector in this namespace" > "This subset is already referenced in another route destination" > "Destination field is mandatory" > "Unable to verify the validity, cross-namespace validation is not supported for this field" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1070) Automate AuthPolicy https://github.com/kiali/kiali/pull/2261

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1070?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1070. ----------------------------------- Resolution: Done > Automate AuthPolicy https://github.com/kiali/kiali/pull/2261 > ------------------------------------------------------------ > > Key: SWSQE-1070 > URL: https://issues.redhat.com/browse/SWSQE-1070 > 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.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1074) Automate API Doc https://github.com/kiali/kiali-ui/pull/1667

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1074?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1074. ----------------------------------- Resolution: Done > Automate API Doc https://github.com/kiali/kiali-ui/pull/1667 > ------------------------------------------------------------ > > Key: SWSQE-1074 > URL: https://issues.redhat.com/browse/SWSQE-1074 > 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.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4868) HA-CEP test with Executable Model

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4868?page=com.atlassian.jira.plug... ] Massimiliano Dessi resolved DROOLS-4868. ---------------------------------------- Resolution: Done > HA-CEP test with Executable Model > --------------------------------- > > Key: DROOLS-4868 > URL: https://issues.redhat.com/browse/DROOLS-4868 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Massimiliano Dessi > Priority: Major > > org.kie.hacep.PodAsLeaderSnapshotTest.processMessagesAsLeaderAndCreateSnapshotTest -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5094) KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10

by Charles Herrick (Jira)

[ https://issues.redhat.com/browse/DROOLS-5094?page=com.atlassian.jira.plug... ] Charles Herrick updated DROOLS-5094: ------------------------------------ Attachment: image002.png image004.jpg Really the bug should be more focused on the fact that with the KIE-Base and KIE-Session set the Test Scenario (Legacy) FAILs. e: Charles.Herrick(a)perficient.com<mailto:Charles.Herrick@perficient.com> t: Texas Time -- Charles Herrick, Technical Architect m: 512-289-0926 | NASDAQ: PRFT | Perficient.com<http://www.perficient.com/> From: Toni Rikkola (Jira) <issues(a)jboss.org> Sent: Thursday, February 27, 2020 2:55 AM To: Charles Herrick <Charles.Herrick(a)perficient.com> Subject: [JBoss JIRA] (DROOLS-5094) KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10 [cid:image001.png@01D5ED4A.38F21650] Toni Rikkola<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fs...> commented on [Bug] DROOLS-5094<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> Re: KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> If you open the Test Scenario editor and select the Settings-tab you can find two dropdowns that let you select the kbase and ksession that the Test Scenario uses. [Add Comment]<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> Add Comment<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) [Image removed by sender. Atlassian logo] > KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10 > -------------------------------------------------------------------------------------------- > > Key: DROOLS-5094 > URL: https://issues.redhat.com/browse/DROOLS-5094 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.26.0.Final > Reporter: Charles Herrick > Assignee: Toni Rikkola > Priority: Critical > Attachments: image002.png, image004.jpg, image006.jpg, image007.png, image008.jpg > > > bug[1]: Once you set the KIE-Base and a KIE-Session in Settings on a Project, subsequent Test Scenario (Legacy) inherit/adopt the KIE-Base and KIE-Session. The run-scenario fails without even running. > Workaround: > 1. Create and build the Test Scenario (Legacy) > 2. Download the Test Scenario (creates an XML file) > 3. Edit the XML file to set the Session to : > <ksessions> > <string>defaultKieSession</string> > </ksessions> > 4. Delete the Test Scenario from Decision-Manager > Space > Project > Assets. > 5. Import Asset > the edited XML file. > Now the Test Scenario will run. > Bug[2]: In the Settings for a specific Test Scenario (Legacy) the KIE-Base and KIE-Session are NOT editable and can not be changed. To fix this you have to follow the workaround. > Versions: Windows 10, rhdm 7 v 7.5.1, EAP v 7.2, Drools: rhdmAdmin (About) == 7.26 Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1078) Automate VS subset https://github.com/kiali/kiali-ui/pull/1674

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1078: ------------------------------------- Summary: Automate VS subset https://github.com/kiali/kiali-ui/pull/1674 Key: SWSQE-1078 URL: https://issues.redhat.com/browse/SWSQE-1078 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5094) KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10

by Charles Herrick (Jira)

[ https://issues.redhat.com/browse/DROOLS-5094?page=com.atlassian.jira.plug... ] Charles Herrick updated DROOLS-5094: ------------------------------------ Attachment: image006.jpg image007.png image008.jpg These are NOT editable/un-choosable in rhdm 7.5.1 Decision Central Test Scenario (Legacy). Once they KIE-Base and KIE-Session are set in the Project > Settings, they are NOT able to be un-set in the Test Scenario (Legacy). And if they are there, the Test Scenario (Legacy) run-scenario will FAIL immediately. [cid:image006.jpg@01D5ED48.6ED79CB0] e: Charles.Herrick(a)perficient.com<mailto:Charles.Herrick@perficient.com> t: Texas Time -- Charles Herrick, Technical Architect m: 512-289-0926 | NASDAQ: PRFT | Perficient.com<http://www.perficient.com/> From: Toni Rikkola (Jira) <issues(a)jboss.org> Sent: Thursday, February 27, 2020 2:55 AM To: Charles Herrick <Charles.Herrick(a)perficient.com> Subject: [JBoss JIRA] (DROOLS-5094) KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10 [cid:image002.png@01D5ED48.6EC04420] Toni Rikkola<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fs...> commented on [Bug] DROOLS-5094<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> Re: KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> If you open the Test Scenario editor and select the Settings-tab you can find two dropdowns that let you select the kbase and ksession that the Test Scenario uses. [Add Comment]<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> Add Comment<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...> This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) [Image removed by sender. Atlassian logo] > KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10 > -------------------------------------------------------------------------------------------- > > Key: DROOLS-5094 > URL: https://issues.redhat.com/browse/DROOLS-5094 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.26.0.Final > Reporter: Charles Herrick > Assignee: Toni Rikkola > Priority: Critical > Attachments: image006.jpg, image007.png, image008.jpg > > > bug[1]: Once you set the KIE-Base and a KIE-Session in Settings on a Project, subsequent Test Scenario (Legacy) inherit/adopt the KIE-Base and KIE-Session. The run-scenario fails without even running. > Workaround: > 1. Create and build the Test Scenario (Legacy) > 2. Download the Test Scenario (creates an XML file) > 3. Edit the XML file to set the Session to : > <ksessions> > <string>defaultKieSession</string> > </ksessions> > 4. Delete the Test Scenario from Decision-Manager > Space > Project > Assets. > 5. Import Asset > the edited XML file. > Now the Test Scenario will run. > Bug[2]: In the Settings for a specific Test Scenario (Legacy) the KIE-Base and KIE-Session are NOT editable and can not be changed. To fix this you have to follow the workaround. > Versions: Windows 10, rhdm 7 v 7.5.1, EAP v 7.2, Drools: rhdmAdmin (About) == 7.26 Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ] Matthew Mahoney updated SWSQE-1077: ----------------------------------- Description: The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. Meeting with [~brian.avery] [~gbaufake]: 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... 2) Kiali team then to add an api test case(s) via 'curl' to validate the Istio/Kiali integration is properly functioning. was: The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. Meeting with [~brian.avery] [~gbaufake]: 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... 2) Kiali team then to add an api test case(s) via 'curl' that to validate the Istio/Kiali integration is properly functioning. > Kiali Test For Istio.io > ----------------------- > > Key: SWSQE-1077 > URL: https://issues.redhat.com/browse/SWSQE-1077 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. > Meeting with [~brian.avery] [~gbaufake]: > 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework > https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... > 2) Kiali team then to add an api test case(s) via 'curl' to validate the Istio/Kiali integration is properly functioning. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ] Matthew Mahoney updated SWSQE-1077: ----------------------------------- Description: The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. Meeting with [~brian.avery] [~gbaufake]: 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... 2) Kiali team then to add an api test case(s) via 'curl' that to validate the Istio/Kiali integration is properly functioning. was: The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. Meeting with [~brian.avery] [~gbaufake]: 1) BrinanA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... 2) Kiali team then to add an api test case(s) via 'curl' that to validate the Istio/Kiali integration is properly functioning. > Kiali Test For Istio.io > ----------------------- > > Key: SWSQE-1077 > URL: https://issues.redhat.com/browse/SWSQE-1077 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. > Meeting with [~brian.avery] [~gbaufake]: > 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework > https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... > 2) Kiali team then to add an api test case(s) via 'curl' that to validate the Istio/Kiali integration is properly functioning. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ] Matthew Mahoney updated SWSQE-1077: ----------------------------------- Sprint: Kiali Sprint #32 > Kiali Test For Istio.io > ----------------------- > > Key: SWSQE-1077 > URL: https://issues.redhat.com/browse/SWSQE-1077 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. > Meeting with [~brian.avery] [~gbaufake]: > 1) BrinanA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework > https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... > 2) Kiali team then to add an api test case(s) via 'curl' that to validate the Istio/Kiali integration is properly functioning. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 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 February 2020