April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3857) Update html/css for Settings dock

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3857?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3857: --------------------------------- Labels: ScenarioSimulation (was: ) > Update html/css for Settings dock > --------------------------------- > > Key: DROOLS-3857 > URL: https://issues.jboss.org/browse/DROOLS-3857 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Update the html/css for Settings docks with suggestion from [~srambach] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3857) Update html/css for Settings dock

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3857: ---------------------------------------- Summary: Update html/css for Settings dock Key: DROOLS-3857 URL: https://issues.jboss.org/browse/DROOLS-3857 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Update the html/css for Settings docks with suggestion from [~srambach] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3854) DMN: Add a nested row to a new Structured data type by default

by Donato Marrazzo (Jira)

[ https://issues.jboss.org/browse/DROOLS-3854?page=com.atlassian.jira.plugi... ] Donato Marrazzo commented on DROOLS-3854: ----------------------------------------- Hi [~uxdlc] and [~karreiro], this looks a nice improvement. But I continue to think that saving is a useless overhead: why should I confirm a change with a proper action? E.g. in google docs, you don't save just change it! So my suggestion is removing the save action at all, the only action that would require a confirmation is when you change a structure in a datatype, because in such way the user risks loosing the structure content. For a structure the most common action is adding a child, so I believe that "add nested element" deserves a dedicated button easily accessible. > DMN: Add a nested row to a new Structured data type by default > -------------------------------------------------------------- > > Key: DROOLS-3854 > URL: https://issues.jboss.org/browse/DROOLS-3854 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability: Reduce the number of clicks / actions to add a nested element. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11866) Cannot get exception as pass-by-reference

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-11866?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil updated WFLY-11866: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12167 (was: https://github.com/wildfly/wildfly/pull/12167, https://github.com/wildfly/wildfly/pull/12191) > Cannot get exception as pass-by-reference > ----------------------------------------- > > Key: WFLY-11866 > URL: https://issues.jboss.org/browse/WFLY-11866 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final, 17.0.0.Beta1 > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Major > Fix For: 17.0.0.Beta1 > > > Despite of <in-vm-remote-interface-invocation pass-by-value="false"/>, an exception is not thrown by reference, which results in java.io.NotSerializableException if the exception doesn't implement Serializable. This is a blocker of a large migration project from WebLogic because it throws by reference even if that doesn't implement Serializable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-702) Report code coverage for system tests in jenkins job via cobertura plugin

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-702?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-702: -------------------------------- Description: https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverag... > Report code coverage for system tests in jenkins job via cobertura plugin > ------------------------------------------------------------------------- > > Key: SWSQE-702 > URL: https://issues.jboss.org/browse/SWSQE-702 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverag... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-701) Get code coverage for system tests

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-701?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-701. --------------------------------- Resolution: Done See https://github.com/kiali/kiali/pull/970 > Get code coverage for system tests > ---------------------------------- > > Key: SWSQE-701 > URL: https://issues.jboss.org/browse/SWSQE-701 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > # add main go test file which will basically just call main() function to start kiali > # compile kiali in "code coverage ready" way: go test -c -covermode=count -coverpkg ./... > # use this binary to create kiali docker image > # start this docker image with following params: -systemTest > -test.coverprofile /opt/kiali/console/coverage.cov > # run tests > # kill kiali in a graceful way (after this step the coverage report should be generated) > # get report from docker container -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-701) Get code coverage for system tests

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-701?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-701: -------------------------------- Description: # add main go test file which will basically just call main() function to start kiali # compile kiali in "code coverage ready" way: go test -c -covermode=count -coverpkg ./... # use this binary to create kiali docker image # start this docker image with following params: -systemTest -test.coverprofile /opt/kiali/console/coverage.cov # run tests # kill kiali in a graceful way (after this step the coverage report should be generated) # get report from docker container > Get code coverage for system tests > ---------------------------------- > > Key: SWSQE-701 > URL: https://issues.jboss.org/browse/SWSQE-701 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > # add main go test file which will basically just call main() function to start kiali > # compile kiali in "code coverage ready" way: go test -c -covermode=count -coverpkg ./... > # use this binary to create kiali docker image > # start this docker image with following params: -systemTest > -test.coverprofile /opt/kiali/console/coverage.cov > # run tests > # kill kiali in a graceful way (after this step the coverage report should be generated) > # get report from docker container -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-652) Investigate sonar in central ci

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-652?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-652. --------------------------------- Resolution: Done Yes we can use it, we can use jenkins plugin to push results there. Only problem is http, see comments in https://docs.engineering.redhat.com/display/CentralCI/Central+CI+SonarQub... > Investigate sonar in central ci > ------------------------------- > > Key: SWSQE-652 > URL: https://issues.jboss.org/browse/SWSQE-652 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Check if we can use sonar in central CI - https://docs.engineering.redhat.com/display/CentralCI/Jenkins+Sonar+Confi... > https://docs.engineering.redhat.com/pages/viewpage.action?pageId=44543267 > https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverage -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-700) Investigate options for golang code coverage

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-700?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-700. --------------------------------- Resolution: Done For unit tests it's working out of the box just by running e.g. _go test -covermode=count -coverprofile=count.out_ For system tests it's more complicated: # add main go test file which will basically just call main() function to start kiali # compile kiali in "code coverage ready" way: go test -c -covermode=count -coverpkg ./... # use this binary to create kiali docker image # start this docker image with following params: -systemTest -test.coverprofile /opt/kiali/console/coverage.cov # run tests # kill kiali in a graceful way (after this step the coverage report should be generated) # get report from docker container > Investigate options for golang code coverage > -------------------------------------------- > > Key: SWSQE-700 > URL: https://issues.jboss.org/browse/SWSQE-700 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > How can we get code coverage report in golang? > Useful doc: > * https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverage > * https://blog.golang.org/cover > * https://www.elastic.co/blog/code-coverage-for-your-golang-system-tests > * https://forum.golangbridge.org/t/how-to-do-go-test-coverage-for-system-te... > * https://husobee.github.io/golang/test/coverage/2015/11/17/external-test-c... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-700) Investigate options for golang code coverage

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-700?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-700: -------------------------------- Description: How can we get code coverage report in golang? Useful doc: * https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverage * https://blog.golang.org/cover * https://www.elastic.co/blog/code-coverage-for-your-golang-system-tests * https://forum.golangbridge.org/t/how-to-do-go-test-coverage-for-system-te... * https://husobee.github.io/golang/test/coverage/2015/11/17/external-test-c... was:How can we get code coverage report in golang? > Investigate options for golang code coverage > -------------------------------------------- > > Key: SWSQE-700 > URL: https://issues.jboss.org/browse/SWSQE-700 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > How can we get code coverage report in golang? > Useful doc: > * https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverage > * https://blog.golang.org/cover > * https://www.elastic.co/blog/code-coverage-for-your-golang-system-tests > * https://forum.golangbridge.org/t/how-to-do-go-test-coverage-for-system-te... > * https://husobee.github.io/golang/test/coverage/2015/11/17/external-test-c... -- 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