[jboss-jira] [JBoss JIRA] (AS7-4535) Test framework for CLI-based tests can be very slow

Dominik Pospisil (JIRA) jira-events at lists.jboss.org
Fri Apr 27 04:33:17 EDT 2012


    [ https://issues.jboss.org/browse/AS7-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688261#comment-12688261 ] 

Dominik Pospisil commented on AS7-4535:
---------------------------------------

The problem is that there is no easy way how to identify that the CLI has finished writing stuff to output stream. 
Could be done by trying to parse the result line-by-line and guess when the output is done. However this might not work for all use cases. The other way would be to use CLI API which is now available (and was not ~5 months ago).
                
> Test framework for CLI-based tests can be very slow
> ---------------------------------------------------
>
>                 Key: AS7-4535
>                 URL: https://issues.jboss.org/browse/AS7-4535
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 7.1.2.Final-redhat1
>            Reporter: David Bosschaert
>            Assignee: Ondrej Zizka
>            Priority: Minor
>
> The org.jboss.as.test.integration.management.base.AbstractCliTestBase provides a suitable API for testing CLI-based operations. However, running tests with a relatively large number of CLI operations can take a *long* time, seemingly much longer than necessary. This is probably related to the fact that CLIWrapper.readAllAsOpResult() method always seems to wait until the lineTimeout has expired. 
> Typically the WAIT_LINETIMEOUT value is used for this argument. Shortening the timeout is not an option as I have seen cases where a test would fail when run on a slow machine, but this only happens occasionally.
> It would be *much* better if a timeout was not needed for this and the test would wait until a certain operation was finished.
> This can be observed in org.jboss.as.test.integration.management.cli.JmsTestCase and I also experienced it when writing the org.jboss.as.test.integration.osgi.management.OSGiManagementTestCase.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list