[JBoss JIRA] (SWSQE-966) UI Automations - Check Traces tab functionality
by Hayk Hovsepyan (Jira)
[ https://issues.jboss.org/browse/SWSQE-966?page=com.atlassian.jira.plugin.... ]
Hayk Hovsepyan updated SWSQE-966:
---------------------------------
Sprint: Kiali Sprint #28 (was: Kiali Sprint #28, Kiali Sprint #30)
> UI Automations - Check Traces tab functionality
> -----------------------------------------------
>
> Key: SWSQE-966
> URL: https://issues.jboss.org/browse/SWSQE-966
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Major
> Labels: automation
>
> Traces tab of Kiali is not automated in UI Automations framework.
> We need to automate:
> 1. Traces menu clicking and verifying the opened page.
> 2. Traces tab. Click, no errors, no login asked.
> 3. Search Traces in Traces tab. Verify that it shows traces or a message that traces does not exist.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (SWSQE-990) Traffic tab automation
by Hayk Hovsepyan (Jira)
Hayk Hovsepyan created SWSQE-990:
------------------------------------
Summary: Traffic tab automation
Key: SWSQE-990
URL: https://issues.jboss.org/browse/SWSQE-990
Project: Kiali QE
Issue Type: QE Task
Reporter: Hayk Hovsepyan
Assignee: Hayk Hovsepyan
Check Traffic tab of an object.
Read all items.
Click to links.
Verify that the original object is listed in the Traffic tab of clicked object.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (SWSQE-966) UI Automations - Check Traces tab functionality
by Hayk Hovsepyan (Jira)
[ https://issues.jboss.org/browse/SWSQE-966?page=com.atlassian.jira.plugin.... ]
Hayk Hovsepyan updated SWSQE-966:
---------------------------------
Sprint: Kiali Sprint #28, Kiali Sprint #30 (was: Kiali Sprint #28)
> UI Automations - Check Traces tab functionality
> -----------------------------------------------
>
> Key: SWSQE-966
> URL: https://issues.jboss.org/browse/SWSQE-966
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Major
> Labels: automation
>
> Traces tab of Kiali is not automated in UI Automations framework.
> We need to automate:
> 1. Traces menu clicking and verifying the opened page.
> 2. Traces tab. Click, no errors, no login asked.
> 3. Search Traces in Traces tab. Verify that it shows traces or a message that traces does not exist.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ]
Tommasso Borgato commented on WFLY-12718:
-----------------------------------------
Added Undertow as component, because it looks like Clustering is affected by this bug but may also not be the cause
> Clustering: replicated-cache sampling errors
> --------------------------------------------
>
> Key: WFLY-12718
> URL: https://issues.jboss.org/browse/WFLY-12718
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Web (Undertow)
> Affects Versions: 18.0.0.Final
> Reporter: Tommasso Borgato
> Assignee: Paul Ferraro
> Priority: Blocker
>
> The issue is about replicated-cache in fail-over tests.
> WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add()
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add()
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl)
> {noformat}
> The test is run with wildfly-18.0.0.Final.zip;
> The same tests run with version wildfly-17.0.1.Final.zip do not have any problem;
> hence this looks like a regression;
> As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error;
> Here are the runs that exhibit this issue:
> - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...]
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...]
> We also repeated the tests to make sure it can be reproduced:
> - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...]
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ]
Tommasso Borgato updated WFLY-12718:
------------------------------------
Component/s: Web (Undertow)
> Clustering: replicated-cache sampling errors
> --------------------------------------------
>
> Key: WFLY-12718
> URL: https://issues.jboss.org/browse/WFLY-12718
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Web (Undertow)
> Affects Versions: 18.0.0.Final
> Reporter: Tommasso Borgato
> Assignee: Paul Ferraro
> Priority: Blocker
>
> The issue is about replicated-cache in fail-over tests.
> WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add()
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add()
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl)
> {noformat}
> The test is run with wildfly-18.0.0.Final.zip;
> The same tests run with version wildfly-17.0.1.Final.zip do not have any problem;
> hence this looks like a regression;
> As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error;
> Here are the runs that exhibit this issue:
> - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...]
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...]
> We also repeated the tests to make sure it can be reproduced:
> - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...]
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (SWSQE-989) Get time with seconds from tooltip in UI tests
by Filip Brychta (Jira)
Filip Brychta created SWSQE-989:
-----------------------------------
Summary: Get time with seconds from tooltip in UI tests
Key: SWSQE-989
URL: https://issues.jboss.org/browse/SWSQE-989
Project: Kiali QE
Issue Type: QE Task
Reporter: Filip Brychta
Date is displayed in different format in PF4: Oct 30, 8:21 am and full date is displayed in tooltip. We don't have solution for getting text from tooltip yet so we are ignoring seconds for now. We need to fix that to be able to compare with date received via REST which contains seconds.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-4636:
----------------------------------
Sprint: 2019 Week 44-46 (from Okt 28)
> Update Scenario Cheatsheet to mention MVEL
> ------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.jboss.org/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitations
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-4636:
----------------------------------
Story Points: 1
> Update Scenario Cheatsheet to mention MVEL
> ------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.jboss.org/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitations
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL and Background
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-4636:
----------------------------------
Summary: Update Scenario Cheatsheet to mention MVEL and Background (was: Update Scenario Cheatsheet to mention MVEL)
> Update Scenario Cheatsheet to mention MVEL and Background
> ---------------------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.jboss.org/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitations
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFWIP-231) Error messages in operator logs
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-231?page=com.atlassian.jira.plugin.... ]
Martin Choma closed WFWIP-231.
------------------------------
Verified with jbossqe-eap/wildfly-operator:0.3.0.Beta1-9d59838
> Error messages in operator logs
> -------------------------------
>
> Key: WFWIP-231
> URL: https://issues.jboss.org/browse/WFWIP-231
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Critical
> Labels: operator
>
> The following error log message appears in operator log:
> {noformat}
> {"level":"error","ts":1570436049.1596415,"logger":"wildlfyserver_resources","msg":"Failed to create new
> resource","WildFlyServer.Namespace":"pkremens-namespace","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart-
> loadbalancer","Resource.Type":"*v1.Service","error":"services \"quickstart-loadbalancer\" already exists","stacktrace":"github.com/go-logr/zapr.
> (*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\ngithub.com/wildfly/wildfly-operator/pkg/resources.Create\n\t/go
> /src/github.com/wildfly/wildfly-operator/pkg/resources/actions.go:37\ngithub.com/wildfly/wildfly-operator/pkg/resources
> /services.CreateOrUpdateLoadBalancerService\n\t/go/src/github.com/wildfly/wildfly-operator/pkg/resources/services/service.go:63\ngithub.com
> /wildfly/wildfly-operator/pkg/controller/wildflyserver.(*ReconcileWildFlyServer).Reconcile\n\t/go/src/github.com/wildfly/wildfly-operator
> /pkg/controller/wildflyserver/wildflyserver_controller.go:195\nsigs.k8s.io/controller-runtime/pkg/internal/controller.
> (*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.1.12/pkg/internal/controller/controller.go:215\nsigs.k8s.io
> /controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime(a)v0.1.12/pkg/internal/controller
> /controller.go:158\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20190221213512-86fb29eff628
> /pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/pkg/mod/k8s.io
> /apimachinery@v0.0.0-20190221213512-86fb29eff628/pkg/util/wait/wait.go:134\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/go/pkg/mod/k8s.io
> /apimachinery@v0.0.0-20190221213512-86fb29eff628/pkg/util/wait/wait.go:88"}
> {noformat}
> The error message appears every time during project creation, it can be reproduced using the latest upstream (dd5a057) operator and provided quickstart-cr.yaml example.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months