[JBoss JIRA] (WFCORE-4550) Create a test to validate CLI embedded server output after a reload
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4550?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4550:
---------------------------------------
Ah okay. I'm going to edit the description then. I feel I should know this, but does {{reload}} wait until the server is started to return?
> Create a test to validate CLI embedded server output after a reload
> -------------------------------------------------------------------
>
> Key: WFCORE-4550
> URL: https://issues.jboss.org/browse/WFCORE-4550
> Project: WildFly Core
> Issue Type: Task
> Components: CLI, Test Suite
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
>
> There are tests that validate the output however these use the {{CommandContext}} which doesn't consume all the console output. It would be useful to have a test which uses a new process to test for things like WFCORE-4543.
> Some thought will need to go into this on how it would work. We should use a {{:reload(running-mode=admin-only)}} operation and wait for the server to be ready, then use something like {{echo hello}} to ensure that logging was not configured on the CLI {{LogContext}}.
> This is not an urgent issue as manually verifying this is easy. However in the past we've had other issues similar to this and the output really should be verified. Both the {{:reload}} operation and {{reload}} command should likely be tested.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (WFLY-12242) Default VERIFY_SUSPECT timeout is too high
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-12242:
-----------------------------------
Summary: Default VERIFY_SUSPECT timeout is too high
Key: WFLY-12242
URL: https://issues.jboss.org/browse/WFLY-12242
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 17.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
In a world where WF starts in 2 seconds on a 2 year old laptop, the default VERIFY_SUSPECT timeout of WF (currently 5 seconds) can easily create the condition where a killed and restarted server shows up in the topology before the old server leaves. Ideally, the VERIFY_SUSPECT timeout should not be longer than the time it takes to start the server process. A timeout of 1 second should suffice.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (SWSQE-796) Kiali Doc OKR Metrics
by Matthew Mahoney (Jira)
Matthew Mahoney created SWSQE-796:
-------------------------------------
Summary: Kiali Doc OKR Metrics
Key: SWSQE-796
URL: https://issues.jboss.org/browse/SWSQE-796
Project: Kiali QE
Issue Type: QE Task
Reporter: Matthew Mahoney
Currently Kiali Doc metrics are not represented in Tablue. Work with Kiali Docs folks to identify tests which will generate PQI/OKR metrics.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4142:
--------------------------------------
Summary: [GSS-RFE] UX design: Find feature in GDST/DMN 7.5 (was: [GSS-RFE] UX design: Search feature in GDST 7.5)
> [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
> -------------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> See referenced document.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Search feature in GDST 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4142:
--------------------------------------
Description:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirements
See referenced document.
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Searching for non-existing result
- Result appearing once
- Result appearing multiple times
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
was:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirements
*Find function*
* Find text strings within "Data cells"
* Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
* “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
* Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
*UI Find/Search components*
* A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
* UI element that supports a long string query in the input field of the search box
*Find/Search Results*
* The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
* If there are No results: Presentation and state of the search component when users searches for something and gets no results.
* Search results shows strings that might: Appear once, Appear multiple times
* [FIND] Previous/Next arrows with focus, to navigate.
* Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Searching for non-existing result
- Result appearing once
- Result appearing multiple times
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
> [GSS-RFE] UX design: Search feature in GDST 7.5
> -----------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> See referenced document.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Search feature in GDST 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4142:
--------------------------------------
Description:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirements
*Find function*
* Find text strings within "Data cells"
* Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
* “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
* Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
*UI Find/Search components*
* A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
* UI element that supports a long string query in the input field of the search box
*Find/Search Results*
* The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
* If there are No results: Presentation and state of the search component when users searches for something and gets no results.
* Search results shows strings that might: Appear once, Appear multiple times
* [FIND] Previous/Next arrows with focus, to navigate.
* Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Searching for non-existing result
- Result appearing once
- Result appearing multiple times
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
was:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirements
*Find function*
* Find text strings within "Data cells"
* Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
* “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
* Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
*UI Find/Search components*
* A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
* UI element that supports a long string query in the input field of the search box
*Find/Search Results*
* The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
* If there are No results: Presentation and state of the search component when users searches for something and gets no results.
* Search results shows strings that might: Appear once, Appear multiple times
* [FIND] Previous/Next arrows with focus, to navigate.
* Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Searching for non-existing result
- Result appearing once
- Result appearing multiple times
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
> [GSS-RFE] UX design: Search feature in GDST 7.5
> -----------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> *Find function*
> * Find text strings within "Data cells"
> * Find text strings within the Guided Decision Table editor (tables), DMN graph, DMN Decision Table
> * “Find all GDT cells, DRG Elements, and any other searchable element. Searchable elements are: DMN nodes (Decisions, Inputs, BKMs, etc); DMN Decision Tables cell; and GDT cells See jira. “Open item: If Find supports all boxed logic or just Decision tables.
> * Search using text strings,including numbers, symbols: A-Z, a-z, 0-9, Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +, Blank spaces
> *UI Find/Search components*
> * A UI element - Development definition: “In the UI, each editor instance will have an instance of a SearchBarComponent. This component will call the editor index, that will have all searchable elements. When a given component has the desired text, the respective highlight-command will be executed.”
> * UI element that supports a long string query in the input field of the search box
> *Find/Search Results*
> * The search/find mechanism must return results even when users type only the part of the search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed
> * If there are No results: Presentation and state of the search component when users searches for something and gets no results.
> * Search results shows strings that might: Appear once, Appear multiple times
> * [FIND] Previous/Next arrows with focus, to navigate.
> * Supports keyboard controls for basic accessibility - focus and navigation (tab order, etc.)
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months