[
https://issues.jboss.org/browse/WFCORE-4550?page=com.atlassian.jira.plugi...
]
James Perkins updated WFCORE-4550:
----------------------------------
Description:
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}}
command 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.
was:
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
--start-mode=admin-only}} command 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.
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}}
command 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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)