[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
[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
[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
[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