[jboss-jira] [JBoss JIRA] (WFCORE-4550) Create a test to validate CLI embedded server output after a reload
James Perkins (Jira)
issues at jboss.org
Wed Jun 26 16:52:00 EDT 2019
[ https://issues.jboss.org/browse/WFCORE-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752472#comment-13752472 ]
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)
More information about the jboss-jira
mailing list